You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by Daniel John Debrunner <dj...@debrunners.com> on 2004/09/27 21:47:55 UTC
[VOTE] Derby upgrade policy
-----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/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
iD8DBQFBWG5rIv0S4qsbfuQRAmxkAJ9ePo998kjv48sPqD93iq2lOiBFUwCg4/Tw
A+mIS9R0yaBWCAO62N4v3qw=
=gHou
-----END PGP SIGNATURE-----
Re: [VOTE] Derby upgrade policy
Posted by Jalud Abdulmenan <te...@rogers.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
+1
Jalud,
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 Thunderbird - http://enigmail.mozdev.org
iD8DBQFBWks+2MOhC3LM/1oRAhiKAKC5xMXCKtrC87u7wOC3W3aSm+SwXgCfaDmp
CwO4J9Js38oCsr0j0ILJMRc=
=mphw
-----END PGP SIGNATURE-----
[VOTE] [RESULT] Derby upgrade policy
Posted by Daniel John Debrunner <dj...@debrunners.com>.
-----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-----
Re: [VOTE] Derby upgrade policy
Posted by Kathey Marsden <km...@Sourcery.Org>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
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.
>
+1
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBWd5RG0h36bFmkocRAuSoAKCdIyOXdGv2EN8J8CMHMSAfHm0YQwCfbom6
QyJtPRXVWx66I30SHVUFObs=
=k+Wa
-----END PGP SIGNATURE-----