Feature lists for 1.2

[Jacob Kaplan-Moss-2]

Hi folks --

Based on the votes and comments I've received for Django 1.2 I've
prepared a breakdown of features into high, medium, and low priority:
http://code.djangoproject.com/wiki/Version1.2Features.

I've noted associated committers and, where I know 'em, lieutenants.
Please make corrections if needed.

If you need clarification as to why a particular feature is classified
where it is, or if you want to see our comments, please check out the
master vote spreadsheet:
http://spreadsheets.google.com/ccc?key=0AtIlKMKDxMBpdGVPVXlTODVLeTBpNkdLd3hqZzdYR3c&hl=en.
I'm happy to clarify anything that's not clear, but please lets not
have an argument about "low" vs "medium" or whathaveyou.

Remember: these are only guidlines. Anything complete by the feature
freeze deadline (December 22nd) is a candidate for inclusion.

So: we've got sixty days to get new features in - let's go!

Jacob

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Django developers" group.
To post to this group, send email to django-developers@...
To unsubscribe from this group, send email to django-developers+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---

[Mikhail Korobov]

Some features from wiki proposal page don't get their way to google
spreadsheet (ex: 2 cache-related proposals) and they are not mentioned
in the final features page neither in a list of accepted features nor
in a list of rejected features. I understand that there are some valid
reasons for that but, out of curiosity, what are their 'official'
status?

On 23 окт, 22:29, Jacob Kaplan-Moss <ja...@...> wrote:

> Hi folks --
>
> Based on the votes and comments I've received for Django 1.2 I've
> prepared a breakdown of features into high, medium, and low priority:http://code.djangoproject.com/wiki/Version1.2Features.
>
> I've noted associated committers and, where I know 'em, lieutenants.
> Please make corrections if needed.
>
> If you need clarification as to why a particular feature is classified
> where it is, or if you want to see our comments, please check out the
> master vote spreadsheet:http://spreadsheets.google.com/ccc?key=0AtIlKMKDxMBpdGVPVXlTODVLeTBpN....
> I'm happy to clarify anything that's not clear, but please lets not
> have an argument about "low" vs "medium" or whathaveyou.
>
> Remember: these are only guidlines. Anything complete by the feature
> freeze deadline (December 22nd) is a candidate for inclusion.
>
> So: we've got sixty days to get new features in - let's go!
>
> Jacob

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Django developers" group.
To post to this group, send email to django-developers@...
To unsubscribe from this group, send email to django-developers+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---

[Jacob Kaplan-Moss-2]

2009/10/23 kmike <kmike84@...>:
> Some features from wiki proposal page don't get their way to google
> spreadsheet (ex: 2 cache-related proposals) and they are not mentioned
> in the final features page neither in a list of accepted features nor
> in a list of rejected features.

That's because they were proposed too late and/or were not clearly specified.

> I understand that there are some valid
> reasons for that but, out of curiosity, what are their 'official'
> status?

Same as everything else: get the code done by December 22nd and it goes in.

Jacob

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Django developers" group.
To post to this group, send email to django-developers@...
To unsubscribe from this group, send email to django-developers+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---

[Joshua Russo-2]

On Fri, Oct 23, 2009 at 5:29 PM, Jacob Kaplan-Moss <jacob@...> wrote:

2009/10/23 kmike <kmike84@...>:

> Some features from wiki proposal page don't get their way to google
> spreadsheet (ex: 2 cache-related proposals) and they are not mentioned
> in the final features page neither in a list of accepted features nor
> in a list of rejected features.

That's because they were proposed too late and/or were not clearly specified.

> I understand that there are some valid
> reasons for that but, out of curiosity, what are their 'official'
> status?

Same as everything else: get the code done by December 22nd and it goes in.

Jacob

So any tickets that have the full gambit of patch/docs/tests should make it into 1.2?

Just trying to get a handle on how the process works.

Thanks

Josh

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Django developers" group.
To post to this group, send email to django-developers@...
To unsubscribe from this group, send email to django-developers+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---

[Jacob Kaplan-Moss-2]

> So any tickets that have the full gambit of patch/docs/tests should make it
> into 1.2?

In theory. Keep in mind, though, that us committers have limited
mental bandwidth so we can't absolutely promise to get to every single
ticket.

I'll do my best, of course, but at the end of the day I'm going to
prioritize the features that the aggregate voice of the community
seems to want most.

Jacob

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Django developers" group.
To post to this group, send email to django-developers@...
To unsubscribe from this group, send email to django-developers+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---

[Joshua Russo-2]

On Fri, Oct 23, 2009 at 11:21 PM, Jacob Kaplan-Moss <jacob@...> wrote:

> So any tickets that have the full gambit of patch/docs/tests should make it
> into 1.2?

In theory. Keep in mind, though, that us committers have limited
mental bandwidth so we can't absolutely promise to get to every single
ticket.

I'll do my best, of course, but at the end of the day I'm going to
prioritize the features that the aggregate voice of the community
seems to want most.

Gotcha, understood. 

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Django developers" group.
To post to this group, send email to django-developers@...
To unsubscribe from this group, send email to django-developers+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---