Good! Attach some dates and we have a release plan!
Since there was talk about feature freeze, I thought we were somewhere
before the release cycle. I didn't really follow the alpha series for
2.2.0, so I wasn't aware that there will be a bunch of them.
The alpha phase can be shortened if there are less features still being
put in. I think it is important to have a first alpha release soon,
along with a plan of what's still going in and when.
As for Loom, I am curious about the white space issue -- whether it can
be fixed before the James release. There might be other 'little' issues
like this that may turn out to be nasty. So it should be thoroughly tested.
Would it be an idea to release James with both Phoenix (not perfect but
well known) and Loom (better but more unknown), with Phoenix the default?
Cheers,
Hes.
Stefano Bagnara wrote:
I thought the 2.3.0 release was coming up shortly?
You mean that it is the right time to put Loom in, just
before releasing the RCs for 2.3.0. Is it correct that your
point is that real testing will be done with the RCs, not
with the trunk?
Cheers,
Let me explain what is the release cycle in my head:
Alpha cycle:
- add new features
- handle bug reports
- test it is working and release an alpha
- fix bugs or delay them to a following alpha/beta
- schedule feature/bug fixes for the releases
Repeat Alpha cycle until your major features are in.
Beta cycle
- handle bug reports
- fix bugs or delay them to a following beta
- test and release a new beta
- schedule bug fixes for the next release
Repeat Beta cycles until your minor features are completed and you have
fixed all the bugs you want to fix
RC cycle
- release a candidate
- wait for show-stoppers
- fix show-stoppers
Repeat RC cycles until you have showstoppers.
Final release
Currently we are in the first step of the Alpha Cycle, you can see that this
is the most distant point from the final release in the release cycle.
Note that the cycles are not binded to "real/solar time": the whole process
can take years or weeks depending on too many factors.
What I would like is to do a fist alpha release as soon as possible so we
start understanding what the roadmap for following Alphas and Betas will be.
We can only plan alphas/betas.
Isn't this the "common" way to operate?
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
