hi Eric,

if this PR would cause another RC and another week delay i think we should leave it out. We can mention on the download page that NB 14 will not work on JDK 19 and users should use a NB 15 dev build for JDK 19 experiments (as suggested on the PR comment). I thought we might be able to add it to rc5.

-mbien

On 24.05.22 12:19, Eric Barboni wrote:
Hi
Eventually delivery is up again for a rc6 as yesterday I try to get rc5 but 
build are not possible.

Eventually for https://github.com/apache/netbeans/pull/4130

Best Regards
Eric

-----Message d'origine-----
De : Michael Bien <>
Envoyé : mardi 24 mai 2022 09:32
À : dev@netbeans.apache.org; Eric Barboni <sk...@apache.org>
Objet : [MESSAGE MARQUE SPAM : BAS]Re: [RELEASES] 14 remaining issues

there would be another candidate for inclusion:
https://github.com/apache/netbeans/pull/4130

please take a look at my comment at:
https://github.com/apache/netbeans/pull/4130#issuecomment-1135513737

best regards,
michael

On 23.05.22 13:15, Eric Barboni wrote:
Hi
   Will try to fix delivery now. I hope nobody needs to PR to that branch.

-----Message d'origine-----
De : Neil C Smith <>
Envoyé : dimanche 22 mai 2022 10:59
À : dev <dev@netbeans.apache.org>
Objet : Re: [RELEASES] 14 remaining issues

Hi,

On Sun, 22 May 2022, 04:27 Jaroslav Tulach,
<jaroslav.tul...@gmail.com>
wrote:

...but when I studied the `delivery` rules the last time, the #1 rule was:
No
mere developer can press the merge button - a release coordinator has to.
If
the rule still applies, then it is the release team who ultimately
decides what to merge into `delivery` (and I am fine with that).

We've never decided what gets merged. The release team handle merges to 
delivery for various scheduling, technical, requirements reasons. We don't 
decide what gets merged (any more than any other committer does anyway).

The PR review process for delivery should cover justifications for why a PR 
needs to go into delivery / the release.

All PRs that pass that review process will be merged to delivery.

Every change to delivery forces another release candidate cycle. Usually that 
adds a week, although we can shorten that a bit. If you open a PR to delivery, 
particularly at this point at the cycle, it is effectively also a request to 
delay the release on it.

Thanks for the additional info on background for this PR. Delivery will need 
fixing before it can be merged, which might require it to be updated.

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



Reply via email to