Release Team BoF Summary

Jorge Manuel B. S. Vicetto jmbsvicetto at gentoo.org
Sat Jul 14 12:07:31 UTC 2012


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 14-07-2012 10:29, Michael Jansen wrote:
> On Friday, July 13, 2012 02:31:35 PM Aurélien Gâteau wrote:
>> Le jeudi 12 juillet 2012 20:43:12 Albert Astals Cid a écrit :
>>> So here comes the summary of the Release Team BoF, the attached
>>> picture is all we wrote during the BoF itself so all written
>>> here is me trying to remember what we said, if any of the
>>> presents disagrees or remembers more, please do not hesitate to
>>> comment.
>> 
>> Something which we discussed in the KDE Quality BoF and is of
>> interest to the KDE Release Team is the numbering of unstable
>> versions.
>> 
>> Up to now we have been using 4.N.8* and 4.N.9* for alpha, beta
>> and rc. The problem with those is it is difficult when you get a
>> report on 4.8.85 to know if the user is running beta1, beta2, rc1
>> or something else.
>> 
>> To address this we proposed the following numbering scheme:
>> 
>> 4.N.7{1,2,3} => N+1 alpha 1, 2, 3 4.N.8{1,2,3} => N+1 beta 1, 2,
>> 3 4.N.9{1,2,3} => N+1 rc 1, 2, 3
> 
> Why not marking an alpha, beta and rc as what it is and every other
> project out there already does? Why masking is as a stable
> release?
> 
> 4.N.1~alpha1 4.N.1~alpha2 4.N.1~beta1 4.N.1~beta2 4.N.1~rc 4.N.1
> 
> Which btw. was discussed on this very list. So i would like to know
> what the rationale behind this scheme is. Why keep doing it?

Both proposals are fine for us (Gentoo).

Mike, I assume in the above you meant to say given a release 4.N, the
versions of the new release will be:

4.(N+1)-alpha1
4.(N+1)-alpha2
4.(N+1)-beta1
4.(N+1)-beta2
4.(N+1)-rc
4.(N+1)

> Mike
> 
> 
> 
> _______________________________________________ release-team
> mailing list release-team at kde.org 
> https://mail.kde.org/mailman/listinfo/release-team
> 

- -- 
Regards,

Jorge Vicetto (jmbsvicetto) - jmbsvicetto at gentoo dot org
Gentoo- forums / Userrel / Devrel / KDE / Elections / RelEng


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJQAWEDAAoJEC8ZTXQF1qEP2hUP/ihaii/nIyYMlWOLtqK44Ysw
AUdQvxBBPCWDvvHeg5bp12p/Oeq8cdU4swoq+abgtXse421pTyOUMYs5q4lTo/N5
1cb0XzzLXooznO59YdvsmLaLShamFzr0xvW9PC8nwgOgLNuCwSDwSP9cqFgrja0l
PEieSWGBgfaddKm7xtjAAsVInHxYqs0PjOmNy02nKIWIKBoNQG3d54j2Ft8EU5ox
tSIueDwKXa0EiuoA98Vwjk6r2Ze4pQPVVS1MeN66cobz0NI9Xy3QkYA4gB/uUS0r
W8x2Z/OdRCZCEYyPQk7tOnetA/MK/ztOUHcBzP17lnfjdqA0a3n32f1GJLgfkwhD
jEqkl9zFmyJnSaamUxi1/mnGStt6H+af6jFWFBO/iB1jPRTUu3lkF908H8se65gO
lTLJozNb4kLQwUxDzNEW7Rvtu/J1TdTg3JE/tj+fM9eOdlTukAd7qFL+1QJWavlx
0aEJPfgjZ1NF+o/rNeqAyLBIeWw3OkrnGImrkEfRhHaS/axTtu5f4O/eAfwxvSfb
QcO0PcA84DAwAiVuO/HzBdrGkPDZdmDS0B6rlZya3nI3GkASkjiNK1WJ7mIRiXXj
q3FPO/jOn9yznc8Yh81Fm/8TAJNoNSQHHUcgKv0+hNMr2cike22+J6CPGfWrLEfW
+xKocL0Bchonk02zmUmx
=UO5C
-----END PGP SIGNATURE-----


More information about the release-team mailing list