On Nov 8, 2005, at 10:13 AM, Adrian Holovaty wrote:
On 11/8/05, Robert Wittams <[EMAIL PROTECTED]> wrote:
The general feeling from those using or considering Django (including
some rubyists) seemed to be "Release a 0.7 tarball, for the love
of all
that is holy!"
It seems that quite some people just aren't comfortable with checking
things out of subversion. They don't particularly want backwards
compatibility, just a tarball. This would probably widen the
number of
people willing to use/try out Django.
If all this means is automatically packaging a tarball every couple of
days/weeks, let's do it.
I think we need to bite our lips, suck it up, and release a 1.0
version. It seems that we keep running into feeping-creaturism every
time we try to set a stake in the ground, and that's limiting
adoption. Obviously everyone is unhappy when their tickets aren't
included, but more tickets are being opened than fixed. I think we
need to accept that certain things might not get done, release a 1.0,
and move on.
[Calling it "0.7" would inaccurately represent how stable and usable
Django is, which is why I say 1.0.]
If it sounds OK, I'd like to start a 1.0 release branch and only
apply any outstanding bug fixes to it; moving feature requests/
patches to a 1.1 target. That way we can get a stable 1.0 out the
door and focus on 1.1 for feature improvements.
In terms of backwards-compatibility, it seems most of the big deal
architectural changes have already been done, and as long as we
provide VERY EASY upgrade paths from 1.0 -> 1.x I think we're OK.
So, any objections to starting a 1.0 bug-fix-only release branch?
Jacob
