On Fri, 31 Aug 2018 10:35:32 +0200, Benedikt Ritter wrote:
This discussion keeps popping up every few month. At the end we alway
conclude that we don't want to publish anything that's binary
incompatible
under the same coordinates.
There was no such conclusion, as Gary's answer shows:
This discussion keeps popping up every few month. At the end we alway
conclude that we don't want to publish anything that's binary incompatible
under the same coordinates. So way are we discussing this again? Appending
"beta" to a release version will not stop people from using it. So why not
On 30 August 2018 at 15:35, Gary Gregory wrote:
> But SNAPSHOT builds _are_ publicly available on repository.apache.org. Sure
> they come and go and you cannot rely on their permanence.
Just about all our code is available from URLs that don't require logins.
However only formal releases should
What I would love to see it a release of commons-math 3 with an
Automatic-Module-Name for Java 9 modules (potentially the only
change). You could use the release as a way of advertising the
progress towards v4.
Stephen
On Thu, 30 Aug 2018 at 19:16, Gilles wrote:
>
> On Thu, 30 Aug 2018
On Thu, 30 Aug 2018 07:35:12 -0700, Gary Gregory wrote:
But SNAPSHOT builds _are_ publicly available on
repository.apache.org. Sure
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
But SNAPSHOT builds _are_ publicly available on repository.apache.org. Sure
they come and go and you cannot rely on their permanence.
Gary
On Thu, Aug 30, 2018, 04:50 sebb wrote:
> SNAPSHOT builds must only be published to Commons developers.
> They cannot be published on public download
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 in
the usual way.
Once published, they are permanently
What's the difference to a nightly build being published to the Apache
Snapshot repo?
Benedikt
Am Mi., 29. Aug. 2018 um 21:51 Uhr schrieb Gary Gregory <
garydgreg...@gmail.com>:
> We do not have hard rules for betas AFAIK. IMO, only a beta can depend on
> another beta, for example see
We do not have hard rules for betas AFAIK. IMO, only a beta can depend on
another beta, for example see HttpComponents. We should not release a
non-beta that depends on a beta. I think breaking BC is to be expected in
an alpha and less so in a beta. Changing package names and coordinates from
one
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?
10 matches
Mail list logo