That seems reasonable to me. > On Mar 30, 2020, at 10:19 AM, Matt Juntunen <matt.juntu...@hotmail.com> wrote: > > The issue I saw with the site [1] was that the text under the Releases > section says "There is no offcial release yet. Come and join development > work!" Clearly, that won't work for a release version. > > Also, the Nexus staging repository (1496) failed validation because it could > not find my key in a public key server. I thought I had added it but > apparently it didn't work. > > -Matt > > [1] https://home.apache.org/~mattjuntunen/commons-numbers-1.0-B1-RC1-site/ > ________________________________ > From: Rob Tompkins <chtom...@gmail.com> > Sent: Monday, March 30, 2020 10:13 AM > To: Commons Developers List <dev@commons.apache.org> > Subject: Re: [numbers] 1.0-B1 Release Proposal > > > >> On Mar 30, 2020, at 10:11 AM, Gary Gregory <garydgreg...@gmail.com> wrote: >> >> On Mon, Mar 30, 2020 at 9:58 AM Alex Herbert <alex.d.herb...@gmail.com >> <mailto:alex.d.herb...@gmail.com>> >> wrote: >> >>> >>> On 30/03/2020 14:27, Gary Gregory wrote: >>>> If "B" stands for "Beta", then make the POM version "1.0-beta1", no need >>>> for mystery. >>> >>> In Matt's defence I think he was following the naming conventions from >>> the commons versioning guide [1]. That uses: >>> >>> "Beta releases are denoted by adding "B<beta version number>" >>> >>> I think that the explicit Beta is clearer. So should it be updated on >>> the versioning page to state you can use either 'B' or 'Beta' or >>> modified to enforce the use of "Beta<beta version number>"? >>> >> >> Most people know what a 'beta' version is, but 'B' is too cryptic IMO. I'll >> pool the ML. > > B1 was clear to me, but I agree that more specificity is always better. > > -Rob > >> >> Gary >> >> >>> >>> [1] https://commons.apache.org/releases/versioning.html >>> <https://commons.apache.org/releases/versioning.html> >>> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >>> <mailto:dev-unsubscr...@commons.apache.org> >>> For additional commands, e-mail: dev-h...@commons.apache.org >>> <mailto:dev-h...@commons.apache.org>
--------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
