[Math] Beta release (Was: [All] What's in a "beta" release?)
On Thu, 30 Aug 2018 07:35:12 -0700, Gary Gregory wrote:
But SNAPSHOT builds _are_ publicly available on
they come and go and you cannot rely on their permanence.
And, perhaps, developers do not check what's available there...
Reports keep coming showing that they don't know about the status
of "Commons Math".
Thus the idea that a beta release might draw to the rejuvenation
attempt. A "beta" because it is still a lot of work to fix all
the identified issues and we need extra help; a "release" because
a lot of work has been done since the last release, providing many
bug fixes and other improvements.
A release of the development version of CM requires the release
of its dependencies: "Commons Numbers" and "Commons Statistics".
Both would be "beta" too.
 And also "Commons Geometry" if the code is in a state that's
able to replace the "o.a.c.math4.geometry" package.
On Thu, Aug 30, 2018, 04:50 sebb <sebbaz@xxxxxxxxx> wrote:
SNAPSHOT builds must only be published to Commons developers.
They cannot be published on public download pages.
Also they may disappear or be replaced at any time.
Beta builds are subject to a release VOTE, and so can be published
the usual way.
Once published, they are permanently available.
On 30 August 2018 at 09:38, Benedikt Ritter <britter@xxxxxxxxxx>
> What's the difference to a nightly build being published to the
> Snapshot repo?
> Am Mi., 29. Aug. 2018 um 21:51 Uhr schrieb Gary Gregory <
>> We do not have hard rules for betas AFAIK. IMO, only a beta can
>> another beta, for example see HttpComponents. We should not
>> non-beta that depends on a beta. I think breaking BC is to be
>> an alpha and less so in a beta. Changing package names and
>> one beta to the next seems a bit excessive but I would not object
>> On Wed, Aug 29, 2018, 10:36 Gilles <gilles@xxxxxxxxxxxxxxxxxxxxx>
>> > Hello.
>> > Do you have an idea of what it would take to automate "beta"
>> > releases?
>> > By this I mean: take a component (at some state) and create
>> > a branch (with all the necessary adaptations) to become an
>> > official release.
>> > Are "beta" releases subject to the same BC requirements as
>> > "ordinary" ones? Concretely, suppose that several releases
>> > will be necessary: Do they have to change top-level package
>> > name?
>> > Can a (non-"beta") release (of some component) depend on a
>> > "beta" release (of another component)? Or has the former to
>> > be a "beta" too?
>> > Rationale: I imagine that uploading to "Maven Central" may
>> > help correcting the misrepresentation of resources available
>> > from this project.
>> > Regards,
>> > Gilles
To unsubscribe, e-mail: dev-unsubscribe@xxxxxxxxxxxxxxxxxx
For additional commands, e-mail: dev-help@xxxxxxxxxxxxxxxxxx