On Tue, 30 Jun 2020 at 07:06, Laszlo Kishalmi <[email protected]> wrote: > We are planning to release 12.0.1 in middle of July if everything goes > right. I'm volunteering as an RM for that release.
Great! Now just need an RM for 12.1. :-) Are we definitely going with 12.0.1 over 12.0-u1? We used -u1 for 11.2. Either way fine with me, but we should probably document this time and stick to it in future? > Let's try to identify the scope: The reason for having a 12.0(.1 / -u1) originally was the update for nb-javac. I doubt that's going to make it, or even know where it's got to?! And probably deserves more testing on master before pushing to a release anyway. > If the PR is merged, then you have the time till Monday morning to mark > the PR-s you would like to see in 12.0.1 with the "NB12.0.1" label on GitHub Maybe should use a milestone - that was decided for versions over labels a few releases back, and has benefits for archiving. Junichi's thread at https://lists.apache.org/thread.html/7cf6c75bffa26adf7357f0e638eec490f22697905edcea04268bdb47%40%3Cdev.netbeans.apache.org%3E > but be aware to change the patch version number on the module > manifest.mf in addition to the changes in the original PR. Being very careful that the patched version is less than the one in master. > I would like to create a release bundle mid next week we are going to > vote on it. We are going to vote on the full source, however as it would > be a patch release, the binary release would be only the changed nbm-s. > No Maven, no javadoc, no installer. just the NBM-s on the 12.0 UC. And splicing of the new entries into the update centre catalogue XML for 12.0 on the VM, with full links (rather than relative links) via closer.lua. Which requires careful escaping - I only broke updates for half an hour! ;-) For the 11.2-u1 vote an extra update centre was made available during the vote so people could test installing the NBMs - not via closer.lua though, obviously - see https://lists.apache.org/thread.html/0e8607fb94bbe5f9e3bc620a3e516a4a4a7c97c1b23f5305731d4ee6%40%3Cdev.netbeans.apache.org%3E The xml.u1 as suffix is needed because of the current redirect pattern on the VM. It would be really good to test NBM updates as part of this, however, I'm not sure how easy it would be to add an extra UC as trusted, and thus check the signatures in the XML and trouble free installation. At least the trusted mechanism means you no longer have the fun of mangling the NBMs through Apache's JAR signing process! :-) I realise you did a lot of those steps with the 11.0 update, but a few changes to build process and VM config since, including that UC catalog is no longer, and cannot be, served via the mirrors. Give Eric or I a shout if anything isn't properly documented! 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
