On 6/19/06, Matt Hogstrom [EMAIL PROTECTED] wrote:
Tony,
The 1.1 branch is close and not accepting updates. It is currently located at
branches/1.1.0 and
will me moved to tags/1.1.0 when the final approval vote goes through.
branches/1.1.1 is ready for updates but we haven't agreed on the
Hi,
On Fri, Jun 16, 2006 at 12:40:03AM -0400, Matt Hogstrom wrote:
Working copies of versions in branches would be branches/n.n. This would
be the effective trunk for any version work.
Does this mean that someone will be re-creating a branches/1.1 branch?
There used to be one, and it looks
Done.
On Jun 19, 2006, at 11:36 AM, toby cabot wrote:
Hi,
On Fri, Jun 16, 2006 at 12:40:03AM -0400, Matt Hogstrom wrote:
Working copies of versions in branches would be branches/n.n.
This would
be the effective trunk for any version work.
Does this mean that someone will be re-creating
Hi David,
Done.
Thanks!
Toby
Oh, I see. There is already a 1.1.1 branch. My bad.
Sorry, going to delete the branches/1.1 and call for a vote.
-David
On Jun 19, 2006, at 2:54 PM, toby cabot wrote:
Hi David,
Done.
Thanks!
Toby
On 6/16/06, Matt Hogstrom [EMAIL PROTECTED] wrote:
Here is what I got from the thread and think makes a lot of sense.
Working copies of versions in branches would be branches/n.n. This would be
the effective trunk for
any version work.
When the team has decided that work is done and the
Here is what I got from the thread and think makes a lot of sense.
Working copies of versions in branches would be branches/n.n. This would be the effective trunk for
any version work.
When the team has decided that work is done and the release process begins the branches/n.n would be
