Jaap Keuter wrote:
> Having a develoment trunk and release branches just take more management
> around the time of the branch. Calm down on the new stuff, focus on
> bugfixes then branch and work only on the stability of the branch. Have a
> look at the Linux kernel development process, they face the same problems.
OK, no one likes trunk-1.0, apparently. :) Here's an updated list of
what I'd like to do:
Create a "/prerelease" directory in SVN, and copy the 0.99.1pre1
revision to "/prerelease/wireshark-0.99.1pre1. (Bryant, will this
meet your needs?)
Create "/historic" and move "/trunk-1.0", "/branches", and "/tags"
there.
For each release, do the following:
Copy "/trunk" to "/trunk-<version>".
For each prerelease, copy "/trunk-<version>" to
"/prerelease/wireshark-<version>.pre<x>".
For the final release, move "/trunk-<version>" to
"/releases/wireshark-<version>"
This is a slight variation on what we were doing before, which was to
copy "/trunk" directly to "/releases/<release name>".
I'd like to create "/trunk-0.99.2" as soon as the current fuzz bugs are
fixed, followed by a 0.99.2pre1 release, followed by the full release.
