Re: Release management policy fundamentals

> When are branches line 1.0.x created (before the first release in the
> 1.0.x line, afterward, or maybe before the next major release)?

A branch is created when a part of the project moves a different
direction, or so I understand. For example, you create a version that
supports something the original version doesn't (or vice versa).

You probably call what I call a tag, a branch (IIRC, in subversion they
are the same thing, it's just the name of the directory). A tag is just
a named version of the trunk. I create a tag when the version in the
trunk is "done" at that moment, e.g. I have released it to my customer,
the customer has reviewed it, and is using it. The tag is just an easy
way to find back a moment in time, ie. the state of the trunk when
released to the customer the first time etc.

> Where
> developers usually work (on the major-release branches or the trunk)?

For me, the trunk

> What happens during release-stabilization periods? etc...

I create a tag, if I understand you correctly.

Just my understanding of things,
John

Just found this one:
https://moin.conectiva.com.br/RepositorySystem

on http://subversion.tigris.org/project_links.html

-- 
John                               MexIT: http://johnbokma.com/mexit/
                            personal page:       http://johnbokma.com/
    Experienced Perl programmer available:     http://castleamber.com/
             Happy Customers: http://castleamber.com/testimonials.html
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org