You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Karl Fogel kf...@newton.ch.collab.net on 2003/01/24 16:57:47 UTC
Re: [Issue 1105] Changed - cvs2svn doesn't respect executable bit
Greg Stein gstein@lyra.org writes:
+ cvs2svn issues don't block Subversion 1.0, so they go in Post-1.0,
+ where resides the master cvs2svn issue, issue #514.
Hunh? How can we ship svn without a converter? Our entire purpose is
to replace CVS.
We're already shipping svn without a converter :-).
Could also ask, why wasn't this a big deal before now? We've been
tossing cvs2svn issues into Post-1.0 for ages, starting with the
original issue #514. This is nothing new. But probably you just
didn't notice, or you would have asked earlier...
I completely agree that cvs2svn is important. But the ability to
convert a particular versioned datastore to Subversion is unrelated to
Subversion's own readiness for use. Subversion could be bug-free and
have first-class changeset support... Would we then say Oh, it's not
1.0 yet, because we don't have a tool to convert CVS repositories.?
What about all those people starting new projects? It's not 1.0 for
them? Sure it is.
Maybe the real problem is that we have this milestone label Post-1.0
that we use to mean two different things:
1. This is a Subversion bug, but it need not block a 1.0 release.
2. This bug isn't really about Subversion, so it need not block a
1.0 release.
We could start using the `inapplicable' milestone for category (2), or
use some new nomenclature, if we can think of something clearer.
-K
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [Issue 1105] Changed - cvs2svn doesn't respect executable bit
Posted by Karl Fogel kf...@newton.ch.collab.net.
Greg Stein gstein@lyra.org writes:
Another concept is providing release plans/paths for each of these separate
tools or supporting items. Quite annoying to do, of course :-)
Yeah, that's what I was thinking. Already got our hands full just
tracking svn itself... :-) (And to be realistic, we will continue
tracking cvs2svn, since it's one of the most important tools.)
I'd say a new milestone of separate or non-svn or whatever color your
bikeshed is today. Reserving inapplicable for SVN itself might be nice
(altho what those are... ??)
I'll mull over the paints available for this bikeshed and pick one,
then.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org