On Mon, 13 Jul 2020 at 09:14, Eric Barboni <[email protected]> wrote: > It's possible to get the maven bits alongside a patch release, we only need a > version scheme like RELEASE120-u1 knowing that RELEASE120-1 is taken by > eventually a republish (may happen in the future) > > https://github.com/apache/netbeans-jenkins-lib/edit/master/meta/netbeansrelease.json > mavenversion for release120 need to be updated for version number > RELEASE120-u1 and it should be ok to stage.
It would be great to look at a BOM approach to this for the future, with the modules by spec version. Having to update every Maven module for each update release doesn't seem sustainable if we start having more of them. And be good if the implementation versions remained in sync with the UCs? 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
