Well note for the clarification, Geertjan.
Thanks
Kai
On 5/6/2019 3:41 PM, Geertjan Wielenga wrote:
Well, just note, it’s not the donation of Payara, but the donation and
integration of the source files that define the plugin providing usage of
Payara from Apache NetBeans.
But, indeed, excellent news. :-)
Gj
On Mon, 6 May 2019 at 15:37, Kai Uwe Pel <kaiuwe...@asia.com> wrote:
Wow! That's really an amazing update! Thanks for the donation of Payara!
Much appreciated!
Thanks
Kai
On 5/6/2019 2:36 PM, Gaurav Gupta wrote:
Hi all,
Yes, We @ Payara planned for donation of both Payara Server and Payara
Micro plugins to Apache NetBeans IDE before the end of May month with
Payara upcoming release 5.192 & JDK 11 support.
*** Payara Server plugin is a patched, enhanced, and derived from
GlassFish
Server plugins bundled in NetBeans IDE 8.2.*
Thanks and kind regards,
Gaurav Gupta
On Mon, May 6, 2019 at 12:10 AM Geertjan Wielenga <geert...@apache.org>
wrote:
On Sun, 5 May 2019 at 18:51, Neil C Smith <neilcsm...@apache.org>
wrote:
Hi,
On Sun, 5 May 2019 at 16:32, Geertjan Wielenga <geert...@apache.org>
wrote:
Regardless of who becomes the next release manager, can we get an easy
view
into which pull requests will be part of the release?
IMO, if we're doing this June release we should be freezing master at
the end of May and releasing whatever is there as NB12. And fixing
that date as soon as possible so there's an advertised time to fix up
any desired PR's for that release. Cherry-picking things to include,
Just for clarity — I’m not cherry picking, instead, what I’m trying to
establish is a list of features, enhancements, and fixes that we already
know will be part of the June release.
or deciding now whether it counts as "major" or "minor", seems counter
to doing time-based releases.
So, you’re saying it will definitely be Apache NetBeans 12?
I’m asking because I’d like to start putting a release page together on
the
Wiki and I’d also like to know what NetCAT should be focused on.
Thanks,
Gj
And I still think it would be good to freeze master at branch point
for anything other than fixes intended for the next release, and run
merge windows for new features after the releases are done.
I'd be happy to consider being release manager this time around, as
discussed last time, if we do something along these lines. I'm not so
keen to release manage with further cherry picking on to the
release110 branch. If it's purely about bug fixes / improvements on
select modules, can't they be done separately via the update centre?
Best wishes,
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
