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 Rick Hillegas <Ri...@Sun.COM> on 2005/08/08 22:38:16 UTC
[VOTE] Policy for supported platforms
No-one on the user list has objected to the proposed sunsetting policy
for jdk 1.3. Therefore I'm cautiously hopeful that we can move forward
with a vote. Let's wrap up the voting by Friday evening (12 August, 2005).
Thanks,
-Rick
> Please vote on the following proposed policy for Derby's supported
> platforms. Mostly, this proposal merely restates the current policy.
> Changes are flagged.
>
> o 10.2 will be the LAST Derby release which runs on jdk 1.3 and
> supports JDBC 2.0.
> THIS IS A CHANGE FROM CURRENT POLICY.
>
> o 10.2 will run on the following platforms:
>
> - J2ME/CDC/Foundation 1.0 (exposing the JDBC subset in JSR 169)
> - 1.3.x (exposing JDBC 2.0)
> - 1.4.x and 1.5.x (exposing JDBC 3.0)
> - 1.6 beta (exposing JDBC 4.0) THIS IS A CHANGE FROM CURRENT POLICY.
>
> o To build 10.2, you MUST have the 1.3 and 1.4 sdks.
>
> o The 10.2 build will expose an optional target for building JDBC 4.0
> support. To use this target, you must have a 1.6 sdk. THIS IS A CHANGE.
>
>
>
Re: [VOTE] Policy for supported platforms
Posted by Shreyas Kaushik <Sh...@Sun.COM>.
+1
Lance J. Andersen wrote:
> +1
>
> Rick Hillegas wrote:
>
>> +1
>>
>> Rick Hillegas wrote:
>>
>>> No-one on the user list has objected to the proposed sunsetting
>>> policy for jdk 1.3. Therefore I'm cautiously hopeful that we can
>>> move forward with a vote. Let's wrap up the voting by Friday evening
>>> (12 August, 2005).
>>>
>>> Thanks,
>>> -Rick
>>>
>>>> Please vote on the following proposed policy for Derby's supported
>>>> platforms. Mostly, this proposal merely restates the current
>>>> policy. Changes are flagged.
>>>>
>>>> o 10.2 will be the LAST Derby release which runs on jdk 1.3 and
>>>> supports JDBC 2.0.
>>>> THIS IS A CHANGE FROM CURRENT POLICY.
>>>>
>>>> o 10.2 will run on the following platforms:
>>>>
>>>> - J2ME/CDC/Foundation 1.0 (exposing the JDBC subset in JSR 169)
>>>> - 1.3.x (exposing JDBC 2.0)
>>>> - 1.4.x and 1.5.x (exposing JDBC 3.0)
>>>> - 1.6 beta (exposing JDBC 4.0) THIS IS A CHANGE FROM CURRENT POLICY.
>>>>
>>>> o To build 10.2, you MUST have the 1.3 and 1.4 sdks.
>>>>
>>>> o The 10.2 build will expose an optional target for building JDBC 4.0
>>>> support. To use this target, you must have a 1.6 sdk. THIS IS A
>>>> CHANGE.
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
Re: [VOTE] Policy for supported platforms
Posted by Francois Orsini <fr...@gmail.com>.
In theory, a 10.2 level Derby release would not need/have to be
recompiled if the JARs are available for download - hence we are
saying that we will still support a 10.2 release running with jdk/jre
1.3, right? 1.3 is kinda ancient as we know...
+1
On 8/10/05, Lance J. Andersen <La...@sun.com> wrote:
> +1
>
> Rick Hillegas wrote:
>
> > +1
> >
> > Rick Hillegas wrote:
> >
> >> No-one on the user list has objected to the proposed sunsetting
> >> policy for jdk 1.3. Therefore I'm cautiously hopeful that we can
> >> move forward with a vote. Let's wrap up the voting by Friday evening
> >> (12 August, 2005).
> >>
> >> Thanks,
> >> -Rick
> >>
> >>> Please vote on the following proposed policy for Derby's supported
> >>> platforms. Mostly, this proposal merely restates the current policy.
> >>> Changes are flagged.
> >>>
> >>> o 10.2 will be the LAST Derby release which runs on jdk 1.3 and
> >>> supports JDBC 2.0.
> >>> THIS IS A CHANGE FROM CURRENT POLICY.
> >>>
> >>> o 10.2 will run on the following platforms:
> >>>
> >>> - J2ME/CDC/Foundation 1.0 (exposing the JDBC subset in JSR 169)
> >>> - 1.3.x (exposing JDBC 2.0)
> >>> - 1.4.x and 1.5.x (exposing JDBC 3.0)
> >>> - 1.6 beta (exposing JDBC 4.0) THIS IS A CHANGE FROM CURRENT POLICY.
> >>>
> >>> o To build 10.2, you MUST have the 1.3 and 1.4 sdks.
> >>>
> >>> o The 10.2 build will expose an optional target for building JDBC 4.0
> >>> support. To use this target, you must have a 1.6 sdk. THIS IS A
> >>> CHANGE.
> >>>
> >>>
> >>>
> >>
> >>
> >
> >
>
Re: [VOTE] Policy for supported platforms
Posted by "Lance J. Andersen" <La...@Sun.COM>.
+1
Rick Hillegas wrote:
> +1
>
> Rick Hillegas wrote:
>
>> No-one on the user list has objected to the proposed sunsetting
>> policy for jdk 1.3. Therefore I'm cautiously hopeful that we can
>> move forward with a vote. Let's wrap up the voting by Friday evening
>> (12 August, 2005).
>>
>> Thanks,
>> -Rick
>>
>>> Please vote on the following proposed policy for Derby's supported
>>> platforms. Mostly, this proposal merely restates the current policy.
>>> Changes are flagged.
>>>
>>> o 10.2 will be the LAST Derby release which runs on jdk 1.3 and
>>> supports JDBC 2.0.
>>> THIS IS A CHANGE FROM CURRENT POLICY.
>>>
>>> o 10.2 will run on the following platforms:
>>>
>>> - J2ME/CDC/Foundation 1.0 (exposing the JDBC subset in JSR 169)
>>> - 1.3.x (exposing JDBC 2.0)
>>> - 1.4.x and 1.5.x (exposing JDBC 3.0)
>>> - 1.6 beta (exposing JDBC 4.0) THIS IS A CHANGE FROM CURRENT POLICY.
>>>
>>> o To build 10.2, you MUST have the 1.3 and 1.4 sdks.
>>>
>>> o The 10.2 build will expose an optional target for building JDBC 4.0
>>> support. To use this target, you must have a 1.6 sdk. THIS IS A
>>> CHANGE.
>>>
>>>
>>>
>>
>>
>
>
Re: [VOTE] Policy for supported platforms
Posted by Rick Hillegas <Ri...@Sun.COM>.
+1
Rick Hillegas wrote:
> No-one on the user list has objected to the proposed sunsetting policy
> for jdk 1.3. Therefore I'm cautiously hopeful that we can move
> forward with a vote. Let's wrap up the voting by Friday evening (12
> August, 2005).
>
> Thanks,
> -Rick
>
>> Please vote on the following proposed policy for Derby's supported
>> platforms. Mostly, this proposal merely restates the current policy.
>> Changes are flagged.
>>
>> o 10.2 will be the LAST Derby release which runs on jdk 1.3 and
>> supports JDBC 2.0.
>> THIS IS A CHANGE FROM CURRENT POLICY.
>>
>> o 10.2 will run on the following platforms:
>>
>> - J2ME/CDC/Foundation 1.0 (exposing the JDBC subset in JSR 169)
>> - 1.3.x (exposing JDBC 2.0)
>> - 1.4.x and 1.5.x (exposing JDBC 3.0)
>> - 1.6 beta (exposing JDBC 4.0) THIS IS A CHANGE FROM CURRENT POLICY.
>>
>> o To build 10.2, you MUST have the 1.3 and 1.4 sdks.
>>
>> o The 10.2 build will expose an optional target for building JDBC 4.0
>> support. To use this target, you must have a 1.6 sdk. THIS IS A
>> CHANGE.
>>
>>
>>
>
>
Re: [VOTE] Policy for supported platforms
Posted by Rick Hillegas <Ri...@Sun.COM>.
Thanks, Andrew.
-Rick
Andrew McIntyre wrote:
>On 8/16/05, Rick Hillegas <Ri...@sun.com> wrote:
>
>
>>Hi Andrew,
>>
>>I've made the following changes to STATUS, which I'm submitting in the
>>attached diff file:
>>
>>1) Reworded the preamble to indicate that Derby is a full-fledged Apache
>>DB project.
>>
>>2) Listed 10.1.1.0 as released.
>>
>>3) Noted our graduation.
>>
>>4) Recorded the platform support vote.
>>
>>
>
>Committed revision 233074. Thanks for helping keep STATUS up to date!
>
>
>
>>I didn't know what you meant about listing the new committers (Bernt,
>>Oyvind, and David). They are already at the end of the committer list.
>>
>>
>
>I think I was looking at an outdated copy, sorry.
>
>
>
>>By the way, does anyone know what the "type" column in the "Detailed
>>references" table means? For the original committers, this
>>column holds some kind of login name or abbreviation which, at least in
>>some cases, isn't the individual's JIRA id. Currently, this
>>column is blank for the new committers.
>>
>>
>
>The type column is from a table on the original Derby page at the
>Incubator website. That info is archived at
>http://incubator.apache.org/projects/derby.html. Now that we've
>graduated from the Incubator, most of the incubation status info at
>the top of STATUS can go, including this section. I'll leave that for
>the next person who updates the file.
>
>cheers,
>andrew
>
>
Re: [VOTE] Policy for supported platforms
Posted by Andrew McIntyre <mc...@gmail.com>.
On 8/16/05, Rick Hillegas <Ri...@sun.com> wrote:
> Hi Andrew,
>
> I've made the following changes to STATUS, which I'm submitting in the
> attached diff file:
>
> 1) Reworded the preamble to indicate that Derby is a full-fledged Apache
> DB project.
>
> 2) Listed 10.1.1.0 as released.
>
> 3) Noted our graduation.
>
> 4) Recorded the platform support vote.
Committed revision 233074. Thanks for helping keep STATUS up to date!
> I didn't know what you meant about listing the new committers (Bernt,
> Oyvind, and David). They are already at the end of the committer list.
I think I was looking at an outdated copy, sorry.
> By the way, does anyone know what the "type" column in the "Detailed
> references" table means? For the original committers, this
> column holds some kind of login name or abbreviation which, at least in
> some cases, isn't the individual's JIRA id. Currently, this
> column is blank for the new committers.
The type column is from a table on the original Derby page at the
Incubator website. That info is archived at
http://incubator.apache.org/projects/derby.html. Now that we've
graduated from the Incubator, most of the incubation status info at
the top of STATUS can go, including this section. I'll leave that for
the next person who updates the file.
cheers,
andrew
[RESULT] [VOTE] Policy for supported platforms
Posted by Rick Hillegas <Ri...@Sun.COM>.
This proposal also passed. Oddly enough, the result is recorded in
STATUS and at http://wiki.apache.org/db-derby/VoteResults.
Cheers,
-Rick
Re: [VOTE] Policy for supported platforms
Posted by Rick Hillegas <Ri...@Sun.COM>.
Hi Andrew,
I've made the following changes to STATUS, which I'm submitting in the
attached diff file:
1) Reworded the preamble to indicate that Derby is a full-fledged Apache
DB project.
2) Listed 10.1.1.0 as released.
3) Noted our graduation.
4) Recorded the platform support vote.
I didn't know what you meant about listing the new committers (Bernt,
Oyvind, and David). They are already at the end of the committer list.
By the way, does anyone know what the "type" column in the "Detailed
references" table means? For the original committers, this
column holds some kind of login name or abbreviation which, at least in
some cases, isn't the individual's JIRA id. Currently, this
column is blank for the new committers.
Thanks in advance to some industrious committer for checking in these
changes,
-Rick
Andrew McIntyre wrote:
>
> On Aug 15, 2005, at 12:16 PM, Rick Hillegas wrote:
>
>> For the record, this proposal passed with four +1 votes and no other
>> votes:
>>
>> Lance Andersen
>> Rick Hillegas
>> Shreyas Kaushik
>> Francois Orsini
>>
>> Does someone (maybe me?) need to inscribe/enshrine/link/post this fact?
>
>
> The mailing list archives will preserve the decision for posterity.
>
> This is also just the sort of thing that is good to have in the
> STATUS file at the top of the tree. If anyone has some time to update
> it, it would be good to record our recent graduation from the
> Incubator, addition of new committers (just the votes are currently
> recorded there), the recent release of 10.1, and recent voting
> activity such as this into STATUS.
>
> I won't have time to update it till later this week, maybe not till
> next week, but if some industrious Derby developer takes the time to
> produce a patch to update the STATUS file, I'm sure one of the
> committers will give it their immediate attention. (hint, hint)
>
> andrew
>
Re: [VOTE] Policy for supported platforms
Posted by Andrew McIntyre <mc...@gmail.com>.
On Aug 15, 2005, at 12:16 PM, Rick Hillegas wrote:
> For the record, this proposal passed with four +1 votes and no
> other votes:
>
> Lance Andersen
> Rick Hillegas
> Shreyas Kaushik
> Francois Orsini
>
> Does someone (maybe me?) need to inscribe/enshrine/link/post this
> fact?
The mailing list archives will preserve the decision for posterity.
This is also just the sort of thing that is good to have in the
STATUS file at the top of the tree. If anyone has some time to update
it, it would be good to record our recent graduation from the
Incubator, addition of new committers (just the votes are currently
recorded there), the recent release of 10.1, and recent voting
activity such as this into STATUS.
I won't have time to update it till later this week, maybe not till
next week, but if some industrious Derby developer takes the time to
produce a patch to update the STATUS file, I'm sure one of the
committers will give it their immediate attention. (hint, hint)
andrew
Re: [VOTE] Policy for supported platforms
Posted by Daniel John Debrunner <dj...@debrunners.com>.
Rick Hillegas wrote:
> For the record, this proposal passed with four +1 votes and no other votes:
Tradition is to change the subject for a result of a vote to be
[RESULT] [VOTE] <subject of vote>
i.e. in this case
[RESULT] [VOTE] Policy for supported platforms
Dan.
Re: [VOTE] Policy for supported platforms
Posted by Rick Hillegas <Ri...@Sun.COM>.
For the record, this proposal passed with four +1 votes and no other votes:
Lance Andersen
Rick Hillegas
Shreyas Kaushik
Francois Orsini
Does someone (maybe me?) need to inscribe/enshrine/link/post this fact?
Thanks,
-Rick
Rick Hillegas wrote:
> No-one on the user list has objected to the proposed sunsetting policy
> for jdk 1.3. Therefore I'm cautiously hopeful that we can move
> forward with a vote. Let's wrap up the voting by Friday evening (12
> August, 2005).
>
> Thanks,
> -Rick
>
>> Please vote on the following proposed policy for Derby's supported
>> platforms. Mostly, this proposal merely restates the current policy.
>> Changes are flagged.
>>
>> o 10.2 will be the LAST Derby release which runs on jdk 1.3 and
>> supports JDBC 2.0.
>> THIS IS A CHANGE FROM CURRENT POLICY.
>>
>> o 10.2 will run on the following platforms:
>>
>> - J2ME/CDC/Foundation 1.0 (exposing the JDBC subset in JSR 169)
>> - 1.3.x (exposing JDBC 2.0)
>> - 1.4.x and 1.5.x (exposing JDBC 3.0)
>> - 1.6 beta (exposing JDBC 4.0) THIS IS A CHANGE FROM CURRENT POLICY.
>>
>> o To build 10.2, you MUST have the 1.3 and 1.4 sdks.
>>
>> o The 10.2 build will expose an optional target for building JDBC 4.0
>> support. To use this target, you must have a 1.6 sdk. THIS IS A
>> CHANGE.
>>
>>
>>
>
>