Etiquette when working on the branch

Etiquette when working on the branch

Tim Hunt發表於
Number of replies: 3
Core developers的相片 Documentation writers的相片 Particularly helpful Moodlers的相片 Peer reviewers的相片 Plugin developers的相片
I am a bit of a newbie when it comes to working on a CVS branch. Is it my responsibility for merging my changes from the branch to head?

And is this the right sort of procedure:
  1. Do the bug fix in my 1.6 branch sandbox.
  2. Test the fix.
  3. Check the fix in.
  4. Use CVS to merge that change into my HEAD sandbox.
  5. Then I check that in.
(Should I also test between 4 and 5? Well, yes, obviously I should. What I mean is how bad is it if I don't?)

評比平均分數: -
In reply to Tim Hunt

Re: Etiquette when working on the branch

Howard Miller發表於
Core developers的相片 Documentation writers的相片 Particularly helpful Moodlers的相片 Peer reviewers的相片 Plugin developers的相片
Tim,

Yes it is your responsibility. You will find specific instructions in the developers area in the docs wiki - you need to follow these to the letter (although for extra safety you can type just the name of the file(s) you are working with on the end of all the commands).

I say this because I found out the hard way ( 臉紅 ) that working on the stable branch is much higher risk - even more so when we come out of beta. The stakes are a whole lot higher!

branches docs....

http://docs.moodle.org/en/CVS_%28developer%29#Stable_branches_for_each_release
In reply to Howard Miller

Re: Etiquette when working on the branch

Tim Hunt發表於
Core developers的相片 Documentation writers的相片 Particularly helpful Moodlers的相片 Peer reviewers的相片 Plugin developers的相片
Wow! read the docs. What a great idea!

So it seems I got it almost right. The one thing I missed was updating the _MERGED tag on the branch, which I have now done.