[Opendnssec-develop] How to handle trunk until 1.0.0?

Rickard Bellgrim rickard.bellgrim at iis.se
Tue Jan 26 10:18:16 CET 2010


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi

We now have a RC3 and are really close to releasing 1.0.0. There are still coming in some suggested changes to the code and configure scripts. It would be reasonable to not commit any minor changes to trunk until we have released 1.0.0. But it would be ok to commit code if it fixes a major problem.

If we decide to fix a problem, then we have to do a RC4. After 1.0.0 we have to decide on how to handle our release management, so that we do not get situations like this again.

Do you agree? (Or do we want everything to be correct instead of releasing a 1.0.1 in a couple of weeks)

// Rickard

-----BEGIN PGP SIGNATURE-----
Version: 9.8.3 (Build 4028)
Charset: utf-8

wsBVAwUBS16zWOCjgaNTdVjaAQh/XQgAkvNf5waEk1Trz+M87KMVRkW8uojm2JP2
dg1qwGSVa6trmLh2OVmWssCN5ZG96KrtI545js6RMpO1cwVWHsHVxlZ1HcqXYXIs
qrSHkfd8/f7ILhWeCWiMysDY82iYP98DjG5TcFvGNYNn4jO5Ma0+yyc4FnY8qEiY
7y47ITwaLFdbeK0bnZxboF610O6pD5dLksWygTVapHEh6tW1UrLXBWB+O/9n/0GL
ivWAbKILc7Igy8O/wf7USI7dDQjN/naow8M+1DiqrHDVLzICNBVzBBAKidwwVpJ3
CXkpzO76F4g7AZKZbjTlzBY6KwSH2J9QWVlGet9FVksw270Vioghpg==
=/SAh
-----END PGP SIGNATURE-----


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20100126/59db4586/attachment.html>


More information about the Opendnssec-develop mailing list