I've looked at the Release Planning Template,
https://cwiki.apache.org/confluence/display/OOOUSERS/Release+Planning+Template
It is what I would want to do for a major release with user interface
changes.
We also need something far, far more agile for getting simple bug fix
releases out quickly and easily. I propose using 4.1.3 as a test case
for a stripped down process. Alternatively, this can be regarded as
adding binary distribution to the normal way ASF projects release.
The minimal process will be suitable for releases containing only a
small set of bug fix changes that do not require any changes or
additions to externally displayed strings, and do not make significant
changes to the external interface.
No string changes means we do not need the "String freeze" or
"Translation phase" steps. No significant changes to external
interfaces, combined with a small number of relatively simple fixes,
eliminates the "Beta Release" phase.
We still need to pick the bug fixes to go in the release, construct a
release candidate, test it, write release notes etc.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
