[bt-devel] Your changes in CVS

Jaak Ristioja Ristioja at gmail.com
Tue Nov 17 04:03:35 MST 2009


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

Eeli Kaikkonen wrote:
> On Tue, 17 Nov 2009, Jaak Ristioja wrote:
>> I completely agree that we should branch before beta or RC. I'd prefer
>> that we branch the RC and that branch will only get bug fixes and
>> improved translations.
> 
> The normal convention is that the last RC will not be changed at all
> before the final release. If there will be changes, a new RC is released
> until there are no changes. We haven't followed this convention but
> introduced even new features for an RC which actually would need another
> beta testing phase, and fixed quite many things after RC which would
> need another RC or even beta. My commit of Get Remote Source List
> feature was such (though before RC, not after). One reason I committed
> it too late was that I couldn't have committed it for a long time
> otherwise. But anyways, RCs should be open for important bugfixes only.
> Therefore bug-a-thons and other activities should happen before an RC,
> not after. Otherwise our RCs are actually betas and should be labeled as
> such.

Good point. I think formulating what exactly beta releases and release
candidates are, would help us. I think that what Eeli just wrote about
RC's and betas further demonstrates the need to branch properly.

> On the other hand, I have wondered whether our release schedule is too
> quick. Now the beta and RC releases aren't very useful if they are only
> reminders for developers. It would be more useful to get them in to
> "on-the-edge"  repositories and let eager users test them for a while.
> Two weeks is too short a time for that. We should allow two weeks for
> packaging/publishing and two weeks for testing. It's almost a month. But
> now we have major relases about once a month which is too much.
> 
> I know this is against the "release early, release often" idea, but I
> don't see a rapid release schedule very useful if it makes packagers
> work all the time or users lagging behind when new release have come
> out even when the older one isn't yet packaged.
> 
> This all may of course be my own imagination. Maybe we just understand
> beta, rc and final labels differently. But we should come to a
> conclusion so that we can orientate properly for each release.

I agree. For example I made an ebuild for gentoo for BibleTime 2.3 and
skipped bugging the developers until the latest 2.3.X bugfix, because I
thought it would be impolite to bug them so often.


Jaak
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (GNU/Linux)

iQgcBAEBAgAGBQJLAoMCAAoJEFqwhAoGc/hvYd0//jpNpH2a+i93EdvWdsbWsb4O
Zb+owoLyuFc+8L4nS9kPnDoAIb4vrE3+SRM1+Xj/y8oysQZzK4iQ6+qsq7spq65b
erZyUkyX8hIoTUz+o1AKnKNzzpEyH49+Gd1byZXEfcXM6qSDm5DcErjn7FrfUc9P
IWdzrB3bJFc9garHKcqYugWnU8zULvMY8QgF9Vq11NWHswJM7bGvizjGV/uVdgpF
PNDfxzyzXp9dbbSb881Zvm++AIwFlVCpVNke+Enlj1rddzICTtT8D3zTcnlTceM/
02nIRoqMmtV01Is3ySux1Vget2r4MaKTyT8DfevIjHyOEdYE33QKEzuxjogAPTXA
dbNPQW0uN3P9cAifp8YMZQ/inbzuXaiXGMJZB7sbt8RxB+y62At6yyOSNbE37c4X
PvYhJW4wt+WqhVHlthkYCWLPumFbAgxxhw0rz2EJKk8zFk1qBE0IBwv+rxvb8MPX
Y7G+4vDDwjdhlU9ezbmtgQ19OE/4Non+H5LLc4cjE7wvcwhmOmDEcEYv0f7Pg2cS
1si+w1czJxWZgiRW7SLuSvVtLoP6LTiD6B00Wn6Gy4PqedR+S+31sDM6hvl7XwzY
2M57AcqmT7d7b0biQZ6uBpSzo4rlzgMyH4QSB+Wl/3c222cI2tWNy2roKbNlvcME
3e+vpoXyaiQRA+e2upYtNSyQTa4wXuheUHwvdVA+/5ufC+cD0oWrmCyOhT1EhNzo
sxQ60lys7cDVHNugdEdoOw9M3WpSu/AGAbuE5SfrW+34V165zHnOzRox0d8V0EI4
60CZ3CPGTICP/ZkJRi2O8MS9prYMyQxeiWteQqtgBqKJ4cJKL714MIn02ewHCmxF
odYUuWNv7luAer6VWKrdr/jhpko7ikX4HrdsS5d2FCOelNyXpsf69Hr0KXF/s5X9
3OdCqsOIK5lO2jUeVyvKMrRcwRahIy4qBodgA766QjESg0xcp+ywCEuMvo1NMw5+
B/c59+D+lA7L5hVtceoZsu65h8ZCmo8KUln4L8F93ps9EhERsOs9iqodEfPoCaDs
5CYG83yvuw6ARNyENaXLPXkxbHLoi1Nw1Ed/G1Iyl5WnpNqKxp1yX1WfHbzJKP8p
foAWV/SEy0+c7SmdQtDlYECHmLklT2acl/71Kp6E69x+aKq6IXevKUEg5FimIBAj
OWK6PNw3KkmHTPnGUWrU4t4TfbFOPLNPxpyshEyefeZq5jxlwCiITdNv7DYJD3DL
FTY0GbHID/HyDeZ2MRGpW74NPIwPZoI+rhUdY2KV/RvFWffc+cOJw+WzwZhPNil/
pEY+5s3AORpREd96wYP3Bcl7x9vZYkg3Hq9jYkC2v0oPewDCAwALkKywcnnfX73B
OTljbi4swDTcm0ZCOViHIBSxAiNvFNRxV0DjhVJB/9NEbKGi1FGwI2ae8nkowPl7
50vEk6C1LL+utpkDcIWQfOSW1IxlOHpPR88fkUmtx1KY2wjr/FbcV1UMwND3nBwi
sYBT/ZmfpE8UHM0ezB4SmV0V4sV7vNuFbrIgGwukC9goGCyAGGjZ2uoqk6IFuHwW
/Bg/77wKwC098rAqHpj0TQEleRsb7TVPhrVhXUIfNsgeVAgtPsm+R6SMuCAv8TFs
uhr++Xi/KFVMng0Ix6Tm/E1usYnnFon2c6uGeXbE7XnohLjDg6KWbW7F/2kSG+/R
gsSVQ/+I4qKk2WaFHdc8tFY4zH9VCLuuWB05h+50XjelIAr1bwCJQW//mRru0iKh
8DHFPgzAC8fz7/qrlHJ5Iu8XPb42CoArZbwhPRCf2dRNeAK1wq3OPvx390bHIG2M
LkJKSAqtwawJBKLgzOh30yapLZVBgzJC/VGyWZ/ang9HsiOJ0NEvXqEbN/t92nIG
LbZvFfIsyvSv4wCsPTBVTAvpN4voE2LqmRrm9x6BjTjWwI2eEBpElWmfJ5ZaAOwz
dfzE/JzWHWm/un19BAEMz1eafQIOzwNs7oLopDisb7Np7QgmxLxdEqDtoHCkKfzj
W7tRHzjuS5GQldTfQLQDH/BRfvbACI4g5r4PRJ0iOJy+O11ItKOS8hO27axq9+uS
0eetNRJ3hBaaLoFXUdbt8E8F4h8AITku97kk4H31BKLjyhUF7yHrciq19t0o6q3H
s5vDu2sDMIG4TEU2ZIDH2UwVAAvpfzKcSgrQ6ZqspcdB+k1utiunm1EpgOS+7X1D
iAb7233jTciGyRplbH/n8FWDK2QgCVPIS02WeNS8oThBfo7HNk2+eFVlwSlqBCHp
bhBrrOw/CjLn98QxTMAvY0Jbmo7T7gI2RUhCHO4Vh73NB9q5Vhc43v0Zjnu6UWdi
uX1lSpatsR6BCyBXWbRXEkN+Fyqbvw2EWl5LtPg08GbAoDUMVTNTVe7L2kWFB5Jq
ERagPT3wwplwAkIqw7P8YUEFEaqEA/CbPeaqZON1IAA/pNqKJRimJnrrsakOy0D9
fj4q8T3CdjlVUhTwJuqVyzPLSc/QzZwSpIV/WAksLto+T+S5OtwSTGGr05Kdn6jM
M3p54t32CPVotTM4iNgD7BEc1Crxzwl0nmqHTz/hpayltgB42boyEG1nFlCRrcQX
INubJBPNZp1rGv9FULCtyqNtk+QIt+go8V1q3Z1OxLELaY+c4hJ1HNCpGnj5J3wc
E6X9rAqLKgO3NDoPAb4BvSVvOZ7LkvfoQduKFEYpvsqGdIjm2w3Pzq1YyzL82LYD
pMDWq6SnA5Jzfzo2L3ad
=6E3M
-----END PGP SIGNATURE-----



More information about the bt-devel mailing list