You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@netbeans.apache.org by Neil C Smith <ne...@apache.org> on 2022/06/29 14:16:39 UTC
[RELEASES] Getting ready for NetBeans 15 branching
Hi Eric, Martin, Geertjan .. and everyone else,
Just thought I'd kick off a thread as it's getting near branching time
again. Seems to come around quicker every time! I also realised I
don't think we had the usual postmortem thread on NB14 either. Any
points, changes, etc. to address for 15?
Few from me would be -
There were a couple of PRs in NB14 that to me didn't really meet the
criteria for merging to delivery, one which potentially held the
release up. It's not a release team job to decide what gets merged -
that's for all reviewers. And primarily, in my mind, the PR author
should be making the initial call. I'd like to suggest that all
descriptions on PRs for delivery, at least when not linked to an
issue, should include a short justification for inclusion. Thoughts?
On PRs, Martin, can you handle reviewing and merging delivery PRs (or
parts) that are VSCode related? Obviously need to schedule around
syncing and RC builds. Whenever I merge to delivery, I try to test
the fix, check for potential conflicts, think about highlighting in RC
emails, etc. But for me that's with the IDE in mind rather than the
VSCode plugin.
As discussed elsewhere, I've added a GitHub label for Highlight, to
try and start flagging PRs that are changes to highlight in release
notes, announcements, etc. Possibly need to apply some
retrospectively for 15.
I should be OK for all of this release cycle - sorry I had to duck out
for much of the last one. I'm happy to handle the initial branch and
configuration around July 15th, unless anyone else wants to? Anyone
else got commitments, holidays, etc. to consider this time around?
Summer release always a fun one.
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: [RELEASES] Getting ready for NetBeans 15 branching
Posted by Eric Barboni <sk...@apache.org>.
Hi,
The jenkins issue was kind of network issue but it was working again a few day later Intend was to make a RC fast but was delayed for RC6. Hardware issue may happen infra suffer an hardware issue last weeks that was kind of 48h to repopulate all the build. (not only NetBeans)
Sometime bad luck happens 😃
Eric
-----Message d'origine-----
De : Neil C Smith <>
Envoyé : jeudi 30 juin 2022 12:11
À : Michael Bien <mb...@gmail.com>; dev@netbeans.apache.org
Objet : Re: [RELEASES] Getting ready for NetBeans 15 branching
On Wed, 29 Jun 2022 at 22:03, Michael Bien <mb...@gmail.com> wrote:
> I believe part of the problem was that we had issues with 2 of 3 build
> clusters. Travis didn't want to build [1] (basically just like right
> now when we have a queue time of ~24h for some reason) and Jenkins had
> problems too which is probably even worse during release.
>
> This caused PRs to pile up and added at least one extra RC, which in
> turn also added more opportunities to integrate more PRs etc.
Yes, didn't mention Jenkins infrastructure issues. Eric, do you know whether what happened is fully resolved / could happen again?
I'm not sure the infrastructure issues were the reason for RC5 (never actually announced), but did allow a couple more things in for RC6 while it was being resolved.
> There was also the incident when we lost ~2 PRs from the delivery
> branch which also caused an extra RC. To avoid this in future, we
> should double check the sync PRs before merging, to make sure everything is in it.
> Lets do a proper review as if it is a regular PR (maybe put the
> authors of the PRs which got merged during RC on the reviewer list?).
I'm not sure I'd add that overhead into turning around the sync PRs in the general case, given that sometimes we need to turn around in a few hours. We've not had this issue before, and I think the reason was clear.
We've never had to force push delivery before, although it's always been an outside possibility. I think we had 2 this time, the first of which possibly shouldn't have been necessary and a sign there was a problem. I'm not sure we can lose a PR without a force push?
I think we need more robust checks and [NOTICE] emails if there's a need to force push, so full review in those circumstances would make sense. Of course, PR authors should probably also be checking on sync to release and master that changes merged, applied and work correctly anyway!
We could potentially use GitHub actions to automatically notify on any force push into a repository branch. That might be worth considering?
> We should also spend more time trying to make tests fast and reliable
> since this is actually something we can influence. Long queue times
> become less of a problem if we don't have to restart jobs like playing
> whack a mole ;)
You take away the need to whack a mole on Travis and you take away half the "fun" of managing releases! :-)
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
---------------------------------------------------------------------
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: [RELEASES] Getting ready for NetBeans 15 branching
Posted by Neil C Smith <ne...@apache.org>.
On Wed, 29 Jun 2022 at 22:03, Michael Bien <mb...@gmail.com> wrote:
> I believe part of the problem was that we had issues with 2 of 3 build
> clusters. Travis didn't want to build [1] (basically just like right now
> when we have a queue time of ~24h for some reason) and Jenkins had
> problems too which is probably even worse during release.
>
> This caused PRs to pile up and added at least one extra RC, which in
> turn also added more opportunities to integrate more PRs etc.
Yes, didn't mention Jenkins infrastructure issues. Eric, do you know
whether what happened is fully resolved / could happen again?
I'm not sure the infrastructure issues were the reason for RC5 (never
actually announced), but did allow a couple more things in for RC6
while it was being resolved.
> There was also the incident when we lost ~2 PRs from the delivery branch
> which also caused an extra RC. To avoid this in future, we should double
> check the sync PRs before merging, to make sure everything is in it.
> Lets do a proper review as if it is a regular PR (maybe put the authors
> of the PRs which got merged during RC on the reviewer list?).
I'm not sure I'd add that overhead into turning around the sync PRs in
the general case, given that sometimes we need to turn around in a few
hours. We've not had this issue before, and I think the reason was
clear.
We've never had to force push delivery before, although it's always
been an outside possibility. I think we had 2 this time, the first of
which possibly shouldn't have been necessary and a sign there was a
problem. I'm not sure we can lose a PR without a force push?
I think we need more robust checks and [NOTICE] emails if there's a
need to force push, so full review in those circumstances would make
sense. Of course, PR authors should probably also be checking on sync
to release and master that changes merged, applied and work correctly
anyway!
We could potentially use GitHub actions to automatically notify on any
force push into a repository branch. That might be worth considering?
> We should also spend more time trying to make tests fast and reliable
> since this is actually something we can influence. Long queue times
> become less of a problem if we don't have to restart jobs like playing
> whack a mole ;)
You take away the need to whack a mole on Travis and you take away
half the "fun" of managing releases! :-)
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: [RELEASES] Getting ready for NetBeans 15 branching
Posted by Michael Bien <mb...@gmail.com>.
Hi Neil,
I believe part of the problem was that we had issues with 2 of 3 build
clusters. Travis didn't want to build [1] (basically just like right now
when we have a queue time of ~24h for some reason) and Jenkins had
problems too which is probably even worse during release.
This caused PRs to pile up and added at least one extra RC, which in
turn also added more opportunities to integrate more PRs etc.
There was also the incident when we lost ~2 PRs from the delivery branch
which also caused an extra RC. To avoid this in future, we should double
check the sync PRs before merging, to make sure everything is in it.
Lets do a proper review as if it is a regular PR (maybe put the authors
of the PRs which got merged during RC on the reviewer list?).
We should also spend more time trying to make tests fast and reliable
since this is actually something we can influence. Long queue times
become less of a problem if we don't have to restart jobs like playing
whack a mole ;)
best regards,
michael
[1] https://issues.apache.org/jira/browse/INFRA-23257
On 29.06.22 16:16, Neil C Smith wrote:
> Hi Eric, Martin, Geertjan .. and everyone else,
>
> Just thought I'd kick off a thread as it's getting near branching time
> again. Seems to come around quicker every time! I also realised I
> don't think we had the usual postmortem thread on NB14 either. Any
> points, changes, etc. to address for 15?
>
> Few from me would be -
>
> There were a couple of PRs in NB14 that to me didn't really meet the
> criteria for merging to delivery, one which potentially held the
> release up. It's not a release team job to decide what gets merged -
> that's for all reviewers. And primarily, in my mind, the PR author
> should be making the initial call. I'd like to suggest that all
> descriptions on PRs for delivery, at least when not linked to an
> issue, should include a short justification for inclusion. Thoughts?
>
> On PRs, Martin, can you handle reviewing and merging delivery PRs (or
> parts) that are VSCode related? Obviously need to schedule around
> syncing and RC builds. Whenever I merge to delivery, I try to test
> the fix, check for potential conflicts, think about highlighting in RC
> emails, etc. But for me that's with the IDE in mind rather than the
> VSCode plugin.
>
> As discussed elsewhere, I've added a GitHub label for Highlight, to
> try and start flagging PRs that are changes to highlight in release
> notes, announcements, etc. Possibly need to apply some
> retrospectively for 15.
>
>
> I should be OK for all of this release cycle - sorry I had to duck out
> for much of the last one. I'm happy to handle the initial branch and
> configuration around July 15th, unless anyone else wants to? Anyone
> else got commitments, holidays, etc. to consider this time around?
> Summer release always a fun one.
>
> 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
>
>
>
---------------------------------------------------------------------
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: [External] : Re: [RELEASES] Getting ready for NetBeans 15 branching
Posted by Martin Balin <ma...@oracle.com>.
Hi,
thanks’ for heads up.
Martin
> On 12. 7. 2022, at 21:11, Laszlo Kishalmi <la...@gmail.com> wrote:
>
> Just an FYI: Going to upgrade Gradle Tooling to Gradle 7.5 as a PR (with JDK 18 Support) on Thursday/Friday. Right now Gradle 7.5 is in rc4, I hope Thursday it would hit GA, if not I'll create the PR with 7.5-rc4 and we could update to 7.5 during the NB 15 release phase.
>
> I hope that would be fine with everyone!
>
>
> On 6/29/22 07:16, Neil C Smith wrote:
>> Hi Eric, Martin, Geertjan .. and everyone else,
>>
>> Just thought I'd kick off a thread as it's getting near branching time
>> again. Seems to come around quicker every time! I also realised I
>> don't think we had the usual postmortem thread on NB14 either. Any
>> points, changes, etc. to address for 15?
>>
>> Few from me would be -
>>
>> There were a couple of PRs in NB14 that to me didn't really meet the
>> criteria for merging to delivery, one which potentially held the
>> release up. It's not a release team job to decide what gets merged -
>> that's for all reviewers. And primarily, in my mind, the PR author
>> should be making the initial call. I'd like to suggest that all
>> descriptions on PRs for delivery, at least when not linked to an
>> issue, should include a short justification for inclusion. Thoughts?
>>
>> On PRs, Martin, can you handle reviewing and merging delivery PRs (or
>> parts) that are VSCode related? Obviously need to schedule around
>> syncing and RC builds. Whenever I merge to delivery, I try to test
>> the fix, check for potential conflicts, think about highlighting in RC
>> emails, etc. But for me that's with the IDE in mind rather than the
>> VSCode plugin.
>>
>> As discussed elsewhere, I've added a GitHub label for Highlight, to
>> try and start flagging PRs that are changes to highlight in release
>> notes, announcements, etc. Possibly need to apply some
>> retrospectively for 15.
>>
>>
>> I should be OK for all of this release cycle - sorry I had to duck out
>> for much of the last one. I'm happy to handle the initial branch and
>> configuration around July 15th, unless anyone else wants to? Anyone
>> else got commitments, holidays, etc. to consider this time around?
>> Summer release always a fun one.
>>
>> 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!!ACWV5N9M2RV99hQ!Lf4BcmRa8nMQzTgYXeXivQ4dphjKxJ94LPpwRFf4BSpjsTtU4CJ0g9pi26QzrEAzo7cmAiHds_rYm0u1R7lmQ_oq1Qw$
>>
>>
>
> ---------------------------------------------------------------------
> 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!!ACWV5N9M2RV99hQ!Lf4BcmRa8nMQzTgYXeXivQ4dphjKxJ94LPpwRFf4BSpjsTtU4CJ0g9pi26QzrEAzo7cmAiHds_rYm0u1R7lmQ_oq1Qw$
>
>
Re: [RELEASES] Getting ready for NetBeans 15 branching
Posted by Michael Bien <mb...@gmail.com>.
sounds great Laszlo!
-mbien
On 12.07.22 21:11, Laszlo Kishalmi wrote:
> Just an FYI: Going to upgrade Gradle Tooling to Gradle 7.5 as a PR
> (with JDK 18 Support) on Thursday/Friday. Right now Gradle 7.5 is in
> rc4, I hope Thursday it would hit GA, if not I'll create the PR with
> 7.5-rc4 and we could update to 7.5 during the NB 15 release phase.
>
> I hope that would be fine with everyone!
>
>
> On 6/29/22 07:16, Neil C Smith wrote:
>> Hi Eric, Martin, Geertjan .. and everyone else,
>>
>> Just thought I'd kick off a thread as it's getting near branching time
>> again. Seems to come around quicker every time! I also realised I
>> don't think we had the usual postmortem thread on NB14 either. Any
>> points, changes, etc. to address for 15?
>>
>> Few from me would be -
>>
>> There were a couple of PRs in NB14 that to me didn't really meet the
>> criteria for merging to delivery, one which potentially held the
>> release up. It's not a release team job to decide what gets merged -
>> that's for all reviewers. And primarily, in my mind, the PR author
>> should be making the initial call. I'd like to suggest that all
>> descriptions on PRs for delivery, at least when not linked to an
>> issue, should include a short justification for inclusion. Thoughts?
>>
>> On PRs, Martin, can you handle reviewing and merging delivery PRs (or
>> parts) that are VSCode related? Obviously need to schedule around
>> syncing and RC builds. Whenever I merge to delivery, I try to test
>> the fix, check for potential conflicts, think about highlighting in RC
>> emails, etc. But for me that's with the IDE in mind rather than the
>> VSCode plugin.
>>
>> As discussed elsewhere, I've added a GitHub label for Highlight, to
>> try and start flagging PRs that are changes to highlight in release
>> notes, announcements, etc. Possibly need to apply some
>> retrospectively for 15.
>>
>>
>> I should be OK for all of this release cycle - sorry I had to duck out
>> for much of the last one. I'm happy to handle the initial branch and
>> configuration around July 15th, unless anyone else wants to? Anyone
>> else got commitments, holidays, etc. to consider this time around?
>> Summer release always a fun one.
>>
>> 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
>>
>>
>>
>
> ---------------------------------------------------------------------
> 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
>
>
>
---------------------------------------------------------------------
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: [RELEASES] Getting ready for NetBeans 15 branching
Posted by Neil C Smith <ne...@apache.org>.
On Tue, 12 Jul 2022 at 20:16, Laszlo Kishalmi <la...@gmail.com> wrote:
>
> Just an FYI: Going to upgrade Gradle Tooling to Gradle 7.5 as a PR (with
> JDK 18 Support) on Thursday/Friday. Right now Gradle 7.5 is in rc4, I
> hope Thursday it would hit GA, if not I'll create the PR with 7.5-rc4
> and we could update to 7.5 during the NB 15 release phase.
>
> I hope that would be fine with everyone!
That would be great. Sounds the correct approach, and be nice not to
have complaints about Java 18 on every Gradle project!
Incidentally, for another thread, I'm curious what would be required
to not have that warning when setting the project to a supported
platform?
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: [RELEASES] Getting ready for NetBeans 15 branching
Posted by Laszlo Kishalmi <la...@gmail.com>.
Just an FYI: Going to upgrade Gradle Tooling to Gradle 7.5 as a PR (with
JDK 18 Support) on Thursday/Friday. Right now Gradle 7.5 is in rc4, I
hope Thursday it would hit GA, if not I'll create the PR with 7.5-rc4
and we could update to 7.5 during the NB 15 release phase.
I hope that would be fine with everyone!
On 6/29/22 07:16, Neil C Smith wrote:
> Hi Eric, Martin, Geertjan .. and everyone else,
>
> Just thought I'd kick off a thread as it's getting near branching time
> again. Seems to come around quicker every time! I also realised I
> don't think we had the usual postmortem thread on NB14 either. Any
> points, changes, etc. to address for 15?
>
> Few from me would be -
>
> There were a couple of PRs in NB14 that to me didn't really meet the
> criteria for merging to delivery, one which potentially held the
> release up. It's not a release team job to decide what gets merged -
> that's for all reviewers. And primarily, in my mind, the PR author
> should be making the initial call. I'd like to suggest that all
> descriptions on PRs for delivery, at least when not linked to an
> issue, should include a short justification for inclusion. Thoughts?
>
> On PRs, Martin, can you handle reviewing and merging delivery PRs (or
> parts) that are VSCode related? Obviously need to schedule around
> syncing and RC builds. Whenever I merge to delivery, I try to test
> the fix, check for potential conflicts, think about highlighting in RC
> emails, etc. But for me that's with the IDE in mind rather than the
> VSCode plugin.
>
> As discussed elsewhere, I've added a GitHub label for Highlight, to
> try and start flagging PRs that are changes to highlight in release
> notes, announcements, etc. Possibly need to apply some
> retrospectively for 15.
>
>
> I should be OK for all of this release cycle - sorry I had to duck out
> for much of the last one. I'm happy to handle the initial branch and
> configuration around July 15th, unless anyone else wants to? Anyone
> else got commitments, holidays, etc. to consider this time around?
> Summer release always a fun one.
>
> 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
>
>
>
---------------------------------------------------------------------
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: [RELEASES] Getting ready for NetBeans 15 branching
Posted by Geertjan Wielenga <ge...@googlemail.com.INVALID>.
Awesome and agree with all points plus would like to be involved again,
maybe a weekly Zoom call with anyone wanting to be involved to see where we
are and how we can work together and of course anything we discuss will be
put back into this mailing list.
Gj
On Wed, Jun 29, 2022 at 6:17 PM Neil C Smith <ne...@apache.org> wrote:
> Hi Eric, Martin, Geertjan .. and everyone else,
>
> Just thought I'd kick off a thread as it's getting near branching time
> again. Seems to come around quicker every time! I also realised I
> don't think we had the usual postmortem thread on NB14 either. Any
> points, changes, etc. to address for 15?
>
> Few from me would be -
>
> There were a couple of PRs in NB14 that to me didn't really meet the
> criteria for merging to delivery, one which potentially held the
> release up. It's not a release team job to decide what gets merged -
> that's for all reviewers. And primarily, in my mind, the PR author
> should be making the initial call. I'd like to suggest that all
> descriptions on PRs for delivery, at least when not linked to an
> issue, should include a short justification for inclusion. Thoughts?
>
> On PRs, Martin, can you handle reviewing and merging delivery PRs (or
> parts) that are VSCode related? Obviously need to schedule around
> syncing and RC builds. Whenever I merge to delivery, I try to test
> the fix, check for potential conflicts, think about highlighting in RC
> emails, etc. But for me that's with the IDE in mind rather than the
> VSCode plugin.
>
> As discussed elsewhere, I've added a GitHub label for Highlight, to
> try and start flagging PRs that are changes to highlight in release
> notes, announcements, etc. Possibly need to apply some
> retrospectively for 15.
>
>
> I should be OK for all of this release cycle - sorry I had to duck out
> for much of the last one. I'm happy to handle the initial branch and
> configuration around July 15th, unless anyone else wants to? Anyone
> else got commitments, holidays, etc. to consider this time around?
> Summer release always a fun one.
>
> 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: Re: [RELEASES] Getting ready for NetBeans 15 branching
Posted by Neil C Smith <ne...@apache.org>.
On Tue, 26 Jul 2022 at 13:00, Eric Bresie <eb...@gmail.com> wrote:
> Don’t suppose that release process is captured on a wiki or confluence page anywhere is it?
Some (not all) of the release process is at
https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+Release+README
The email linked above needs adding to a wiki page sometime. It's
nothing new, really, just tidying up and being explicit about what
we've been doing for some time now.
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: Re: [RELEASES] Getting ready for NetBeans 15 branching
Posted by Eric Bresie <eb...@gmail.com>.
Don’t suppose that release process is captured on a wiki or confluence page anywhere is it?
Eric Bresie
Ebresie@gmail.com (mailto:Ebresie@gmail.com)
> On July 23, 2022 at 3:31:53 AM CDT, Neil C Smith <neilcsmith@apache.org (mailto:neilcsmith@apache.org)> wrote:
> On Sat, 23 Jul 2022 at 08:35, Jaroslav Tulach <jaroslav.tulach@gmail.com (mailto:jaroslav.tulach@gmail.com)> wrote:
> >
> > Dne středa 29. června 2022 16:16:39 CEST, Neil C Smith napsal(a):
> > > It's not a release team job to decide what gets merged -
> > > that's for all reviewers. And primarily, in my mind, the PR author
> > > should be making the initial call. I'd like to suggest that all
> > > descriptions on PRs for delivery, at least when not linked to an
> > > issue, should include a short justification for inclusion. Thoughts?
> >
> > Example: https://github.com/apache/netbeans/pull/4422
> >
> > Justification done. Reviewers are fine with the merge to delivery. Who is
> > supposed to merge? Me or release coordinator?
>
> All merges to delivery are done by the release team.
>
> Please read the full process at
> https://lists.apache.org/thread/hyjbsz55zb9xfcnccghkrsvqsnt83nwf
>
> It will be merged at some point before rc2 is built, and merged
> through to master sometime shortly after.
>
> Best wishes,
>
> Neil
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org (mailto:dev-unsubscribe@netbeans.apache.org)
> For additional commands, e-mail: dev-help@netbeans.apache.org (mailto:dev-help@netbeans.apache.org)
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
Re: [RELEASES] Getting ready for NetBeans 15 branching
Posted by Neil C Smith <ne...@apache.org>.
On Sat, 23 Jul 2022 at 08:35, Jaroslav Tulach <ja...@gmail.com> wrote:
>
> Dne středa 29. června 2022 16:16:39 CEST, Neil C Smith napsal(a):
> > It's not a release team job to decide what gets merged -
> > that's for all reviewers. And primarily, in my mind, the PR author
> > should be making the initial call. I'd like to suggest that all
> > descriptions on PRs for delivery, at least when not linked to an
> > issue, should include a short justification for inclusion. Thoughts?
>
> Example: https://github.com/apache/netbeans/pull/4422
>
> Justification done. Reviewers are fine with the merge to delivery. Who is
> supposed to merge? Me or release coordinator?
All merges to delivery are done by the release team.
Please read the full process at
https://lists.apache.org/thread/hyjbsz55zb9xfcnccghkrsvqsnt83nwf
It will be merged at some point before rc2 is built, and merged
through to master sometime shortly after.
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: [RELEASES] Getting ready for NetBeans 15 branching
Posted by Jaroslav Tulach <ja...@gmail.com>.
Dne středa 29. června 2022 16:16:39 CEST, Neil C Smith napsal(a):
> It's not a release team job to decide what gets merged -
> that's for all reviewers. And primarily, in my mind, the PR author
> should be making the initial call. I'd like to suggest that all
> descriptions on PRs for delivery, at least when not linked to an
> issue, should include a short justification for inclusion. Thoughts?
Example: https://github.com/apache/netbeans/pull/4422
Justification done. Reviewers are fine with the merge to delivery. Who is
supposed to merge? Me or release coordinator?
-jt
---------------------------------------------------------------------
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