The question is though, just for clarity, whether we really do need to vote at all if (when) we provide a patch soon after the 11.2 release for a fix to nb-javac, which will mean that only this specific file will need to change:
https://github.com/apache/netbeans/blob/master/nb/updatecenters/extras/nbjavac.impl/release/modules/ext/nb-javac-13-impl.jar.external I.e., the URL and fallback URL and hash will need to change in that module and nothing else. Will we really need to go through a vote process for this change? Gj On Wed, Oct 23, 2019 at 1:19 PM Neil C Smith <[email protected]> wrote: > On Tue, 22 Oct 2019 at 11:13, Neil C Smith <[email protected]> wrote: > > I'm wondering whether if we do ship updates, we trigger a new > > milestone in the release branch, and have a vote on full sources, as > > per normal. Alongside that we nominate specific module convenience > > binaries (nbms) to be added to the mirrors / update centre. > > Two further thoughts on that - > > * we would either need to merge the catalog info to include the new > modules OR we remove the 11.2/nbms folder completely and link to > 11.2-update1/nbms ? Second way simpler, but we end up with new build > versions of all modules. > > * currently the distribution nbms aren't signed as far as I know?! What > are the implications for updates there? > > Some thoughts here would be good! How do we best handle this at ASF? > > Best wishes, > > Neil > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > >
