nunit-dev team mailing list archive
-
nunit-dev team
-
Mailing list archive
-
Message #00005
What should we do about lp:nunit-2.5?
Hi All,
The nunit 2.5 mirror on launchpad can no longer be updated. I
merged changes from the 2.5 branch to head so that they would
be available for import to launchpad but ran into a bug in
the conversion program which makes it impossible to import
a cvs project which has added any files to head as the result
of a merge. The bug is two years old, so it doesn't seem
likely that it will be fixed.
I don't want to leave it up as it is, because that encourages
people to branch from old code. That seems to leave two options,
at least as far as I can see...
1. Delete the NUnit 2.5 project on Launchpad and just fix
bugs as needed through cvs.
2. Delete the branch - but not the project - and start a new
branch on launchpad without the cvs history. Continue to fix
bugs on launchpad until there is a new release.
I lean toward #1 myself, since I see no reason to make it
especially easy for folks to extend 2.5 - I'd rather see the
effort go toward 3.0.
What do others think?
Charlie
Follow ups