You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@netbeans.apache.org by Geertjan Wielenga <ge...@googlemail.com.INVALID> on 2018/06/19 11:53:36 UTC
Next release can be put together, volunteer for next release manager needed.
Hi all,
We're coming very close IMHO to the final release of Apache NetBeans 9.0,
i.e., the Java SE IDE (without the 2nd donation code, which is now very
close to being here but we shouldn't wait for that, i.e., JEE, JavaScript,
etc, will come in a next release).
The blockers are few and becoming fewer:
https://issues.apache.org/jira/browse/NETBEANS-330?filter=12343308
Reema is working on the refactoring problem listed above and the other
items above can only be verified once we actually have a release candidate.
So -- last time Emilian put the release together, i.e., rc1. Now we're
going to put the 9.0 final release together. Who will take on the task? It
could be Emilian again, it could also be someone else (I believe there were
a few others who put up their hand, e.g., Sven, Neil).
Instructions:
https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+Release+README
Once the release has been put together, we will:
1. Have NetCAT do a quick check.
2. Do a community acceptance survey.
3. Do the PPMC vote.
4. Do the IPMC vote.
5. Release Apache NetBeans 9.0 final.
So, feedback welcome, and volunteer release manager too.
Thanks,
Gj
Re: Next release can be put together, volunteer for next release
manager needed.
Posted by Wade Chandler <wa...@apache.org>.
+1 to Sven, Neil, and Antonio’s suggestions plus Emilian. It will be great to have Groovy and JS in play!
Thanks,
Wade
> On Jun 21, 2018, at 5:43 AM, Sven Reimers <sv...@gmail.com> wrote:
>
> I am in the same situation.
>
> I think Neil's suggestion about we (the newbies) are going for the next
> alphs... releases to setup stuff from our side and learn the process.
>
> In case Emi will not be able to do it - I am still in - but Emi would be my
> preference.
>
> Upwards and onwards
>
> -Sven
>
> Neil C Smith <ne...@apache.org> schrieb am Do., 21. Juni 2018, 11:14:
>
>> On Thu, 21 Jun 2018 at 05:34, Antonio <an...@vieiro.net> wrote:
>>> I'd like to do this in the future, but I don't think I'd do a good job
>>> right now (this requires setting up things and seeking and reading
>>> documents, and I won't be able to do that right now). So please go ahead.
>>
>> That pretty much describes where I am right now too! Also, in some
>> ways it would make sense for Emi to do this, and for us newbies to get
>> our heads around this on pre-releases?
>>
>>> I can help by preparing up a 9.0 release webpage(s) in draft mode, if
>>> you want, so that we can make it live quickly by changing the
>>> "jbake-status" [1] in the metadata from "draft" to "published".
>>
>> Sounds a plan! Let me know if you want me to look at anything. And,
>> having been a little disconnected the last few weeks, are we all set
>> with inbound links and redirections in/from the IDE now?
>>
>> Incidentally, I'll be meeting the original JBake developer next week
>> at JManc - we got any questions? :-)
>>
>> Best wishes,
>>
>> Neil
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
>> For additional commands, e-mail: dev-help@netbeans.incubator.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-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Next release can be put together, volunteer for next release
manager needed.
Posted by Geertjan Wielenga <ge...@googlemail.com.INVALID>.
Sure. Great.
Gj
On Thu, Jun 21, 2018 at 12:06 PM, Neil C Smith <ne...@apache.org>
wrote:
> On Thu, 21 Jun 2018 at 10:51, Geertjan Wielenga
> <ge...@googlemail.com.invalid> wrote:
> >
> > But, from my point of view, anything is fine, e.g., candidate-1,
> > candidate-2, etc.
>
> Yes, or -vote1?! But something that isn't -rc1 anyway. In fact,
> perhaps a tagging / naming strategy that deliberately doesn't look
> like semantic versioning would be a good idea?
>
> Best wishes,
>
> Neil
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
Re: Next release can be put together, volunteer for next release
manager needed.
Posted by Neil C Smith <ne...@apache.org>.
On Thu, 21 Jun 2018 at 11:58, Wade Chandler <wa...@apache.org> wrote:
> Why not semantic versioning? Asking as it takes care of different meta info such as what we are discussing, and it is quickly becoming an OSS defacto standard from what I can tell anecdotally.
Yes, I'm very pro semantic versioning! My thoughts come from a remark
made by Bertrand - "Each VOTE thread must be about one specific set of
artifacts, clearly
identified.". What we're voting on is 9.0, and any version info built
into that release should obviously say 9.0. Whether *that* 9.0 sees
the light of day is another matter, but it's an internal thing.
So, while we could use a suffix, and Bertrand suggested -vc1, I'd be
equally happy with a tag like "9.0 (vote 1)". And a second tag of the
same commit as "9.0" assuming it passes.
My 2c.
Best wishes,
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Next release can be put together, volunteer for next release
manager needed.
Posted by Laszlo Kishalmi <la...@gmail.com>.
Well,
Semantic versioning is just one option, not necessarily the best one
here. Just remember how many projects started with that, and end up
using something else, or a variant of it. Like Java started with that.
Linux kernel 3 was merely introduced as Linus was tired releasing the
2.4x something kernels (4.x happened almost for the same reason).
Firefox dropped that, because they felt that users 3.6 -> 3.7 movement
does not express the amount of work they put in between releases, and
who would use FF 3.8 when there is Chrome 6 or 7 etc.
Semantic versioning works on module level well, though there are quite
many options out there to pick from. We could do the releases in a
timely manner after we are out of incubation if we like. I just would
like to start a discussion on that. Also what matters probably the most,
it would be good what our users think of this.
On 06/21/2018 04:04 AM, Wade Chandler wrote:
> Just so everyone knows how semver works (especially semver 2), and if we were to need a bigger convo, we can start another thread (just putting out info for now):
>
> https://semver.org/ <https://semver.org/>
>
>
>> On Jun 21, 2018, at 6:58 AM, Wade Chandler <wa...@apache.org> wrote:
>>
>> Why not semantic versioning? Asking as it takes care of different meta info such as what we are discussing, and it is quickly becoming an OSS defacto standard from what I can tell anecdotally.
>>
>> Thanks,
>>
>> Wade
>>
>>> On Jun 21, 2018, at 6:06 AM, Neil C Smith <ne...@apache.org> wrote:
>>>
>>> On Thu, 21 Jun 2018 at 10:51, Geertjan Wielenga
>>> <ge...@googlemail.com.invalid> wrote:
>>>> But, from my point of view, anything is fine, e.g., candidate-1,
>>>> candidate-2, etc.
>>> Yes, or -vote1?! But something that isn't -rc1 anyway. In fact,
>>> perhaps a tagging / naming strategy that deliberately doesn't look
>>> like semantic versioning would be a good idea?
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Next release can be put together, volunteer for next release
manager needed.
Posted by Wade Chandler <wa...@apache.org>.
Just so everyone knows how semver works (especially semver 2), and if we were to need a bigger convo, we can start another thread (just putting out info for now):
https://semver.org/ <https://semver.org/>
> On Jun 21, 2018, at 6:58 AM, Wade Chandler <wa...@apache.org> wrote:
>
> Why not semantic versioning? Asking as it takes care of different meta info such as what we are discussing, and it is quickly becoming an OSS defacto standard from what I can tell anecdotally.
>
> Thanks,
>
> Wade
>
>> On Jun 21, 2018, at 6:06 AM, Neil C Smith <ne...@apache.org> wrote:
>>
>> On Thu, 21 Jun 2018 at 10:51, Geertjan Wielenga
>> <ge...@googlemail.com.invalid> wrote:
>>>
>>> But, from my point of view, anything is fine, e.g., candidate-1,
>>> candidate-2, etc.
>>
>> Yes, or -vote1?! But something that isn't -rc1 anyway. In fact,
>> perhaps a tagging / naming strategy that deliberately doesn't look
>> like semantic versioning would be a good idea?
>
Re: Next release can be put together, volunteer for next release
manager needed.
Posted by Wade Chandler <wa...@apache.org>.
Why not semantic versioning? Asking as it takes care of different meta info such as what we are discussing, and it is quickly becoming an OSS defacto standard from what I can tell anecdotally.
Thanks,
Wade
> On Jun 21, 2018, at 6:06 AM, Neil C Smith <ne...@apache.org> wrote:
>
> On Thu, 21 Jun 2018 at 10:51, Geertjan Wielenga
> <ge...@googlemail.com.invalid> wrote:
>>
>> But, from my point of view, anything is fine, e.g., candidate-1,
>> candidate-2, etc.
>
> Yes, or -vote1?! But something that isn't -rc1 anyway. In fact,
> perhaps a tagging / naming strategy that deliberately doesn't look
> like semantic versioning would be a good idea?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Next release can be put together, volunteer for next release
manager needed.
Posted by Neil C Smith <ne...@apache.org>.
On Thu, 21 Jun 2018 at 10:51, Geertjan Wielenga
<ge...@googlemail.com.invalid> wrote:
>
> But, from my point of view, anything is fine, e.g., candidate-1,
> candidate-2, etc.
Yes, or -vote1?! But something that isn't -rc1 anyway. In fact,
perhaps a tagging / naming strategy that deliberately doesn't look
like semantic versioning would be a good idea?
Best wishes,
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Next release can be put together, volunteer for next release
manager needed.
Posted by Geertjan Wielenga <ge...@googlemail.com.INVALID>.
But, from my point of view, anything is fine, e.g., candidate-1,
candidate-2, etc.
Gj
On Thu, Jun 21, 2018 at 11:50 AM, Geertjan Wielenga <
geertjan.wielenga@googlemail.com> wrote:
> No, true, not yet -- well, I believe, rc1, rc2, etc...
>
> Gj
>
> On Thu, Jun 21, 2018 at 11:48 AM, Sven Reimers <sv...@gmail.com>
> wrote:
>
>> Did we agree on the naming suffixes/ tag name strategy?
>>
>> Sven
>>
>> Geertjan Wielenga <ge...@googlemail.com.invalid> schrieb am
>> Do., 21. Juni 2018, 11:47:
>>
>> > OK, great, Emilian gets the honor to put the candidate for the final
>> Apache
>> > NetBeans (incubating) 9.0 release together. :-)
>> >
>> > As soon as he's done so, we'll start with NetCAT giving it a look and
>> the
>> > community acceptance survey after that. If those two give the go ahead,
>> > we'll move to the PPMC vote. If not, we'll fix what's needed and Emilian
>> > will put the next candidate together, etc.
>> >
>> > Gj
>> >
>> > On Thu, Jun 21, 2018 at 11:43 AM, Sven Reimers <sv...@gmail.com>
>> > wrote:
>> >
>> > > I am in the same situation.
>> > >
>> > > I think Neil's suggestion about we (the newbies) are going for the
>> next
>> > > alphs... releases to setup stuff from our side and learn the process.
>> > >
>> > > In case Emi will not be able to do it - I am still in - but Emi would
>> be
>> > my
>> > > preference.
>> > >
>> > > Upwards and onwards
>> > >
>> > > -Sven
>> > >
>> > > Neil C Smith <ne...@apache.org> schrieb am Do., 21. Juni 2018,
>> > 11:14:
>> > >
>> > > > On Thu, 21 Jun 2018 at 05:34, Antonio <an...@vieiro.net> wrote:
>> > > > > I'd like to do this in the future, but I don't think I'd do a good
>> > job
>> > > > > right now (this requires setting up things and seeking and reading
>> > > > > documents, and I won't be able to do that right now). So please go
>> > > ahead.
>> > > >
>> > > > That pretty much describes where I am right now too! Also, in some
>> > > > ways it would make sense for Emi to do this, and for us newbies to
>> get
>> > > > our heads around this on pre-releases?
>> > > >
>> > > > > I can help by preparing up a 9.0 release webpage(s) in draft
>> mode, if
>> > > > > you want, so that we can make it live quickly by changing the
>> > > > > "jbake-status" [1] in the metadata from "draft" to "published".
>> > > >
>> > > > Sounds a plan! Let me know if you want me to look at anything.
>> And,
>> > > > having been a little disconnected the last few weeks, are we all set
>> > > > with inbound links and redirections in/from the IDE now?
>> > > >
>> > > > Incidentally, I'll be meeting the original JBake developer next week
>> > > > at JManc - we got any questions? :-)
>> > > >
>> > > > Best wishes,
>> > > >
>> > > > Neil
>> > > >
>> > > > ------------------------------------------------------------
>> ---------
>> > > > To unsubscribe, e-mail: dev-unsubscribe@netbeans.incub
>> ator.apache.org
>> > > > For additional commands, e-mail:
>> > dev-help@netbeans.incubator.apache.org
>> > > >
>> > > > For further information about the NetBeans mailing lists, visit:
>> > > > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>> > > >
>> > > >
>> > > >
>> > > >
>> > >
>> >
>>
>
>
Re: Next release can be put together, volunteer for next release
manager needed.
Posted by Geertjan Wielenga <ge...@googlemail.com.INVALID>.
No, true, not yet -- well, I believe, rc1, rc2, etc...
Gj
On Thu, Jun 21, 2018 at 11:48 AM, Sven Reimers <sv...@gmail.com>
wrote:
> Did we agree on the naming suffixes/ tag name strategy?
>
> Sven
>
> Geertjan Wielenga <ge...@googlemail.com.invalid> schrieb am
> Do., 21. Juni 2018, 11:47:
>
> > OK, great, Emilian gets the honor to put the candidate for the final
> Apache
> > NetBeans (incubating) 9.0 release together. :-)
> >
> > As soon as he's done so, we'll start with NetCAT giving it a look and the
> > community acceptance survey after that. If those two give the go ahead,
> > we'll move to the PPMC vote. If not, we'll fix what's needed and Emilian
> > will put the next candidate together, etc.
> >
> > Gj
> >
> > On Thu, Jun 21, 2018 at 11:43 AM, Sven Reimers <sv...@gmail.com>
> > wrote:
> >
> > > I am in the same situation.
> > >
> > > I think Neil's suggestion about we (the newbies) are going for the next
> > > alphs... releases to setup stuff from our side and learn the process.
> > >
> > > In case Emi will not be able to do it - I am still in - but Emi would
> be
> > my
> > > preference.
> > >
> > > Upwards and onwards
> > >
> > > -Sven
> > >
> > > Neil C Smith <ne...@apache.org> schrieb am Do., 21. Juni 2018,
> > 11:14:
> > >
> > > > On Thu, 21 Jun 2018 at 05:34, Antonio <an...@vieiro.net> wrote:
> > > > > I'd like to do this in the future, but I don't think I'd do a good
> > job
> > > > > right now (this requires setting up things and seeking and reading
> > > > > documents, and I won't be able to do that right now). So please go
> > > ahead.
> > > >
> > > > That pretty much describes where I am right now too! Also, in some
> > > > ways it would make sense for Emi to do this, and for us newbies to
> get
> > > > our heads around this on pre-releases?
> > > >
> > > > > I can help by preparing up a 9.0 release webpage(s) in draft mode,
> if
> > > > > you want, so that we can make it live quickly by changing the
> > > > > "jbake-status" [1] in the metadata from "draft" to "published".
> > > >
> > > > Sounds a plan! Let me know if you want me to look at anything. And,
> > > > having been a little disconnected the last few weeks, are we all set
> > > > with inbound links and redirections in/from the IDE now?
> > > >
> > > > Incidentally, I'll be meeting the original JBake developer next week
> > > > at JManc - we got any questions? :-)
> > > >
> > > > Best wishes,
> > > >
> > > > Neil
> > > >
> > > > ------------------------------------------------------------
> ---------
> > > > To unsubscribe, e-mail: dev-unsubscribe@netbeans.
> incubator.apache.org
> > > > For additional commands, e-mail:
> > dev-help@netbeans.incubator.apache.org
> > > >
> > > > For further information about the NetBeans mailing lists, visit:
> > > > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> > > >
> > > >
> > > >
> > > >
> > >
> >
>
Re: Next release can be put together, volunteer for next release
manager needed.
Posted by Sven Reimers <sv...@gmail.com>.
Did we agree on the naming suffixes/ tag name strategy?
Sven
Geertjan Wielenga <ge...@googlemail.com.invalid> schrieb am
Do., 21. Juni 2018, 11:47:
> OK, great, Emilian gets the honor to put the candidate for the final Apache
> NetBeans (incubating) 9.0 release together. :-)
>
> As soon as he's done so, we'll start with NetCAT giving it a look and the
> community acceptance survey after that. If those two give the go ahead,
> we'll move to the PPMC vote. If not, we'll fix what's needed and Emilian
> will put the next candidate together, etc.
>
> Gj
>
> On Thu, Jun 21, 2018 at 11:43 AM, Sven Reimers <sv...@gmail.com>
> wrote:
>
> > I am in the same situation.
> >
> > I think Neil's suggestion about we (the newbies) are going for the next
> > alphs... releases to setup stuff from our side and learn the process.
> >
> > In case Emi will not be able to do it - I am still in - but Emi would be
> my
> > preference.
> >
> > Upwards and onwards
> >
> > -Sven
> >
> > Neil C Smith <ne...@apache.org> schrieb am Do., 21. Juni 2018,
> 11:14:
> >
> > > On Thu, 21 Jun 2018 at 05:34, Antonio <an...@vieiro.net> wrote:
> > > > I'd like to do this in the future, but I don't think I'd do a good
> job
> > > > right now (this requires setting up things and seeking and reading
> > > > documents, and I won't be able to do that right now). So please go
> > ahead.
> > >
> > > That pretty much describes where I am right now too! Also, in some
> > > ways it would make sense for Emi to do this, and for us newbies to get
> > > our heads around this on pre-releases?
> > >
> > > > I can help by preparing up a 9.0 release webpage(s) in draft mode, if
> > > > you want, so that we can make it live quickly by changing the
> > > > "jbake-status" [1] in the metadata from "draft" to "published".
> > >
> > > Sounds a plan! Let me know if you want me to look at anything. And,
> > > having been a little disconnected the last few weeks, are we all set
> > > with inbound links and redirections in/from the IDE now?
> > >
> > > Incidentally, I'll be meeting the original JBake developer next week
> > > at JManc - we got any questions? :-)
> > >
> > > Best wishes,
> > >
> > > Neil
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> > > For additional commands, e-mail:
> dev-help@netbeans.incubator.apache.org
> > >
> > > For further information about the NetBeans mailing lists, visit:
> > > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> > >
> > >
> > >
> > >
> >
>
Re: Next release can be put together, volunteer for next release
manager needed.
Posted by Geertjan Wielenga <ge...@googlemail.com.INVALID>.
OK, great, Emilian gets the honor to put the candidate for the final Apache
NetBeans (incubating) 9.0 release together. :-)
As soon as he's done so, we'll start with NetCAT giving it a look and the
community acceptance survey after that. If those two give the go ahead,
we'll move to the PPMC vote. If not, we'll fix what's needed and Emilian
will put the next candidate together, etc.
Gj
On Thu, Jun 21, 2018 at 11:43 AM, Sven Reimers <sv...@gmail.com>
wrote:
> I am in the same situation.
>
> I think Neil's suggestion about we (the newbies) are going for the next
> alphs... releases to setup stuff from our side and learn the process.
>
> In case Emi will not be able to do it - I am still in - but Emi would be my
> preference.
>
> Upwards and onwards
>
> -Sven
>
> Neil C Smith <ne...@apache.org> schrieb am Do., 21. Juni 2018, 11:14:
>
> > On Thu, 21 Jun 2018 at 05:34, Antonio <an...@vieiro.net> wrote:
> > > I'd like to do this in the future, but I don't think I'd do a good job
> > > right now (this requires setting up things and seeking and reading
> > > documents, and I won't be able to do that right now). So please go
> ahead.
> >
> > That pretty much describes where I am right now too! Also, in some
> > ways it would make sense for Emi to do this, and for us newbies to get
> > our heads around this on pre-releases?
> >
> > > I can help by preparing up a 9.0 release webpage(s) in draft mode, if
> > > you want, so that we can make it live quickly by changing the
> > > "jbake-status" [1] in the metadata from "draft" to "published".
> >
> > Sounds a plan! Let me know if you want me to look at anything. And,
> > having been a little disconnected the last few weeks, are we all set
> > with inbound links and redirections in/from the IDE now?
> >
> > Incidentally, I'll be meeting the original JBake developer next week
> > at JManc - we got any questions? :-)
> >
> > Best wishes,
> >
> > Neil
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> > For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
> >
> > For further information about the NetBeans mailing lists, visit:
> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >
> >
> >
> >
>
Re: Next release can be put together, volunteer for next release
manager needed.
Posted by Sven Reimers <sv...@gmail.com>.
I am in the same situation.
I think Neil's suggestion about we (the newbies) are going for the next
alphs... releases to setup stuff from our side and learn the process.
In case Emi will not be able to do it - I am still in - but Emi would be my
preference.
Upwards and onwards
-Sven
Neil C Smith <ne...@apache.org> schrieb am Do., 21. Juni 2018, 11:14:
> On Thu, 21 Jun 2018 at 05:34, Antonio <an...@vieiro.net> wrote:
> > I'd like to do this in the future, but I don't think I'd do a good job
> > right now (this requires setting up things and seeking and reading
> > documents, and I won't be able to do that right now). So please go ahead.
>
> That pretty much describes where I am right now too! Also, in some
> ways it would make sense for Emi to do this, and for us newbies to get
> our heads around this on pre-releases?
>
> > I can help by preparing up a 9.0 release webpage(s) in draft mode, if
> > you want, so that we can make it live quickly by changing the
> > "jbake-status" [1] in the metadata from "draft" to "published".
>
> Sounds a plan! Let me know if you want me to look at anything. And,
> having been a little disconnected the last few weeks, are we all set
> with inbound links and redirections in/from the IDE now?
>
> Incidentally, I'll be meeting the original JBake developer next week
> at JManc - we got any questions? :-)
>
> Best wishes,
>
> Neil
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
Re: Next release can be put together, volunteer for next release
manager needed.
Posted by Neil C Smith <ne...@apache.org>.
On Thu, 21 Jun 2018 at 05:34, Antonio <an...@vieiro.net> wrote:
> I'd like to do this in the future, but I don't think I'd do a good job
> right now (this requires setting up things and seeking and reading
> documents, and I won't be able to do that right now). So please go ahead.
That pretty much describes where I am right now too! Also, in some
ways it would make sense for Emi to do this, and for us newbies to get
our heads around this on pre-releases?
> I can help by preparing up a 9.0 release webpage(s) in draft mode, if
> you want, so that we can make it live quickly by changing the
> "jbake-status" [1] in the metadata from "draft" to "published".
Sounds a plan! Let me know if you want me to look at anything. And,
having been a little disconnected the last few weeks, are we all set
with inbound links and redirections in/from the IDE now?
Incidentally, I'll be meeting the original JBake developer next week
at JManc - we got any questions? :-)
Best wishes,
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Next release can be put together, volunteer for next release
manager needed.
Posted by Antonio <an...@vieiro.net>.
Hi all,
I'd like to do this in the future, but I don't think I'd do a good job
right now (this requires setting up things and seeking and reading
documents, and I won't be able to do that right now). So please go ahead.
I can help by preparing up a 9.0 release webpage(s) in draft mode, if
you want, so that we can make it live quickly by changing the
"jbake-status" [1] in the metadata from "draft" to "published".
Cheers,
Antonio
[1] https://jbake.org/docs/2.6.0/#status
On 19/06/18 14:42, Emilian Bold wrote:
> I volunteer but I don't mind if somebody else also wants to give it a try.
>
> --emi
>
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>
> On 19 June 2018 2:53 PM, Geertjan Wielenga <ge...@googlemail.com.INVALID> wrote:
>
>> Hi all,
>>
>> We're coming very close IMHO to the final release of Apache NetBeans 9.0,
>>
>> i.e., the Java SE IDE (without the 2nd donation code, which is now very
>>
>> close to being here but we shouldn't wait for that, i.e., JEE, JavaScript,
>>
>> etc, will come in a next release).
>>
>> The blockers are few and becoming fewer:
>>
>> https://issues.apache.org/jira/browse/NETBEANS-330?filter=12343308
>>
>> Reema is working on the refactoring problem listed above and the other
>>
>> items above can only be verified once we actually have a release candidate.
>>
>> So -- last time Emilian put the release together, i.e., rc1. Now we're
>>
>> going to put the 9.0 final release together. Who will take on the task? It
>>
>> could be Emilian again, it could also be someone else (I believe there were
>>
>> a few others who put up their hand, e.g., Sven, Neil).
>>
>> Instructions:
>>
>> https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+Release+README
>>
>> Once the release has been put together, we will:
>>
>> 1. Have NetCAT do a quick check.
>> 2. Do a community acceptance survey.
>> 3. Do the PPMC vote.
>> 4. Do the IPMC vote.
>> 5. Release Apache NetBeans 9.0 final.
>>
>> So, feedback welcome, and volunteer release manager too.
>>
>> Thanks,
>>
>> Gj
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-help@netbeans.incubator.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-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Next release can be put together, volunteer for next release manager needed.
Posted by Emilian Bold <em...@protonmail.ch.INVALID>.
I volunteer but I don't mind if somebody else also wants to give it a try.
--emi
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On 19 June 2018 2:53 PM, Geertjan Wielenga <ge...@googlemail.com.INVALID> wrote:
> Hi all,
>
> We're coming very close IMHO to the final release of Apache NetBeans 9.0,
>
> i.e., the Java SE IDE (without the 2nd donation code, which is now very
>
> close to being here but we shouldn't wait for that, i.e., JEE, JavaScript,
>
> etc, will come in a next release).
>
> The blockers are few and becoming fewer:
>
> https://issues.apache.org/jira/browse/NETBEANS-330?filter=12343308
>
> Reema is working on the refactoring problem listed above and the other
>
> items above can only be verified once we actually have a release candidate.
>
> So -- last time Emilian put the release together, i.e., rc1. Now we're
>
> going to put the 9.0 final release together. Who will take on the task? It
>
> could be Emilian again, it could also be someone else (I believe there were
>
> a few others who put up their hand, e.g., Sven, Neil).
>
> Instructions:
>
> https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+Release+README
>
> Once the release has been put together, we will:
>
> 1. Have NetCAT do a quick check.
> 2. Do a community acceptance survey.
> 3. Do the PPMC vote.
> 4. Do the IPMC vote.
> 5. Release Apache NetBeans 9.0 final.
>
> So, feedback welcome, and volunteer release manager too.
>
> Thanks,
>
> Gj
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Next release can be put together, volunteer for next release
manager needed.
Posted by Matthias Bläsing <mb...@doppel-helix.eu>.
Hi,
Am Dienstag, den 19.06.2018, 13:53 +0200 schrieb Geertjan Wielenga:
> We're coming very close IMHO to the final release of Apache NetBeans 9.0,
> i.e., the Java SE IDE (without the 2nd donation code, which is now very
> close to being here but we shouldn't wait for that, i.e., JEE, JavaScript,
> etc, will come in a next release).
agreed. The flood of code, that will come in, will be again bring new
pain (licenses and so on). Having a stable release will help with
motivation :-)
> The blockers are few and becoming fewer:
>
> https://issues.apache.org/jira/browse/NETBEANS-330?filter=12343308
>
> Reema is working on the refactoring problem listed above and the
> other items above can only be verified once we actually have a
> release candidate.
My understanding for the incubation process is, that it is ok to
release with known problems.
However these look like sensible things to tackle:
* we still produce md5 sums - from the output of the build job it
looks like the jenkins job holds a shell script to do it. This
should be deactivated (I don't even find the shell script, I think
it needs someone with Jenkins Permissions):
https://builds.apache.org/view/Incubator%20Projects/job/incubator-netbeans-release/lastBuild/consoleText
https://issues.apache.org/jira/browse/NETBEANS-821
* Are all branding updates done (NETBEANS-876)?
https://issues.apache.org/jira/browse/NETBEANS-876
These could be deferred (I'll look into these, but it needs time):
* Entity definitions from w3c were declared with a questionable
license. The issue is in discussion/clearance with apache legal:
https://issues.apache.org/jira/browse/NETBEANS-853
https://issues.apache.org/jira/browse/LEGAL-386
* Licenses for XML catalog grammars are apache internal not cleared.
This need to be discussed (I have an idea for a solution).
https://issues.apache.org/jira/browse/NETBEANS-856
https://issues.apache.org/jira/browse/LEGAL-387
* WSDL grammar file must not be under version control (please! No
discussions, that this is not the best policy decision from the
ASF). I also have an idea how to tackle this.
https://issues.apache.org/jira/browse/NETBEANS-857
Greetings
Matthias
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists