Re: 1.2 Beta Thursday
On Thu, Feb 4, 2010 at 5:22 AM, Richard Davieswrote: > On Feb 2, 9:19 pm, James Bennett wrote: >> Also, note that this will be the final feature freeze for 1.2; >> if it ain't in trunk when I roll the tarball, it'll have to wait until 1.3. > > Any chance of getting #10476 and #11156 in? > > Both minor features, but both on the Version1.2Feature wiki page > (under "Small, or Just Bugs" and "Medium priority" respectively) and > both have had working patches since January 1st or earlier. These are both bugs, not features, so there is no procedural need to get them committed before the feature freeze - both can wait till the bugfix period. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
Re: 1.2 Beta Thursday
Is starting the deprecation process for something a feature or a bug? If feature, we should start the process for the psycopg1 backend (discussed here: http://groups.google.com/group/django-developers/browse_thread/thread/ac7874cac8ece97) before Thursday. Near as I can tell it hasn't been marked pending deprecation yet (but then, for the life of me I cannot figure out how to get pending deprecation warnings to display, so perhaps I'm missing something). Karen -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
Re: 1.2 Beta Thursday
On Feb 2, 9:19 pm, James Bennettwrote: > Also, note that this will be the final feature freeze for 1.2; > if it ain't in trunk when I roll the tarball, it'll have to wait until 1.3. Any chance of getting #10476 and #11156 in? Both minor features, but both on the Version1.2Feature wiki page (under "Small, or Just Bugs" and "Medium priority" respectively) and both have had working patches since January 1st or earlier. Thanks, Richard. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
Re: 1.2 Beta Thursday
On Wed, Feb 3, 2010 at 5:19 AM, James Bennettwrote: > I'm kind of choosing this arbitrarily, but as far as I can tell we > should be good to go for rolling a beta any time. So I'm picking > Thursday. > > If there are any blockers I'm not aware of, let me know. Also, note > that this will be the final feature freeze for 1.2; if it ain't in > trunk when I roll the tarball, it'll have to wait until 1.3. I'm fine with Thursday (or earlier, if the whim takes you). We have bugs, but nothing that can't wait till the bugfix phase (e.g., #7190 boolean fixes for MySQL) Before you do roll the tarball, I might draw your attention to #11520 - it's pointing at something that needs to be tweaked in your release script. Russ %-) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
1.2 Beta Thursday
I'm kind of choosing this arbitrarily, but as far as I can tell we should be good to go for rolling a beta any time. So I'm picking Thursday. If there are any blockers I'm not aware of, let me know. Also, note that this will be the final feature freeze for 1.2; if it ain't in trunk when I roll the tarball, it'll have to wait until 1.3. -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.