Would not it be better to make /trunk-1.0 as late as we have implemented all features planned for 1.0.0?
Then the /trunk-1.0 would continue only with bug fixies.
I am affraid when we make /trunk-1.0 now we will come to the same conclusion during next release, i.e. to forgot /trunk-1.0 and use /trunk.
________________________________
Od: wireshark-dev-bounces@xxxxxxxxxxxxx za uživatele Gerald Combs
Odesláno: pá 30.6.2006 21:25
Komu: wireshark-dev@xxxxxxxxxxxxx
Předmět: [Wireshark-dev] Next release (plus SVN and roadmap changes)
We're overdue for an official Wireshark release. A couple of people
have pointed out that the code in /trunk is in better shape than
/trunk-1.0, and that we might be better off using it for future
releases. I agree.
I'd like to make the following changes in the repository, which would
address this as well as clean up a few other issues:
Create a "/prerelease" directory in SVN, and copy the 0.99.1pre1 tree
there. Future prereleases will be copied there as well.
Move the current "/trunk-1.0" directory to "/branches/old-trunk-1.0".
Copy "/trunk" to "/trunk-1.0".
I'm tempted to create a "/historic" directory and move "/branches" and
"/tags" there. These were created during the migration from CVS to
Subversion, and don't really have any bearing on the current
repository layout.
If anyone is still doing active development in any moved directories,
they should be able to use "svn switch" to point their copy to the
right place.
I'd also like to make the following changes to the roadmap:
Mark 0.99.1 as "abandoned".
Bump the 0.99.x (x > 0) micro release versions by 1, e.g. 0.99.1 will
become 0.99.2, etc.
This means that the next release will be 0.99.2, and that the code will
come from what's currently in "/trunk".
_______________________________________________
Wireshark-dev mailing list
Wireshark-dev@xxxxxxxxxxxxx
http://www.wireshark.org/mailman/listinfo/wireshark-dev
<<winmail.dat>>
