On Fri, 12 Oct 2018 20:47:23 +0200 Geertjan Wielenga <[email protected]> wrote:
> I don't think there's a need to point to Wikipedias about what a > software release cycle is, do you? :-) I was just trying to express any wiki page I would create on netbeans tagging would follow that format _dev, _alpha, _beta, _rc. It would be redundant like providing a link to that page :) Or like others I have provided say from Gentoo. The ebuild file format, maps almost directly to a given version. Which is where I have to keep being creative for Netbeans. https://devmanual.gentoo.org/ebuild-writing/file-format/index.html#file-naming-rules This is nasty! If its 9.0 -> 9.0-vc3, if its 10.0_rc1 -> 10.0-vc1 https://github.com/Obsidian-StudiosInc/os-xtoo/blob/master/eclass/java-netbeans.eclass#L26 > The problem we're trying to solve is how to name voting candidates > for the Apache process whereby the initial candidates for release > tend to, especially in a large project like NetBeans, get rejected > and then new voting candidates need to be created with clearly > distinguished names. It seems all other Apache projects use -rc for that. If your voting, tag it -rc*, if that vote fails. Then increment the number of the -rc. To me it seems pretty simple and straight forward. Not sure why its such a problem that needs discussing and solving. Even Apache's own documentation says that RCs should be voted on. Release Candidate A source package and other accompanying artifacts to be inspected and voted on in order to release. https://www.apache.org/foundation/glossary.html#ReleaseCandidate -- William L. Thomson Jr.
pgpLAbTWTiUAN.pgp
Description: OpenPGP digital signature
