Advancing Plone One Ticket At A Time
Plone Tune-Up Tips
Just make sure we are all on the same page as we move forward with these Tune-Ups, from time to time I'll send out some tips to make sure we make developing on Plone fun and keep it consistent.
1) If you are committing something please reference the ticket number in the post using the trac keywords refs, closes etc. in front of the ticket number like this: refs #1234
If you mark your commit messages like this, they will get posted on the tickets in trac automagically.
2) Don't forget to merge your changes down from the branches to the various trunks of the products if it is applicable. We want to make sure that our fixes get propagated to all the right spots.
3) Don't forget to update the HISTORY.txt files of the modules you are fixing bugs for on your branch and the trunks when you do your merges.
1) If you are committing something please reference the ticket number in the post using the trac keywords refs, closes etc. in front of the ticket number like this: refs #1234
If you mark your commit messages like this, they will get posted on the tickets in trac automagically.
2) Don't forget to merge your changes down from the branches to the various trunks of the products if it is applicable. We want to make sure that our fixes get propagated to all the right spots.
3) Don't forget to update the HISTORY.txt files of the modules you are fixing bugs for on your branch and the trunks when you do your merges.
Add a Comment
About
© 2009 Created by Gabrielle Hendryx-Parker on Ning. Create a Ning Network!
You need to be a member of Plone Tune-Up Network to add comments!
Join this Ning Network