Reminder: Django 1.1 beta this week means feature freeze

[Jacob Kaplan-Moss]

Hi folks --

Quick reminder that Django 1.1 beta is due to drop Friday. This means
feature freeze -- any feature additions not completed by the beta
timeline won't make it into 1.1. Realistically that means that any
feature addition not already "close" to done should probably be
tabled.

We've got a *lot* of bugs to fix between now and 1.1 final, so I'm
going to ask everyone to keep the definition of "bug" fairly strict
and focus on stability and quality, not features, once the beta drops.

Committers: we've all got good judgement, but I'd suggest that we all
be a bit more bold than usual this week about checking in new
features. Let's not check in crap, but I'd rather get a few more
things done and risk reverting a mistake than the alternative.

Non-committers: if you've got something you want to see in 1.1, you
need to get it reviewed and checked in right away. I've cleared the
rest of my week, so if you've got a feature on 1.1 list but haven't
got a committer, find me on #django-dev or drop me a personal email
and I'll try to help out. No promises, but I'll try.

I'm really looking forward to getting 1.1 out the door -- it's gonna
really kick some ass.

Jacob

[Bob Thomas]

Digging through the (huge) 1.1 milestone list a bit, the following
seem to be closer to improvements than bugs (IMO). If you have any
favorites in here, they should probably be looked at for last-minute
additions to 1.1 beta, or they may be in danger of missing 1.1
entirely:

http://code.djangoproject.com/ticket/6064
Allow database connection initialization commands

http://code.djangoproject.com/ticket/8447
with change in behavior to MultiValueDict.iteritems, there should be a
MultiValueDict.iterlists

http://code.djangoproject.com/ticket/8968
No way to utilize `next` parameter to redirect after comment deletion

http://code.djangoproject.com/ticket/8972
Add ability to delete selected vector features within the Geodjango/
OpenLayers Admin map interface

http://code.djangoproject.com/ticket/9101
Improved salt generation for django.contrib.auth

http://code.djangoproject.com/ticket/9124
SelectDateWidget not usable with required=False

http://code.djangoproject.com/ticket/9147
FormPreview needs easier extensibility

http://code.djangoproject.com/ticket/9167
shutdown_message option missing in runserver.py

http://code.djangoproject.com/ticket/9310
404 debug pages should show the name of the tried urlpattern if one
exists.

http://code.djangoproject.com/ticket/9344
TemporaryFile is missing the 'tell' method on Windows platforms

http://code.djangoproject.com/ticket/9404
Proxy file-like methods and attributes in UploadedFile objects

http://code.djangoproject.com/ticket/9460
Template blocks for submit buttons in admin's change view

http://code.djangoproject.com/ticket/9666
ssi tag don't works with context variables

http://code.djangoproject.com/ticket/9686
GeoDjango should support the sqlite3 back end via SpatiaLite

http://code.djangoproject.com/ticket/9745
Add support of PostGIS's SnapToGrid function

http://code.djangoproject.com/ticket/9779
Adding Foreign Key detection to SQLite inspectdb

http://code.djangoproject.com/ticket/9877
More Pythonic mutations of geometry objects

http://code.djangoproject.com/ticket/9881
Auth login should pass current_site to template, not current_site.name

http://code.djangoproject.com/ticket/9966
Generic view "redirect_to" to carry existing query string

http://code.djangoproject.com/ticket/10043
widthratio tag does not accept a variable as the max_width argument

http://code.djangoproject.com/ticket/10047
TemporaryFile.seek has bad interface under Windows NT

http://code.djangoproject.com/ticket/10106
default admin config for User should include is_active filter

http://code.djangoproject.com/ticket/10130
Support setting deletion

http://code.djangoproject.com/ticket/10134
unique_for_* broken?

http://code.djangoproject.com/ticket/10146
Support for contrib/markdown extension_configs in settings.py

http://code.djangoproject.com/ticket/10166
Cookie test fails in login() view

http://code.djangoproject.com/ticket/10190
Charset should be customizable with HttpResponse

http://code.djangoproject.com/ticket/10222
Add line_merge to GEOS geometries under django.contrib.gis

http://code.djangoproject.com/ticket/10326
Allow handler500, handler404 to be callables

http://code.djangoproject.com/ticket/10327
Pass document.domain to popup windows in admin

http://code.djangoproject.com/ticket/10360
allow customized forbidden message when using exceptions

http://code.djangoproject.com/ticket/10370
re-implement MultiValueDict.itervalues() to match values()

http://code.djangoproject.com/ticket/10460
Better redirect for logout view of Authentication


