|Main Archive Page > Month Archives > spamassassin-dev archives|
I think there is major confusion about what a branch is so this is less
a comment on the ongoing discussion and more just clarifying the issue
of branching from my point of view.
> Why? What would we then do for the release scheduled for January?
> Branch it again and call it 3.5?
There would have to be a feature that justified a major release
otherwise January would be a planned release in the branch (i.e. 3.4.1)
> I guess I wouldn't really mind if people wanted to do a branch per
> release. Branch trunk to 3.4.0 for this release, branch trunk to 3.4.1
> in January. Does anybody object to that idea?
3.4.1 is not a branch. 3.4 is a branch. 3.3 is a branch, etc.