Reminder: "Must-have" feature freeze in two weeks

6 views
Skip to first unread message

Jacob Kaplan-Moss

unread,
Jul 7, 2008, 2:58:57 PM7/7/08
to django-d...@googlegroups.com
Hi folks --

This is your friendly reminder the three "must-have" features on the
roadmap are due on two weeks -- Django 1.0 alpha is due for release on
July 20th.

We've got two sprints between then and now (see
http://code.djangoproject.com/wiki/Sprints) so I think we're in good
shape to get those things done. However, we need to focus on those
"big three" for the next few weeks.

Can I get a status report on how everyone feels about this date and
the features on the alpha list?

For my part, I plan to work on #2 (oldforms -> newforms in generic
views) late this week. Brian's patch is pretty much perfect, so it's
just a matter of a code review and a check in.

Jacob

Malcolm Tredinnick

unread,
Jul 7, 2008, 10:29:20 PM7/7/08
to django-d...@googlegroups.com

On Mon, 2008-07-07 at 13:58 -0500, Jacob Kaplan-Moss wrote:
> Hi folks --
>
> This is your friendly reminder the three "must-have" features on the
> roadmap are due on two weeks -- Django 1.0 alpha is due for release on
> July 20th.
>
> We've got two sprints between then and now (see
> http://code.djangoproject.com/wiki/Sprints) so I think we're in good
> shape to get those things done. However, we need to focus on those
> "big three" for the next few weeks.
>
> Can I get a status report on how everyone feels about this date and
> the features on the alpha list?

#285 and related WSGI tickets are pretty much done. I think we have as
much as a solution as we're going to have regarding
backwards-compatibility and that change, so I'll check something in in
the next few days.

Malcolm


Ivan Sagalaev

unread,
Jul 8, 2008, 6:48:48 AM7/8/08
to django-d...@googlegroups.com
Jacob Kaplan-Moss wrote:
> Hi folks --
>
> This is your friendly reminder the three "must-have" features on the
> roadmap are due on two weeks -- Django 1.0 alpha is due for release on
> July 20th.
>
> We've got two sprints between then and now (see
> http://code.djangoproject.com/wiki/Sprints) so I think we're in good
> shape to get those things done. However, we need to focus on those
> "big three" for the next few weeks.
>
> Can I get a status report on how everyone feels about this date and
> the features on the alpha list?

Since you're about to do #2 and Malcolm says #3 is essentialy done this
leaves us with newforms-admin only. My call for local sprinters in
Moscow resulted in 20+ participants so I'm optimistic that we'll have
enough eyeballs and hands to work on it. I even think that bugs may come
to an end sooner than the sprint :-).

Russell Keith-Magee

unread,
Jul 9, 2008, 8:40:20 AM7/9/08
to django-d...@googlegroups.com
On Tue, Jul 8, 2008 at 2:58 AM, Jacob Kaplan-Moss
<jacob.ka...@gmail.com> wrote:
>
> Can I get a status report on how everyone feels about this date and
> the features on the alpha list?

Looking outside the alpha list, here's a quick update on the beta
tickets under my purview:

I'm predicting that #7210 isn't going to happen at this point; the
original submitter hasn't responded to comment from Malcolm or myself,
and Nicolas Lara (the aggregation GSOC student) has found a few
problems with the patch at a functional level. This isn't a huge
concern; the syntax can be added later without any backwards
compatibility problems, and there is a natural crossover with what
Nicolas is doing with aggregation.

#6095 is looking good. The only outstanding piece is admin
representation, and Eric Florenzano has indicated he will be sprinting
on this on Saturday. Rob Hudson has found one potential bug, which I'm
about to try and triage. I'll wait until newforms-admin lands in trunk
before I try and commit, but I have little doubt that it will land
soon after that merge.

Yours,
Russ Magee %-)

alex....@gmail.com

unread,
Jul 9, 2008, 1:45:33 PM7/9/08
to Django developers
Russell, if you can post the feedback for #7210 either here, or on the
ticket(or on IRC), I'd try to take a look at fixing it.

On Jul 9, 7:40 am, "Russell Keith-Magee" <freakboy3...@gmail.com>
wrote:
> On Tue, Jul 8, 2008 at 2:58 AM, Jacob Kaplan-Moss
>

Russell Keith-Magee

unread,
Jul 9, 2008, 7:40:38 PM7/9/08
to django-d...@googlegroups.com
On Thu, Jul 10, 2008 at 1:45 AM, alex....@gmail.com
<alex....@gmail.com> wrote:
>
> Russell, if you can post the feedback for #7210 either here, or on the
> ticket(or on IRC), I'd try to take a look at fixing it.

The comments that matter are either on the ticket itself, or have been
posted to django-dev (#7210 as a search keyword is pretty reliable).

I should also point out that Nicolas Lara (the aggregation GSOC
student) has done a lot of work on this area as part of his
aggregation work; before you jump in and potentially duplicate his
efforts, it would be worth checking with him.

One option might be to take on the task of extracting the F() parts
from his aggregation work as an independent patch - this would allow
#7210 to happen for v1.0, while avoiding duplication of effort.

Yours,
Russ Magee %-)

alex....@gmail.com

unread,
Jul 9, 2008, 7:49:40 PM7/9/08
to Django developers
Ok, thanks Russell, Nicholas said he is going to be taking a look at
it during the sprint, so I will try to talk with him then.

On Jul 9, 6:40 pm, "Russell Keith-Magee" <freakboy3...@gmail.com>
wrote:
> On Thu, Jul 10, 2008 at 1:45 AM, alex.gay...@gmail.com

Gary Wilson Jr.

unread,
Jul 12, 2008, 5:43:32 PM7/12/08
to django-d...@googlegroups.com
Jacob Kaplan-Moss wrote:
> For my part, I plan to work on #2 (oldforms -> newforms in generic
> views) late this week. Brian's patch is pretty much perfect, so it's
> just a matter of a code review and a check in.

Jacob, FYI I just posted an updated patch for #3639 [1] that factored out some duplicate code and added a few more tests.

Gary

[1] http://code.djangoproject.com/ticket/3639

Reply all
Reply to author
Forward
0 new messages