What would be ideal would be that VE have
two releases, the regular one continuing with the current version numbers, and one
containing the incubating code with version numbers < 1.0 and marked
incubator in the file names.
Again, the point is that it’s the
code that’s incubating not the project. I don’t remember seeing
anything preventing a project from releasing more than on “thing”.
Speaking of which, that has been a source
of no end of confusion where the “thing” is often called “project”.
I’m not releasing the CDT project, I’m releasing the CDT “thing”
which is managed by the CDT project.
From: tools-pmc-bounces@xxxxxxxxxxx
[mailto:tools-pmc-bounces@xxxxxxxxxxx] On
Behalf Of Bjorn Freeman-Benson
Sent: Monday, October 22, 2007
11:10 AM
To: Ed Merks
Cc: Tools PMC mailing list;
tools-pmc-bounces@xxxxxxxxxxx
Subject: Re: [tools-pmc] RE:
[ve-dev] Contribution on VE with XML editor
Ed, Doug,
How about if we are "flexible" on the rules and allow VE to be
incubating while having a version number > 1.0 ? As long as VE doesn't make
a release (M.N) without clearing the incubation state and as long as they
follow the rest of the incubation labeling rules (the egg, the
"incubating" in file and feature names, etc.) ??
- Bjorn
Ed Merks wrote:
It doesn't seem
reasonable for VE to go back to incubating since that would involve
reseting the version numbers back to below 1.0;
