On Wed, 10 Jul 2019 at 12:43, Eric Barboni <sk...@apache.org> wrote: > I guess that the "new" Jenkins task do the same than the release job (need > review to be sure)).
Yes, not exactly filling me with confidence there! :-) Anyway, other build tasks (Snap, Installers, etc.) rely on the netbeans-release task. Ideally all the Maven stuff would too, or we switch everything over to the new pipeline. But, an email literally 5min before I was triggering the voting candidate build, and without us having used that pipeline for any of the betas or tested with any of the depending tasks, doesn't feel right. So, unless we intend to push the schedule back by at least a week to fit in another beta, my intention is to go ahead with a vc off of netbeans-release today. Then we can figure out what's missing and how to get it in place ... > AFAIK, we vote also the nbm files as conveniences libraries, so maven > artefact are part of this concept. We don't vote on the nbms or the binaries of the IDE or platform. We vote on the sources. See eg. http://www.apache.org/legal/release-policy.html#compiled-packages The important thing is that all the source required to build the binary artefacts is in the source releases we vote on. I'm assuming this is the case, even if we might be missing some instructions? The PMC also has responsibility to ensure any convenience binaries are correctly made, signed, etc. But AFAIK we can have a sanity check thread about them after the release vote if necessary. Thanks and 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
