Just to be "PC": I don't care about how you use the label 1.0. Put it
off for years, for all I care (and that seems to fit with the general
perfectionist orientation of the core developers -- I'm not being
sarcastic; this is intended as a compliment).
But please do consider stabilizing on a much simpler milestone, much
sooner. Pick the low-hanging fruit. If nothing else, it will help
the project pick up more volunteers, bug searching, bug fixing, etc.
From: Greg Stein <gstein@lyra.org>
> Unless *you* step up to actually start some coding on the ideas
> that you're expressing, then I don't think you're going to get
> *any* traction here.
I've written quite a bit of code, documentation, and analysis that is
useful to your project and that already self-hosts and demonstrates
and documents the features we've been discussing. In spite of my best
efforts (:-), the arch community is marching on: other people are
actively taking the code even further.
> And back to "we": I personally plan to avoid a lot of the post-1.0 design
> and planning.
I sympathize with the sentiment.
> Being an open source project, it is always a bit difficult to mandate a
> feature freeze, but I think the community has been doing very well here.
> "Big" features get discussed rather than "just going in." People seem to be
> very cognizant of trying to avoid perturbation and getting that 1.0 out the
> door.
You'd think that simplifying the 1.0 agenda in light of deeper
understanding of the technology plus current events in the wacky wacky
world of revision control would be an attractive option to consider.
Let's find a short-term plan to kill BK, for example.
You say yourself that, under current plans, 1.0 is far more than 45
days away. But you've also agreed that there are applications, like
the wiki hack, that are worth doing and that can be largely done with
just what's there already.
Ob Free Software Nut Comment: BitMover is actively sabotaging the
free software community -- the community is in crisis. There are
ethical reasons to step away from your current plans.
-t
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Oct 15 23:00:06 2002