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 < [email protected]>: > 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 beta to the next seems a bit excessive but I would not object to it. > > Gary > > On Wed, Aug 29, 2018, 10:36 Gilles <[email protected]> wrote: > > > 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: [email protected] > > For additional commands, e-mail: [email protected] > > > > >
