Bromine RC4
Posted by pdavid on 2011-03-27 19:43
Short explanation on my recent commit :
Rasmus told me not to do a monster commit so I decides do make a branch.
That way I will be able to mass commit without compromising the project.
Since I'm working at 3 different places i.e : at work ( where I can't commit ), at home ( I'm not really there often ) and at my parent's home ( every week-end ), it means 3 different version.
I think my branch will be ready in a week or so, I still got problems with ajax and some other minor issues. All tickets I opened are ( or will be ) included in my branch.
Phil
Rasmus told me not to do a monster commit so I decides do make a branch.
That way I will be able to mass commit without compromising the project.
Since I'm working at 3 different places i.e : at work ( where I can't commit ), at home ( I'm not really there often ) and at my parent's home ( every week-end ), it means 3 different version.
I think my branch will be ready in a week or so, I still got problems with ajax and some other minor issues. All tickets I opened are ( or will be ) included in my branch.
Phil
Home / Developer API / Tour / Get a Project - Solutions for Bug & Issue Tracking, Collaboration Tools, Subversion Hosting, Git Hosting
Bromine is powered by Assembla.
1 Comments
By rasmuspalm on 2011-04-08 08:31
Here's a nice writeup of svn best practise: http://svn.apache.org/repos/asf/subversion/trunk/doc/user/svn-best-practices.html
To clarify on our commit policy heres my understanding:
- A single commit should reflect a single change (eg. bug fix, new feature, etc.)
- Commits should be made to trunk, UNLESS
- - They are highly experimental / breaks everything / completely new paradigm / major changes to core functionality (i.e. ditch the selenium_server_controller.php, let's only parse xml files for results!)
- Trunk should be kept (somewhat) stable
- Branches should be kept to a minimum: they should be merged as soon as possible
However, since you didn't have commit rights until after you had already made alot of changes you did just the right thing by creating a branch :)
Now you should merge that branch into trunk as soon as possible.
I can't wait to take a look at all the cool changes myself :)
Cheers, Rasmus