John,
After rereading my attempt to clarify fell short :)
Bug fixes from JIRAs between now and then can be applied.
Yes, no new features or cosmetic fixes. I thought it was clear we were trying to get a release out
but I guess we need to define it more clearly. My bad.
After the 24 hours the only changes to trunk should be to fix known problems resulting from the
build. If things are horribly broken then they need to be fixed but bug fixes that have been open
for more than 1 year I don't think qualify as critical.
When further problems are identified then we will apply the fixes, release a new candidate and rev
on this process until we as a group are satisfied with the result.
A vote of +1s over a 72-hour period with not -1s would constitute a release. At that point the
final process of changing the version to 1.1, rebuilding, capturing the maven repo, cutting the
source, signing the jars, and moving the results to apache would begin.
Does that clarify my rather terse note?
John Sisson wrote:
Just to clarify..
So bug fixes associated with a JIRA can be committed now (except for new
features and cosmetic changes)?
Are you proposing no changes at all should be made after 24 hours (since
it is a freeze you are notifying us of)? If so, what will the procedure
be if further bugs are found in the release candidate?
Thanks,
John
Matt Hogstrom wrote:
I've been contacted that my communication skills are lacking on the
1.1 release have been negligent so this note is intended to rectify
that observation.
Consider this note a 24-hour branch freeze notification.
As of now
NO NEW FEATURES
NO COSMETIC CHANGES
BUG FIXES RELATED TO JIRA ENTRIES...if you find a bug...open a JIRA
Any changes made to branches 1.1 after 24-hours can be reverted
without notice.
I will cut a build candidate tomorrow after the 24-hour notice which
will incorporate the changes documented about the 1.1 release.
If you are confused, have comments or would like clarification please
post to the dev list and not my private e-mail.
Thanks.
Matt
