Re: [VOTE] Retire Derby
0 (I abstain. I care about Derby, but I won't have cycles to contribute). Best, Til On 06/10/2025 22:08, Kim Haase via derby-dev wrote: +1 I would like to add that working on documentation for Java DB/Derby for Sun/Oracle from 2006 to 2014 was the best experience of my 35 years as a technical writer, because of the wonderfully collaborative nature of the team, dispersed as it was. Great people, working on a great product. Thank you so much, Rick, for being our leader (technical, not managerial) during those years and for all your great work before and after. Kim Haase (retired 2020) On 10/6/2025 12:10 PM, Rick Hillegas wrote: There being no further discussion of this topic on the developer and user lists, I call a vote. A simple majority carries this procedural question. +1 = Derby should be retired -1 = Derby should not be retired The polls close at 5:00 pm San Francisco time on Friday 2025-10-10.
Re: [VOTE] Retire Derby
I was out of town during the voting period, sorry. My vote, 0, is the same as Tilmann's "I care about Derby, but I won't have cycles to contribute" I do hope people will consider joining the community and taking Derby forward, as there are an enormous amount of interesting ideas that could be incorporated into Derby. However, it's a big effort, too big for just a couple people to attempt in their limited spare time. bryan On Mon, Oct 6, 2025 at 9:11 AM Rick Hillegas wrote: > > There being no further discussion of this topic on the developer and > user lists, I call a vote. A simple majority carries this procedural > question. > > +1 = Derby should be retired > > -1 = Derby should not be retired > > The polls close at 5:00 pm San Francisco time on Friday 2025-10-10. >
Re: [VOTE] Retire Derby
+1 On 10/6/25 9:10 AM, Rick Hillegas wrote: There being no further discussion of this topic on the developer and user lists, I call a vote. A simple majority carries this procedural question. +1 = Derby should be retired -1 = Derby should not be retired The polls close at 5:00 pm San Francisco time on Friday 2025-10-10.
Re: [VOTE] Retire Derby
+1 I would like to add that working on documentation for Java DB/Derby for Sun/Oracle from 2006 to 2014 was the best experience of my 35 years as a technical writer, because of the wonderfully collaborative nature of the team, dispersed as it was. Great people, working on a great product. Thank you so much, Rick, for being our leader (technical, not managerial) during those years and for all your great work before and after. Kim Haase (retired 2020) On 10/6/2025 12:10 PM, Rick Hillegas wrote: There being no further discussion of this topic on the developer and user lists, I call a vote. A simple majority carries this procedural question. +1 = Derby should be retired -1 = Derby should not be retired The polls close at 5:00 pm San Francisco time on Friday 2025-10-10.
Re: [VOTE] Retire Derby
0 (I abstain. I care about Derby, but I won't have cycles to contribute). Best, Til On 06/10/2025 22:08, Kim Haase via derby-dev wrote: +1 I would like to add that working on documentation for Java DB/Derby for Sun/Oracle from 2006 to 2014 was the best experience of my 35 years as a technical writer, because of the wonderfully collaborative nature of the team, dispersed as it was. Great people, working on a great product. Thank you so much, Rick, for being our leader (technical, not managerial) during those years and for all your great work before and after. Kim Haase (retired 2020) On 10/6/2025 12:10 PM, Rick Hillegas wrote: There being no further discussion of this topic on the developer and user lists, I call a vote. A simple majority carries this procedural question. +1 = Derby should be retired -1 = Derby should not be retired The polls close at 5:00 pm San Francisco time on Friday 2025-10-10.
