Re: ANNOUNCE: Django 1.2 beta released
Nice, James. Thanks! On Feb 5, 10:30 pm, James Bennett wrote: > Tonight we've released Django 1.2 beta 1: > > * Blog entry:http://www.djangoproject.com/weblog/2010/feb/06/12-beta-1/ > * Release notes:http://docs.djangoproject.com/en/dev/releases/1.2-beta-1/ > * Checksums:http://media.djangoproject.com/pgp/Django-1.2-beta-1.checksum.txt > > Note that this constitutes final feature freeze for Django 1.2; no > further feature additions will take place before the final Django 1.2 > release. > > -- > "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.
ANNOUNCE: Django 1.2 beta released
Tonight we've released Django 1.2 beta 1: * Blog entry: http://www.djangoproject.com/weblog/2010/feb/06/12-beta-1/ * Release notes: http://docs.djangoproject.com/en/dev/releases/1.2-beta-1/ * Checksums: http://media.djangoproject.com/pgp/Django-1.2-beta-1.checksum.txt Note that this constitutes final feature freeze for Django 1.2; no further feature additions will take place before the final Django 1.2 release. -- "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.
Re: 1.2 Beta tomorrow (Friday)
Hope you feel better today :) On Feb 5, 3:35 am, James Bennett wrote: > Due to a combination of exhaustion and illness on the part of the > release manager (me), I'm going to slide the 1.2 beta release one day; > that means beta tomorrow (Friday, February 5, probably evening-ish US > Central time). If anyone's got last-minute commits, get 'em in. > > -- > "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.
1.2 Beta tomorrow (Friday)
Due to a combination of exhaustion and illness on the part of the release manager (me), I'm going to slide the 1.2 beta release one day; that means beta tomorrow (Friday, February 5, probably evening-ish US Central time). If anyone's got last-minute commits, get 'em in. -- "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.
Re: 1.2 Beta Thursday
On Thu, Feb 4, 2010 at 5:22 AM, Richard Davies wrote: > 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 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. 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 Bennett wrote: > 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.
Re: 1.2 beta?
I would also like to point out: http://code.djangoproject.com/ticket/12600 It does break existing code however, because it will look for the preview template somewhere else. On Jan 28, 2:25 am, Ben Firshman wrote: > On 27 Jan 2010, at 22:50, Ben Firshman wrote: > > > > > On 27 Jan 2010, at 15:36, Russell Keith-Magee wrote: > > >> However, my initial impression: one way to dramatically increase your > >> chances is to make sure the patch applies to trunk, and passes all the > >> tests. Neither of these things are true at present. Using the most > >> recent patch on the ticket, I currently get 4 patch failures. Once I > >> fix those the way I suspect they are meant to be fixed, I get a failed > >> test case (SyndicationFeedTest.test_add_domain). > > > Oh gosh, sorry, I thought I fixed all those problems. I'll get it fixed > > against trunk this evening. > > http://code.djangoproject.com/ticket/12403 > > I've added syndication-view-6.diff which should apply cleanly against r12313, > fixes that test and has a few documentation tweaks. You can see a working > pretty diff on github: > > http://github.com/bfirsh/django/commit/1fac8441b49f690094026fb06189d4... > > Ben -- 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?
On 27 Jan 2010, at 22:50, Ben Firshman wrote: > > On 27 Jan 2010, at 15:36, Russell Keith-Magee wrote: >> >> However, my initial impression: one way to dramatically increase your >> chances is to make sure the patch applies to trunk, and passes all the >> tests. Neither of these things are true at present. Using the most >> recent patch on the ticket, I currently get 4 patch failures. Once I >> fix those the way I suspect they are meant to be fixed, I get a failed >> test case (SyndicationFeedTest.test_add_domain). > > Oh gosh, sorry, I thought I fixed all those problems. I'll get it fixed > against trunk this evening. http://code.djangoproject.com/ticket/12403 I've added syndication-view-6.diff which should apply cleanly against r12313, fixes that test and has a few documentation tweaks. You can see a working pretty diff on github: http://github.com/bfirsh/django/commit/1fac8441b49f690094026fb06189d4f12babac4e Ben -- 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?
On 27 Jan 2010, at 15:36, Russell Keith-Magee wrote: > > However, my initial impression: one way to dramatically increase your > chances is to make sure the patch applies to trunk, and passes all the > tests. Neither of these things are true at present. Using the most > recent patch on the ticket, I currently get 4 patch failures. Once I > fix those the way I suspect they are meant to be fixed, I get a failed > test case (SyndicationFeedTest.test_add_domain). Oh gosh, sorry, I thought I fixed all those problems. I'll get it fixed against trunk this evening. Ben -- 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?
On Wed, Jan 27, 2010 at 9:52 PM, Ben Firshman wrote: > On 25 Jan 2010, at 18:55, Jacob Kaplan-Moss wrote: > > Are we on track for releasing a 1.2 beta this week? > > That'd match our original schedule, but we did miss 1.2 alpha by a > week or so, so perhaps we should push back the beta to match? Or is > everyone happy with progress to date and ready to lock things down? > > I suppose it's too late for #12403 isn't it? > http://code.djangoproject.com/ticket/12403 It's not necessarily too late. There are a couple of bugs in the admin UI (#12692, #12705) that need to be fixed, and there was talk this morning (my time) of fixing #7190. IMHO, we should fix these before we cut a beta. Based on Jacob's past comments, the holdup has been the core team finding time, not something fundamental with the code. I should have a chance to take a good look and confirm this tomorrow evening (my time). However, my initial impression: one way to dramatically increase your chances is to make sure the patch applies to trunk, and passes all the tests. Neither of these things are true at present. Using the most recent patch on the ticket, I currently get 4 patch failures. Once I fix those the way I suspect they are meant to be fixed, I get a failed test case (SyndicationFeedTest.test_add_domain). 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?
On 25 Jan 2010, at 18:55, Jacob Kaplan-Moss wrote: Are we on track for releasing a 1.2 beta this week? That'd match our original schedule, but we did miss 1.2 alpha by a week or so, so perhaps we should push back the beta to match? Or is everyone happy with progress to date and ready to lock things down? I suppose it's too late for #12403 isn't it? http://code.djangoproject.com/ticket/12403 Ben -- 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?
On Tuesday 26 January 2010 11:30:45 Florian Apolloner wrote: > Hi, > > I am far away from beeing a commiter, but would like to get some > thoughts about the AnonymousUser permission checks written down > (I'll keep it short to not hijack this thread): By the time I > moved permission checks to the backends I didn't thought much > about anonymous users (I guess that was bad, but by that time I > never needed it). The current situation is as follows: If we pass > the AnonymousUser into the backend we will berak any code that > relied on the User object to be in the database [disclaimer: as > far as I can tell, we always said that the programmer should check > if the User is authenticated or not, but as we never passed > AnonymousUser into the backends I doubt someone checks that. > Though I guess most people used the backends to check against ldap > etc, so this would be a non issue…]. If you are okay with that, I > am +1 on whatever needs to be done to get this feature in. That's a good catch. Previously I was thinking that the change only affected the "per object" code, which was added since 1.1. The changed required to handle AnonymousUser is pretty simple, as demonstrated by the patch on the provided auth backend. However, it could easily catch people out. One possible migration strategy is to add a 'supports_anonymous_user' attribute, similar to 'supports_object_permissions'. Luke -- "The first ten million years were the worst. And the second ten million, they were the worst too. The third ten million, I didn't enjoy at all. After that I went into a bit of a decline." (Marvin the paranoid android) Luke Plant || http://lukeplant.me.uk/ -- 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?
Am 26.01.2010 um 12:30 schrieb Florian Apolloner: > I am far away from beeing a commiter, but would like to get some > thoughts about the AnonymousUser permission checks written down (I'll > keep it short to not hijack this thread): By the time I moved > permission checks to the backends I didn't thought much about > anonymous users (I guess that was bad, but by that time I never needed > it). The current situation is as follows: If we pass the AnonymousUser > into the backend we will berak any code that relied on the User object > to be in the database [disclaimer: as far as I can tell, we always > said that the programmer should check if the User is authenticated or > not, but as we never passed AnonymousUser into the backends I doubt > someone checks that. Though I guess most people used the backends to > check against ldap etc, so this would be a non issue…]. If you are > okay with that, I am +1 on whatever needs to be done to get this > feature in. As mentioned in the other thread, I'm sceptical about adding more meaning to the AnonymousUser (making it a workflow item instead of a placeholder for "this request was made by a non-authorized user"). -0 The major issue here is backwards compatibility though. I'd be glad to know how we'd handle this. > Aside from that I would like to know what the status on admin-ui is, > as Janis worked on that lately. That said I don't see any real reason > why we would need to postpone the beta. This is indeed on my today's todo list, I worked on it during the sprint last weekend. Jannis -- 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?
Hi, I am far away from beeing a commiter, but would like to get some thoughts about the AnonymousUser permission checks written down (I'll keep it short to not hijack this thread): By the time I moved permission checks to the backends I didn't thought much about anonymous users (I guess that was bad, but by that time I never needed it). The current situation is as follows: If we pass the AnonymousUser into the backend we will berak any code that relied on the User object to be in the database [disclaimer: as far as I can tell, we always said that the programmer should check if the User is authenticated or not, but as we never passed AnonymousUser into the backends I doubt someone checks that. Though I guess most people used the backends to check against ldap etc, so this would be a non issue…]. If you are okay with that, I am +1 on whatever needs to be done to get this feature in. Aside from that I would like to know what the status on admin-ui is, as Janis worked on that lately. That said I don't see any real reason why we would need to postpone the beta. Cheers, Florian -- 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?
On Tue, Jan 26, 2010 at 9:05 AM, Russell Keith-Magee wrote: > On Tue, Jan 26, 2010 at 2:55 AM, Jacob Kaplan-Moss wrote: >> Hey folks -- >> >> Are we on track for releasing a 1.2 beta this week? >> >> That'd match our original schedule, but we did miss 1.2 alpha by a >> week or so, so perhaps we should push back the beta to match? Or is >> everyone happy with progress to date and ready to lock things down? > > I'd like a chance to commit #6587 (which is pretty much ready to go), > have a serious look at #7270, and slip in a couple of translation > updates. A couple of days should be enough. > > However, other than that, I'm happy with where we are. I could > certainly live with a release cut from trunk right now. Going back through my inbox, I discovered one more - are we going to put #8425 (USStateField) out of it's misery? I think James and I came to a final position of having USStateField (50+DC) and USPostalField (50+DC+military drops, protectorates etc), with bunch of easy to use lists that could be composed for choices if you wanted to customize either one (e.g., USStateField(choices=LOWER_48+PROTECTORATES) ). The change is trivial once we agree what we're going to do - do we want to do it? 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.
Re: 1.2 beta?
On Tue, Jan 26, 2010 at 7:09 AM, Luke Plant wrote: > On Monday 25 January 2010 18:55:34 Jacob Kaplan-Moss wrote: >> Hey folks -- >> >> Are we on track for releasing a 1.2 beta this week? >> >> That'd match our original schedule, but we did miss 1.2 alpha by a >> week or so, so perhaps we should push back the beta to match? Or is >> everyone happy with progress to date and ready to lock things down? > > I'd like to check in ticket 12557 before the beta, but I'm not sure on > the status of the discussion. By the end, the were some good > arguments in favour, Jannis was somewhere between -0 and +0 I think, > but there wasn't any feedback from the other committers. I haven't looked at the patch in any detail, but on a conceptual level, allowing anonymous users to have permissions determined by the backend makes sense to me. +1. 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.
Re: 1.2 beta?
On Tue, Jan 26, 2010 at 2:55 AM, Jacob Kaplan-Moss wrote: > Hey folks -- > > Are we on track for releasing a 1.2 beta this week? > > That'd match our original schedule, but we did miss 1.2 alpha by a > week or so, so perhaps we should push back the beta to match? Or is > everyone happy with progress to date and ready to lock things down? I'd like a chance to commit #6587 (which is pretty much ready to go), have a serious look at #7270, and slip in a couple of translation updates. A couple of days should be enough. However, other than that, I'm happy with where we are. I could certainly live with a release cut from trunk right now. 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.
