On Wed, 10 Jul 2019 at 10:36, Eric Barboni <[email protected]> wrote: > instead of : > https://builds.apache.org/view/M-R/view/NetBeans/job/netbeans-release/lastSuccessfulBuild/artifact/ > > Bits should be the same but they also contains the all the maven artefacts to > avoid recalling a vote later.
That could have been mentioned a little sooner! ;-) > The normal release process is here > https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+Release+README > > To prepare maven artefacts for release > https://cwiki.apache.org/confluence/display/NETBEANS/Publishing+Apache+NetBeans+maven+artefacts > Section> Publishing > Basically it's signing + test signing and then preparing the repository > staging at apache. Yes, I've just been editing and updating the normal release process page. Was not aware of the Maven page and as far as I can tell it's not linked in? What exactly is that Jenkins task doing differently? Is it using the output of the other build task? Are there any other sources involved? At this point, my inclination is to do the vote based on the existing task, bearing in mind we only officially vote on the sources. I'm assuming everything required to achieve the Maven artefacts will be in the source bundle? Thanks, 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
