-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 John McNally wrote:
> Daniel John Debrunner wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> The Apache DB guidelines has this section on branches >> >> [quote] >> Branches >> Groups are allowed to create a branch for release cycles, etc. They are >> expected to merge completely back with the main branch as soon as their >> release cycle is complete. All branches currently in use should be >> documented by the respective projects. >> [end-quote] >> [http://db.apache.org/source.html] >> >> I read that to mean that the branch only exists during the release >> process. I'm not sure that this works well for Derby. >> >> > > You interpretation may be correct, but that would only mean the document > should be better written. The only way I think it would be a valid > statement if it is interpreted as "all applicable patches committed to > the release branch should be ported to the trunk". It makes sense to > leave a release branch available for quick updates for severe bugs or > security issues. > John McNally > So I think we have lazy approval to use stable/release branches as described by John and myself. Dan. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFBYCGqIv0S4qsbfuQRAqIpAJ9PDgmCjWKxr7ATejqubyPwSMYCgwCfZ6aw GM+5a5pMHEYPQ2cSSNYMSIU= =4IQb -----END PGP SIGNATURE-----
