Hi, folks.

I've just created a branch to use to continue 1.2 development, enabling 
developers to start committing new shiny stuff to trunk.

--

Every change that only affects 1.2 should go to the 1.2 branch.

Every change that breaks the feature/code/string freeze should go to trunk.

Every change that is intended to both should be, either commited to both or 
committed to the 1.2 branch and clearly be marked in the commit log as "also 
for trunk", I'll take care of merging this changes once a day.

--

Those who want to start committing new stuff to trunk can continue using their 
current SVN working copy.

Those who want to keep commiting stuff to 1.2 (or both), fixing bugs, adding 
new sprites, and so on, should switch their working copy to 1.2 branch, by
running:
svn switch svn+ssh://svn.gna.org/svn/wesnoth/branches/1.2/
(or something similar through the graphical interface you're using).

If you can't manage to successfully switch the working copy you can always 
just do a new checkout:
svn co svn+ssh://svn.gna.org/svn/wesnoth/branches/1.2/ wesnoth-1.2/

If you want to have both 1.2 and trunk working copies, you can just copy the 
whole working copy and run the command only in one.

If anyone has any doubts about where to commit what or how to do something 
just ask.

Best regards

_______________________________________________
Wesnoth-dev mailing list
[email protected]
https://mail.gna.org/listinfo/wesnoth-dev

Reply via email to