THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
This page is meant to list the steps needed to submit a change to Subversion. So it is meant as a help to JMeter committers.
Preparation
- Look in Bugzilla if there are any open bugs or enhancements that are related to the changes you are planning on doing.
- Discuss new functionality on JMeter Development mailing list if necessary
Making changes
- Make the necessary code or documentation changes
Documenting changes
- the xdocs/changes.xml file should be updated
Ant targets to run before committing
- ant package
- ant test
- what else ? (I do not know)
Files to commit
- Changes to files in the docs directory should not be committed, these files are built from xdocs. (Is this correct?)
- Only when release candidates are being made from the Subversion branch should the files in the docs directory be committed. (Is this correct?)
- Only when release candidates are being made from the Subversion branch should the files in the docs directory be committed. (Is this correct?)
Committing to Subversion
- Add a sensible description of your changes when committing to Subversion
- If you have fixed a Bugzilla entry, then include the Bugzilla number in the comment.
- If you have fixed a Bugzilla entry, then include the Bugzilla number in the comment.
Updating Bugzilla entry
- If you have fixed a Bugzilla entry, then set the status to ? ( I do not know what), and include the Subversion change number in the Bugzilla comment.