-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [in the Thoughts on a release thread]
Kathey Marsden wrote: > I suggest adding: > > 5) A consensus is reached on the Derby upgrade policy. To address this I propose a vote to accept that for any release of Derby the upgrade policy described in http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]&msgNo=77 is followed. The summary is that any release of Derby can run against a database created by a previous release with either no upgrade, soft upgrade or hard upgrade mode, depending on the circumstance. This would mean that if some new feature was added to Derby, before a release occurred the correct upgrade code would have to be written, if the feature contributor did not provide it. My vote: +1 Dan. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFBWG5rIv0S4qsbfuQRAmxkAJ9ePo998kjv48sPqD93iq2lOiBFUwCg4/Tw A+mIS9R0yaBWCAO62N4v3qw= =gHou -----END PGP SIGNATURE-----
