db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel John Debrunner <...@debrunners.com>
Subject [VOTE] [RESULT] Derby upgrade policy
Date Sun, 03 Oct 2004 15:37:26 GMT
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Passed, three +1 votes.

Dan.


Daniel John Debrunner wrote:

> [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/ReadMsg?listName=derby-dev@db.apache.org&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

iD8DBQFBYBy2Iv0S4qsbfuQRAnpgAJ9SdzkwHx0iH5Q3SmqkSb3SFQrDfACgrI4N
7g6HwxmazLLB8LEqTWkHe4M=
=QVJK
-----END PGP SIGNATURE-----


Mime
View raw message