At Saturday 2005-04-02 16:57, you wrote:
"Victor A. Wagner Jr." <vawjr@rudbek.com> writes:
At Saturday 2005-04-02 11:10, you wrote:
I'll agree again. The changes I check in when we are in release mode (have a release branch active) _always_ go to both the trunk and the branch. The branch doesn't help me in any way.
Apr 15: feature freeze Release "when it's done"
If "when it's done" is short enough, e.g. 2-3 weeks, then it's not even worth branching. Better to just concentrate on getting kinks out for the release. Is this at all realistic?
the reason for the branch is to that those developers who need to work on stuff NOT related to the release have someplace to put their "commits".
In that case you and Doug have different things in mind.
I didn't see anything that Doug said that disagrees. he hasn't said anything about people working on stuff other than the release
I predict this whole thing is going to cause lots of confusion and chaos unless people get it very clear (quickly) what's happening and make sure it's well advertised.
-- Dave Abrahams Boost Consulting www.boost-consulting.com
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Victor A. Wagner Jr. http://rudbek.com The five most dangerous words in the English language: "There oughta be a law"