Django 1.5 release plans
Hi folks -- I wanted to fill everyone in on our plans for the Django 1.5 release. The highlights are: * Feature freeze October 1st, final out before Christmas. * One marquee feature of Django 1.5 is experimental Python 3 support. This is where we need your help the most: we need to be sure that our support for Python 3 hasn't destabilized Django on Python 2. We need lots of testing here! * Most features of 1.5 have already landed, but we're also hoping to land the new pluggable User model work, add support for PostGIS 2.0, start the process of deprecating django.contrib.localflavor, and a few other small things. * This'll be our first "master never closes" release: work, including new features, can continue to land on master while we ship the release. Please read on for details. Timeline Oct 1: Feature freeze, Django 1.5 alpha. Nov 1: Django 1.5 beta. Nov 26: Django 1.5 RC 1 Dec 10: Django 1.5 RC 2 Dec 17: Django 1.5 RC 3, if needed Dec 24 (or earlier): Django 1.5 final (All dates are "week of" - we'll do the releases that week, though not neccisarily that exact day.) Notice the longer-than-usual timeline from beta to final. We're doing this to provide some extra time stablizing the release after landing the Python 3 work. Please see below for details and how you can help. Python 3 support Django 1.5 includes experimental support for Python 3 (it's already landed on master). We're taking a "shared source" approach: Django's code is written in a way that runs on both Python 2 and Python 3 (without needing 2to3's translation). This means that we've touched nearly the entire codebase, and so the surface area for possible bugs is huge. WE REALLY NEED YOUR HELP testing out Django 1.5 *on Python 2*. Please grab master, or one of the upcoming alpha/beta/RC releases, and test it against your apps and sites. We need you to help us catch regressions. We're not yet recommending that people target Python 3 for deployment, so our main focus here is ensuring that we're still rock-solid on Python 2. If you *want* to give Python 3 a whirl things should be pretty solid, but we *especially* need real-world reports of success or failure on Python 2. Features in 1.5 --- Besides the stuff that's already landed (see https://docs.djangoproject.com/en/dev/releases/1.5/), there are a few other features we're hoping to land: * The "pluggable User model" work (Russell Keith-Magee). * Some early low-level schema alteration plumbing work (Andrew Godwin). * Moving django.contrib.localflavor out into individual external packages (Adrian Holovaty). * Support for PostGIS 2.0 (Justin Bronn). * Python 3 support in GeoDjango (Aymeric Augustin). * App-loading (Preston Holmes) is "on the bubble" - there's some debate among the core team over whether its ready, but it's close. Of course, as with our previous releases, the *real* list of what'll go in 1.5 is "whatever's done by October 1st". If you want to help with any of the above areas, contact the person doing the bulk of the work (listed above) and ask to help. And if you have other features you'd like to land, get 'em done! Master never closes --- This'll mark our first release where "master never closes". To recap: in previous releases, once we hit feature freeze we froze the development trunk, forcing all feature work out to branches. In practice, this meant months-long periods where new features couldn't be merged, and led to some stuff withering on the vine. That's not going to happen this time. Instead, when we release 1.5 alpha we'll make a 1.5 release branch right at that point. Work will continue on master -- features, bugfixes, whatever -- and the aplicable bugfixes will be cherry-picked out to the 1.5 release branch. The upshot is a bit more work for us committers -- we'll have to be sure to merge the aplicable commits over -- but no more "sorry you have to wait three months to merge this work." I'm very happy about this! [Committers: I'm happy to assist with this porting of bugfixes from master to the release branch.] See you on the other side, folks! 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@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: Django 1.5 release plans
On Tue, Sep 11, 2012 at 4:21 PM, Jacob Kaplan-Moss wrote: > [...] > > Timeline > > > Oct 1: Feature freeze, Django 1.5 alpha. > Nov 1: Django 1.5 beta. > Nov 26: Django 1.5 RC 1 > Dec 10: Django 1.5 RC 2 > Dec 17: Django 1.5 RC 3, if needed > Dec 24 (or earlier): Django 1.5 final > Looking forward to this release, exciting! However, targeting the release for Christmas Eve seems like a bad idea PR-wise. I suggest either launching after new year's eve or quite a few days before christmas to get better/broader PR. -- *Anders Steinlein* *Eliksir AS* http://e5r.no E-post: and...@e5r.no Mobil: +47 926 13 069 Twitter: @asteinlein -- 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@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: Django 1.5 release plans
On Tue, Sep 11, 2012 at 10:34 AM, Anders Steinlein wrote: > Looking forward to this release, exciting! However, targeting the release > for Christmas Eve seems like a bad idea PR-wise. I suggest either launching > after new year's eve or quite a few days before christmas to get > better/broader PR. Thanks for the suggestion. If this was a traditional product, I'd be holding off until after the new year, but the great thing about being an open source developer is that we don't have to worry about these things. PR's pretty far down the list of things I'm worried about. Free time, on the other hand, is right up there on the top, and the Thanksgiving - Christmas timeframe is traditionally when us volunteers have a ton of free time. So I'm targeting the release for the end of that timeframe. 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@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.
DJango and OrientDB
hi, I am planning to use orientDb with Django application (i am yet in design stage). I am not sure if i should just use simiple pyorient like library to access orientDB or should i write new db driver etc Basically my question is should i worry about not using django db functionality if i write custom classes to represent model classes. Thanks, Sajjad -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/SroraxbeM_gJ. To post to this group, send email to django-developers@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: DJango and OrientDB
Please ask questions about using Django on django-users. The topic of this list is the development of Django itself. Thanks, 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-developers@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: DJango and OrientDB
My question was should I write db driver etc but I do so I will need to be able to participate in framework Dev right? On Sep 11, 2012, at 5:57 PM, Karen Tracey wrote: > Please ask questions about using Django on django-users. The topic of this > list is the development of Django itself. > > Thanks, > 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-developers@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. -- 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@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: DJango and OrientDB
On Tue, Sep 11, 2012 at 10:22 PM, Sajjada Akhter wrote: > My question was should I write db driver etc but I do so I will need to be > able to participate in framework Dev right? > > You'll have a wider audience who may be able to answer this question: > I am not sure if i should just use simiple pyorient like library to access orientDB or should i write new db driver etc on django-users. This seems to be asking if you should use an existing library (not Django ORM interface) to access this OrientDB or if you should write a new Django DB backend (this providing Django ORM interface) to access this DB. The answer to that question in large part depends on whether it is worthwhile, for you, given your anticipated needs, to go to the effort of writing a new backend to get the Django ORM interface or if the existing library you mention might be easier and sufficient for your needs. If you do decide to go the route of writing a new DB backend, that does not have to be added as part of core Django. While Django has a set of core-included backends (PostgreSQL, MySQL, Oracle, sqlite) there are others that are not part of Django and externally maintained (mssql, IBM DB2, firebird). This list might be useful for asking specific technical questions when embarking on writing a new DB backend, but for the larger question you seem to be asking first I think django-users would offer more useful feedback on your question. There's a greater chance, for example, that someone on django-users already has experience with the library and DB you are looking at. 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-developers@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.
