Scott Eade wrote:
I would actually be keener to see a release sooner without the
checkstyle fixes than later with them, so please do not feel obligated
to complete that task. In fact, addressing these errors may slow us
down in a couple of other ways:
1. A +1 on a release will no longer be automatic - we will each need
to review and test the changes
2. When it comes to porting forward to the trunk and fulcrum
checkstyle fixes may actually result in more effort.
The best approach IMO would be to proceed with the release,
sans-checkstyle fixes, port any fixes and enhancements to the
trunk/fulcrum as necessary, then perhaps look at the checkstyle fixes.
+1
Please, let's get this baby out of the door.
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
