--===============4465300423336345203==
Content-Type: multipart/signed; boundary="nextPart9845492.VJ0dASIaUW"; micalg="pgp-sha1"; protocol="application/pgp-signature"
Content-Transfer-Encoding: quoted-printable


--nextPart9845492.VJ0dASIaUW
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"

On Wednesday 15 August 2012 14:12:53 Albert Astals Cid wrote:
> El Dimecres, 15 d'agost de 2012, a les 13:55:59, Martin Gr=C3=A4=C3=9F=
lin va escriure:
> > Am 15.08.2012 12:44, schrieb Albert Astals Cid:
> > > What do you guys think?
> >=20
> > clear +1, but maybe use target milestone instead of version fixed i=
n
> > (or at least in addition).
>=20
> You can't set the milestone in a git/svn commit (AFAIK) so no, let's =
use
> what we told everybody to use, i.e. the FIXED-IN: keyword in commits.=

this would only need to adjust the hook to update in additon the target=
=20
milestone. I just checked the docs [1] and target_milestone can be set =
through=20
the API. The problem is most likely that most bugzilla products do not =
use the=20
target_milestone so setting it would fail. Which is probably a reason w=
hy the=20
kludge with the custom free-text field got introduced.

Maybe Jeroen could comment on this and whether it would be possible to =
easily=20
create the target milestones for all KDE SC products?

Best Regards
Martin

[1]=20
http://www.bugzilla.org/docs/4.2/en/html/api/Bugzilla/WebService/Bug.ht=
ml#update
--nextPart9845492.VJ0dASIaUW
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEABECAAYFAlAr7kwACgkQqVXwidMiVrrT2QCgk8O37Zem3a26cuv5XMuZqbga
/SQAni0N0ynneb3fyEw/VarSyfFrxI5o
=h4Uw
-----END PGP SIGNATURE-----

--nextPart9845492.VJ0dASIaUW--


--===============4465300423336345203==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team

--===============4465300423336345203==--