(list is non-inclusive and unofficial; I'm not a committer)

-bob

[Jacob Kaplan-Moss]

On Thu, Mar 19, 2009 at 3:54 PM, Bob Thomas <robert....@gmail.com> wrote:
> Digging through the (huge) 1.1 milestone list a bit, the following
> seem to be closer to improvements than bugs (IMO). If you have any
> favorites in here, they should probably be looked at for last-minute
> additions to 1.1 beta, or they may be in danger of missing 1.1
> entirely:

Wow, Bob, thanks for doing this -- this is a good list of stuff to
glance at over the next couple days.

As you note, there's a grey area between "feature" and "bug", and
nobody's going to complain too harshly if something like #10326
(handler404/500 as callables) gets considered a "bug" and committed
next week. However, you're completely right that the more we stabilize
APIs *before* the the beta, the better.

Jacob

[Bob Thomas]

On Mar 19, 4:59 pm, Jacob Kaplan-Moss <jacob.kaplanm...@gmail.com>
wrote:

> On Thu, Mar 19, 2009 at 3:54 PM, Bob Thomas <robert.w.tho...@gmail.com> wrote:
> > Digging through the (huge) 1.1 milestone list a bit, the following
> > seem to be closer to improvements than bugs (IMO). If you have any
> > favorites in here, they should probably be looked at for last-minute
> > additions to 1.1 beta, or they may be in danger of missing 1.1
> > entirely:
>
> Wow, Bob, thanks for doing this -- this is a good list of stuff to
> glance at over the next couple days.

You're welcome :-)
I have *even more* of an appreciation for you reviewing all of those
tickets to put them in the 1.1 milestone in the first place.

>
> As you note, there's a grey area between "feature" and "bug"
>

One trend I noticed was that there were quite a few GIS tickets that
aren't really in that grey area at all. Without a champion, they seem
most likely to miss 1.1 (assuming contrib apps are subject to the same
strict definition of "bug" after the beta is released).

-bob

[Jacob Kaplan-Moss]

On Thu, Mar 19, 2009 at 4:09 PM, Bob Thomas <robert....@gmail.com> wrote:
> One trend I noticed was that there were quite a few GIS tickets that
> aren't really in that grey area at all. Without a champion, they seem
> most likely to miss 1.1 (assuming contrib apps are subject to the same
> strict definition of "bug" after the beta is released).

GIS is a bit of a special case; Justin Bronn is the maintainer there,
and he and the rest of the GeoDjango contributors develop somewhat
independently of the rest of Django.

That said, they don't get any special exemptions in terms of timeline,
so GeoDjango feature freeze is this weekend, too.

/me looks meaningfully at Justin.

Jacob

[Jeremy Dunck]

On Thu, Mar 19, 2009 at 4:20 PM, Jacob Kaplan-Moss
<jacob.ka...@gmail.com> wrote:
...

>
> /me looks meaningfully at Justin.

FWIW, I've been a terrible contributor on GIS. All praise to Justin's
great work.

[Antoni Aloy]

2009/3/18 Jacob Kaplan-Moss <ja...@jacobian.org>:

>
> Hi folks --
>
> Quick reminder that Django 1.1 beta is due to drop Friday. This means
> feature freeze -- any feature additions not completed by the beta
> timeline won't make it into 1.1. Realistically that means that any
> feature addition not already "close" to done should probably be
> tabled.
>

What about patches like http://code.djangoproject.com/ticket/5691,
this bugs affects only people working with i18n sites and which has
global catching activate, but it's quite annoying for us, so we'd like
to see it this version if possible.

Best regards,

--
Antoni Aloy López
Blog: http://trespams.com
Site: http://apsl.net

[Alex Gaynor]

That's a bug and therefore fair game for post-beta.  If 1.0 was any indiciation we'll probably have 100+ bugfixes go in before the final release :)

Alex

--
"I disapprove of what you say, but I will defend to the death your right to say it." --Voltaire
"The people's good is the highest law."--Cicero

[Justin Bronn]

> GIS is a bit of a special case; Justin Bronn is the maintainer there,
> and he and the rest of the GeoDjango contributors develop somewhat
> independently of the rest of Django.
>
> That said, they don't get any special exemptions in terms of timeline,
> so GeoDjango feature freeze is this weekend, too.
>
> /me looks meaningfully at Justin.

All of my features have been announced:

http://code.djangoproject.com/wiki/GeoDjango1.1

Realistically some of these features will not be in trunk by the end
of the weekend. Fortunately the majority of them are already complete
in the GeoDjango 1.1 development mercurial, but are waiting more
review/testing, e.g., Aryeh won't be able to review the latest #9877
patch (a non-trivial enhancement) until the end of Sunday. I'm going
to commit them anyway between now and PyCon, unless I'm forced to
sacrifice them at the altar of deadline technicalities. I'd really
hate to tell those folks waiting for SpatiaLite support they'll have
to wait till 1.2 because I didn't prematurely commit the tickets by
midnight on Sunday.

-Justin