I've created the branch which will be used to stabilise the jetspeed 1.3a1 release. The branch is called 'release_1_3a1-branch'. To work on this branch you need to do a fresh checkout of the jetspeed module and specify that you want the tag 'release_1_3a1-branch'. For example: cvs checkout -r release_1_3a1-branch jetspeed IMPORTANT: I currently don't seem to be able to check out this branch from the server which always sends me an assert error when I try. I notified Jon and I hope he can resolve this issue quickly... I propose the guidelines when committing to this branch: - only commit code with low regression risk, ie code which does not impact many files and doesn't change any existing method class signatures. - no new features should be added in this branch, all the commits should deal with: - fixing functional bugs - improving stability and/or performance - cleaning up source code - cleaning up documentation - improve documentation - remove dead documents/code If you really feel you need to commit something that doesn't fit these categories, please notify the list before in order to get explicit approval. I propose that all mails related to the clean-up and release process sports a [1.3a1] tag. I'll write a TODO list, send it to the mailing-list and commit it in the branch root. Feel free to update it with your own TODO items and update it regularly when tasks are completed or if you wish to reserve a task for you. I'll try to maximize my online presence this week-end in order to coordonate the release process, but keep in mind that I'm in Paris, so I'm on a GMT+1 timezone, don't expect me to be available at 23:00 PST... -- Rapha�l Luta - [EMAIL PROTECTED] Vivendi Universal Networks - Services Manager / Paris -- -------------------------------------------------------------- Please read the FAQ! <http://java.apache.org/faq/> To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Archives and Other: <http://marc.theaimsgroup.com/?l=jetspeed> Problems?: [EMAIL PROTECTED]
