In revisions 9102 and 9103, I committed the changes to django.VERSION
and django.get_version() announced previously[1].
To recap:
The VERSION tuple in trunk is now (1, 1, 0, 'alpha', 0), and
get_version() in trunk now prints "1.1 pre-alpha SVN-9103".
The VERSION tuple in the 1.0.x branch is now
On 21 Wrz, 14:35, Fredrik Lundh <[EMAIL PROTECTED]> wrote:
> kubiku wrote:
> > May I suggest using word "stable" instead of final? While "final" is
> > great mood improver for internal django developers, "stable" gives
> > stronger message to django users and especially their bosses. And
> > bring
kubiku wrote:
> May I suggest using word "stable" instead of final? While "final" is
> great mood improver for internal django developers, "stable" gives
> stronger message to django users and especially their bosses. And
> brings more assurance that it means what it means. Final is, well,
> some
On Sep 17, 5:25 am, "James Bennett" <[EMAIL PROTECTED]> wrote:
> * For the final 1.1 release: (1, 1, 0, 'final', 0).
May I suggest using word "stable" instead of final? While "final" is
great mood improver for internal django developers, "stable" gives
stronger message to django users and especia
On Wed, Sep 17, 2008 at 4:25 AM, James Bennett <[EMAIL PROTECTED]> wrote:
> I'm writing this mostly as an explanation of what I plan to do; if
> there aren't any well-founded objections, I'll make the necessary
> changes and commit them before we create the 1.0.x branch.
We've talked about this i
A while back I proposed changing the way the ``django.VERSION`` tuple
is set up. That discussion petered out a bit, until I brought it up
with Jacob just before the 1.0 release. At the time, we felt it wasn't
possible to do it before we rolled 1.0 (this was, due to my
absent-mindedness, about ten
