You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@netbeans.apache.org by Arvind Aprameya <ar...@oracle.com> on 2020/08/18 04:34:26 UTC
nb-javac version 15 release schedule.
Hi All,
Based on the current outlook, below table has the plan for releasing nb-javac 15 versions, let me know if this looks fine with you all.
nb-javac release Roadmap
Supported OpenJDK Version(Release date)
nb-javac Release Version
nb-javac Release timeline
NetBeans Version where nb-javac can be integrated (timeline)
JDK 15 (mid Sep 2020)
nb-javac-15-impl.jar & nb-javac-15-api.jar
Oct 2020
12.2 (Nov 2020)
JDK 15.0.1
nb-javac-15.1-impl.jar & nb-javac-15.1-api.jar
Nov 2020
12.2 (Nov 2020)
JDK 15.0.2
nb-javac-15.2-impl.jar & nb-javac-15.2-api.jar
Feb 2021
12.3( Feb 2021)
A schedule for nb-javac version 16 will be shared once the schedule for OpenJDK 16 is available on the OpenJDK site .
regards,
Arvind
Re: nb-javac version 15 release schedule.
Posted by Arvind Aprameya <ar...@oracle.com>.
Please find my comments inline
On 8/26/2020 9:19 PM, Neil C Smith wrote:
> On Tue, 25 Aug 2020 at 06:21, Arvind Aprameya
> <ar...@oracle.com> wrote:
>> Neil please find my responses inline.
> Thanks. Same ..
>
>> On 8/18/2020 7:15 PM, Neil C Smith wrote:
>>> I think, if we are to continue delivering nb-javac to NetBeans then we
>>> need to ensure support lands in master before freeze dates, ideally at
>>> least a couple of weeks before, so that teething problems can be
>>> ironed out before beta1.
>>>
>>> Which would leave us, by your schedule, needing nb-javac-15 to be
>>> ready for ~Oct 1st and nb-javac-15.2 to be ready for ~Feb 1st. Are
>>> those realistic?
>> Oct 1st for nb-javac-15 seems workable, however at the moment I am not
>> certain if we can make 1st Feb for nb-javac-15.2
> I see no-one picked up the "deliberate" mistake there! :-) Mixing up
> old and new schedules.
>
> Assuming we continue with what we have now as per
> https://urldefense.com/v3/__https://cwiki.apache.org/confluence/display/NETBEANS/Release*Schedule__;Kw!!GqivPVa7Brio!L7qmJUPuCgrZDbeUy_j0s2CCBvkZt2zu8mD1Cbacytb0WNuALAym1k3AxOFDk8SCqTDW$
>
> NetBeans 12.2
> Freeze date : Oct 15th
> Release date : Nov 15-30th
>
> NetBeans 12.3
> Freeze date : Jan 15th
> Release date : Feb 15th-30th(!)
>
> NetBeans 13.0 LTS
> Freeze date : Mar 15th
> Release date : May 15th-30th
>
> Which would leave us ideally having nb-javac ready for -
>
> nb-javac-15 : Oct 1st
> nb-javac-15.1 : Jan 1st
These look fine to me, just so we are on the same page nb-javac-15.1
will be the update from OpenJDK 15.0.1.
> nb-javac-16 : Mar 1st
> nb-javac-16.1 : Jul 1st
There is no schedule posted yet for JDK 16 on
https://openjdk.java.net/projects/jdk/16/ . Assuming a JDK 16 release
during March 2021, and adding some time for integration testing/
validation etc a potential tentative timeline that we could look at
could be sometime in April 2021, depending on the actual JDK 16 release
date.
I do understand that NB 13 being an LTS and NetCAT validation needs to
begin early but a from nb-javac perspective a freeze date around early
May would be preferable.
>
> How feasible? Do we need to rethink how we schedule nb-javac
> inclusion related to NetBeans releases?
>
> I guess a potential issue might come with the earlier freeze date for
> the next LTS (March) if we stick with the current release plan?
Yes, please see my comments above.
> Do we
> expect NB 13.0 to ship with JDK 16 support?
IMO, NB 13 shipping with JDK 16 support would be very welcome since it
would then be relevant.
>
>> These updates would synchronize nb-javac with the javac source code from
>> the corresponding JDK updates, thereby picking up any relevant changes,
>> e.g. critical bug fixes./
> Agreed, but as above wondering (unless we change how nb-javac is
> delivered) about keeping the patch updates synced to NetBeans feature
> releases, and backport to LTS if critical, wherever possible?
Sorry, I did not really understand this one.
> Obviously there might be a need to deliver unplanned critical fixes,
> just wondering about the need to have planned ones, particularly if on
> a different release schedule.
>
>> Currently the source code is present in
>> https://hg.netbeans.org/main/nb-java-x/, and the step-by-step building
>> instructions are present in "readme.md" file.
> Thanks. Given other legacy things we're redirecting to being closed
> down, what is the long term plan for that repository? Could it also
> be mirrored elsewhere, more open to others to potentially work with /
> on too?
There is an effort underway towards migrating this repo, I shall keep
you posted as and when we make good progress.
> The above comments are mainly from my release management perspective.
Totally understandable !
regards,
Arvind
> Be good to get other input on plans here, particularly given different
> thoughts on long term nb-javac plans?
>
> Best wishes,
>
> Neil
--
regards, Arvind
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: nb-javac version 15 release schedule.
Posted by Neil C Smith <ne...@apache.org>.
On Tue, 25 Aug 2020 at 06:21, Arvind Aprameya
<ar...@oracle.com> wrote:
> Neil please find my responses inline.
Thanks. Same ..
> On 8/18/2020 7:15 PM, Neil C Smith wrote:
> > I think, if we are to continue delivering nb-javac to NetBeans then we
> > need to ensure support lands in master before freeze dates, ideally at
> > least a couple of weeks before, so that teething problems can be
> > ironed out before beta1.
> >
> > Which would leave us, by your schedule, needing nb-javac-15 to be
> > ready for ~Oct 1st and nb-javac-15.2 to be ready for ~Feb 1st. Are
> > those realistic?
> Oct 1st for nb-javac-15 seems workable, however at the moment I am not
> certain if we can make 1st Feb for nb-javac-15.2
I see no-one picked up the "deliberate" mistake there! :-) Mixing up
old and new schedules.
Assuming we continue with what we have now as per
https://cwiki.apache.org/confluence/display/NETBEANS/Release+Schedule
NetBeans 12.2
Freeze date : Oct 15th
Release date : Nov 15-30th
NetBeans 12.3
Freeze date : Jan 15th
Release date : Feb 15th-30th(!)
NetBeans 13.0 LTS
Freeze date : Mar 15th
Release date : May 15th-30th
Which would leave us ideally having nb-javac ready for -
nb-javac-15 : Oct 1st
nb-javac-15.1 : Jan 1st
nb-javac-16 : Mar 1st
nb-javac-16.1 : Jul 1st
How feasible? Do we need to rethink how we schedule nb-javac
inclusion related to NetBeans releases?
I guess a potential issue might come with the earlier freeze date for
the next LTS (March) if we stick with the current release plan? Do we
expect NB 13.0 to ship with JDK 16 support?
> These updates would synchronize nb-javac with the javac source code from
> the corresponding JDK updates, thereby picking up any relevant changes,
> e.g. critical bug fixes./
Agreed, but as above wondering (unless we change how nb-javac is
delivered) about keeping the patch updates synced to NetBeans feature
releases, and backport to LTS if critical, wherever possible?
Obviously there might be a need to deliver unplanned critical fixes,
just wondering about the need to have planned ones, particularly if on
a different release schedule.
> Currently the source code is present in
> https://hg.netbeans.org/main/nb-java-x/, and the step-by-step building
> instructions are present in "readme.md" file.
Thanks. Given other legacy things we're redirecting to being closed
down, what is the long term plan for that repository? Could it also
be mirrored elsewhere, more open to others to potentially work with /
on too?
The above comments are mainly from my release management perspective.
Be good to get other input on plans here, particularly given different
thoughts on long term nb-javac plans?
Best wishes,
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: nb-javac version 15 release schedule.
Posted by Arvind Aprameya <ar...@oracle.com>.
Neil please find my responses inline.
On 8/18/2020 7:15 PM, Neil C Smith wrote:
> On Tue, 18 Aug 2020 at 05:34, Arvind Aprameya
> <ar...@oracle.com> wrote:
>> Based on the current outlook, below table has the plan for releasing nb-javac 15 versions, let me know if this looks fine with you all.
> Thanks for this. I'd planned to start a thread on nb-javac after 12.1
> is out, from a release manager perspective with 12.1 and 11.2 in
> particular.
>
> Obviously JDK schedule is important here, but so is ours, and with
> both 12.1 and particularly 11.2, the delay in integrating nb-javac for
> testing has caused real problems.
>
> I think, if we are to continue delivering nb-javac to NetBeans then we
> need to ensure support lands in master before freeze dates, ideally at
> least a couple of weeks before, so that teething problems can be
> ironed out before beta1.
>
> Which would leave us, by your schedule, needing nb-javac-15 to be
> ready for ~Oct 1st and nb-javac-15.2 to be ready for ~Feb 1st. Are
> those realistic?
Oct 1st for nb-javac-15 seems workable, however at the moment I am not
certain if we can make 1st Feb for nb-javac-15.2
> I'm not sure if we want to deliver nb-javac-15.1 - ideally we wouldn't
> need to push an update for it while it's packaged as currently.
> What's the thought behind that? Maybe we need to consider whether it
> can be delivered via plugin portal again, or if current discussions on
> CPE allow and we can guarantee it's all under CPE we might be able to
> ship directly in one module?
_//_The primary reason for these patches are to be able to make changes
from javac into nb-javac.
These updates would synchronize nb-javac with the javac source code from
the corresponding JDK updates, thereby picking up any relevant changes,
e.g. critical bug fixes./
/
> With any of the above, it would be good to improve access to the
> source code and building instructions from a license compliance
> point-of-view.
Currently the source code is present in
https://hg.netbeans.org/main/nb-java-x/, and the step-by-step building
instructions are present in "readme.md" file.
regards,
arvind
>
> Best wishes,
>
> Neil
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://urldefense.com/v3/__https://cwiki.apache.org/confluence/display/NETBEANS/Mailing*lists__;Kw!!GqivPVa7Brio!Jv6grta7RQX33e9_Y4f2nXA9Xcd50_4ReGZe1MzjLkXoYUPErJM0nJIxcDrSWUGBfqon$
>
>
>
--
regards, Arvind
Re: nb-javac version 15 release schedule.
Posted by Neil C Smith <ne...@apache.org>.
On Tue, 18 Aug 2020 at 05:34, Arvind Aprameya
<ar...@oracle.com> wrote:
> Based on the current outlook, below table has the plan for releasing nb-javac 15 versions, let me know if this looks fine with you all.
Thanks for this. I'd planned to start a thread on nb-javac after 12.1
is out, from a release manager perspective with 12.1 and 11.2 in
particular.
Obviously JDK schedule is important here, but so is ours, and with
both 12.1 and particularly 11.2, the delay in integrating nb-javac for
testing has caused real problems.
I think, if we are to continue delivering nb-javac to NetBeans then we
need to ensure support lands in master before freeze dates, ideally at
least a couple of weeks before, so that teething problems can be
ironed out before beta1.
Which would leave us, by your schedule, needing nb-javac-15 to be
ready for ~Oct 1st and nb-javac-15.2 to be ready for ~Feb 1st. Are
those realistic?
I'm not sure if we want to deliver nb-javac-15.1 - ideally we wouldn't
need to push an update for it while it's packaged as currently.
What's the thought behind that? Maybe we need to consider whether it
can be delivered via plugin portal again, or if current discussions on
CPE allow and we can guarantee it's all under CPE we might be able to
ship directly in one module?
With any of the above, it would be good to improve access to the
source code and building instructions from a license compliance
point-of-view.
Best wishes,
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists