Page History

...

• a filter can be created to send all unresolved issues to the dev list
• JIRA is used as a tracker not a place for discussion
• TODO do we want a separate project for design/best practices discussions
• possibility of setting up a custom workflow
• demonstrate design/practices as opposed to scheduled work
• tagging issues with multiple components so that an issue is marked with its real category but can also be marked with a meta category like "design" or "best practices" which would allow us to group them in a view and be able to report on them
• need to sync all the bits and pieces in jira and confluence so we have a cohesive view of the work that needs to be done and planned for

...

svn copy -m "Create Maven 2.0.x branch" \
svn://svn.apache.org/repos/asf/maven/components/trunk \
svn://svn.apache.org/repos/asf/maven/components/branches/maven-2.0.x

Working on a release branch

...

svn co svn://svn.apache.org/repos/asf/maven/components/branches/maven-2.0.x

Calling a vote for a release

...

mvn release:prepare
...
mvn release:perform
...

• TODO We need to figure out the process of how we tag the RCs, probably don't need to keep them. Maybe just roll over the previous one until the RC is good enough to release.

...

You can find the svnmerge.py script here: http://svn.collab.net/viewvc/svn/trunk/contrib/client-side/^{Image Removed}

Updating the svnmerge-integrated property

...

cd <the-branch>
svn propedit svnmerge-integrated
<start-edit>
/maven/components/trunk:1-368287,368989,369304,<your-revision>
<end-edit>
svn commit

Keep in mind the revisions are revisions on the trunk. So if you started in the branch and merged to the trunk then make sure it's the id of the revision on the trunk!

...