> On Aug 13, 2017, at 3:04 AM, Emmanuel Lécharny <[email protected]> wrote: > > The issue with our scheme is that if we cut a release and call it 2.0.0, > it will always be seen as inferior to any milstone of RC we created > beforhand. >
How does this issue present itself as a problem? What are the ramifications of this problem? What I’m asking, is this a problem (only) with OSGI related processes, or does it extend outside to things like maven, git, or human-based reasoning? > I suggest we modify teh wy we name our versions in a way that is not > intrusive : > > - release will not be plain numbers, like 2.0.0, but 2.0.0.GA > > - Milestone will be named AM (A does not stand for anything, it's just > used to make sure it's lower than CR and GA) > > - Release Candidate CR (instead of RC). The rational is that AMn < CRn < > GA, so 2.0.0.AM3 < 2.0.0.CR1 < 2.0.0.GA. It's a convention, and I kno The current versioning scheme is simple, intuitive and fits fortress’ needs quite well. Must we change as well? Thanks, Shawn
