Re: next derby release

2020-01-08 Thread Bryan Pendleton
+1 to a 10.15.2 maintenance release.

I have no particular opinion about Java 9 versus Java 11 (in many of
my environments I am still using Java 8/Derby 10.14 quite
successfully, in fact.)

bryan

On Sun, Jan 5, 2020 at 10:47 AM Davide Grandi  wrote:
>
> May be
> 10.15.2  realeased with Java 9
> 10.15.3-SNAPSHOT in development with Java 11 (or whatever is the next
>   development name)
> ?
>
> Bye,
>
>  Davide
>
> On 05/01/2020 18:48, Rick Hillegas wrote:
> > It's been a year since we produced a Derby release. No significant
> > feature work has gone into the code since then. But I would be happy to
> > manage a 10.15.2 maintenance release in order to roll up the handful of
> > bug fixes which have accumulated over the last year.
> >
> > The only reason I can see for a new feature release would be to advance
> > the minimal JVM version to the Java 11 LTS version. According to
> > convention, this would require a vote by the community. I am not
> > planning any work over the next year which would require Java 11
> > features, so I don't personally see any compelling reason for advancing
> > the JVM version.
> >
> > What are your thoughts?
> >
> > Thanks,
> >
> > -Rick
>
> --
> Ing. Davide Grandi
> email  : davide.gra...@email.it
> mobile : +39 339 7468 778


Re: next derby release

2020-01-05 Thread Davide Grandi

May be
10.15.2  realeased with Java 9
10.15.3-SNAPSHOT in development with Java 11 (or whatever is the next
 development name)
?

Bye,

Davide

On 05/01/2020 18:48, Rick Hillegas wrote:
It's been a year since we produced a Derby release. No significant 
feature work has gone into the code since then. But I would be happy to 
manage a 10.15.2 maintenance release in order to roll up the handful of 
bug fixes which have accumulated over the last year.


The only reason I can see for a new feature release would be to advance 
the minimal JVM version to the Java 11 LTS version. According to 
convention, this would require a vote by the community. I am not 
planning any work over the next year which would require Java 11 
features, so I don't personally see any compelling reason for advancing 
the JVM version.


What are your thoughts?

Thanks,

-Rick


--
Ing. Davide Grandi
email  : davide.gra...@email.it
mobile : +39 339 7468 778


Re: next derby release

2017-06-19 Thread Rick Hillegas
Thanks, Bryan. I am leaning toward a 10.14.1 feature release for two 
reasons:


1) We have at least one new feature which requires hard-upgrade.

2) The 10.14.1 release notes can serve as our announcement that we are 
sunsetting support for Java 8 in the next (10.15.1) release.


I have updated the wiki front page to note that we are working on a 
10.14.1 feature release: https://wiki.apache.org/db-derby/FrontPage.


Please use the 10.14.1 release-planning page 
(https://wiki.apache.org/db-derby/DerbyTenFourteenOneRelease) to 
describe any additional features or important bug-fixes which you think 
the release notes should mention.


Thanks,
-Rick


On 6/18/17 3:31 PM, Bryan Pendleton wrote:

I, too, would like to see a Derby release prior to summer 2018.

I am comfortable with either proposal.

Thanks for volunteering to make this happen! I'll chip in as much as I 
can.


bryan





Re: next derby release

2017-06-18 Thread Bryan Pendleton
I, too, would like to see a Derby release prior to summer 2018.

I am comfortable with either proposal.

Thanks for volunteering to make this happen! I'll chip in as much as I can.

bryan


Re: next derby release

2017-06-17 Thread Rick Hillegas
Alternatively, we could produce a 10.14.1 release which exposes the 
recent work on autoincrement columns. The JDK9-focussed release could be 
called 10.15.1.


On 6/17/17 8:11 AM, Rick Hillegas wrote:
Someone on the user list has asked about our plans for upcoming 
releases. Here are my thoughts:


o I was planning on managing a 10.14.1 release which would build and 
run cleanly on JDK 9. The idea would be that the code would not build 
or run on previous versions of the JDK, due to our limited resources 
and the complexity of building on multiple JDKs. I feel that it would 
be too risky to release 10.14.1 right after JDK 9 goes GA on 
2017-09-21 (see 
http://mail.openjdk.java.net/pipermail/jdk9-dev/2017-June/005867.html). 
I would want to wait for the first maintenance release of JDK 9, which 
would probably come a couple quarters later. That means a GA for 
10.14.1 sometime in 2018.


o That's too long to wait for a new Derby release. I think that we 
need a 10.13.2 maintenance release in the interim. I have created a 
webpage to track that effort: 
https://wiki.apache.org/db-derby/DerbyTenThirteenTwoRelease


I am happy to volunteer to manage a 10.13.2 release sometime in 
September. I'm also happy if someone else wants to volunteer to manage 
the release for an earlier date.


Does anyone have opinions about what would motivate an earlier vs. 
later date?


Thanks,

-Rick