Ubuntu

django 1.2 for lucid

Reported by Thomas Bechtold on 2010-01-10
48
This bug affects 8 people
Affects Status Importance Assigned to Milestone
python-django (Ubuntu)
Wishlist
Unassigned
Nominated for Lucid by Thomas Bechtold

Bug Description

Binary package hint: python-django

the first alpha version of django 1.2 is available.

The final relase should be at the begining of march 2010. So i think it would be great if for ubuntu 10.04 LTS (Lucid) is django 1.2 available.
You can find the roadmap for django 1.2 here: http://code.djangoproject.com/wiki/Version1.2Roadmap

Matt Austin (mattaustin) wrote :

I also think it's important for 10.04 LTS to include Django 1.2. As it is a LTS release, I will be running 10.04 on my webserver for at least two years - and, as I develop using Django, I feel it is important to have the latest stable version in the repositories when Lucid is released.

Django 1.2 beta 1 was released on Feb 6th, and is now at feature freeze. This is the second in a series of preview/development releases leading up to the eventual release of Django 1.2, currently scheduled to take place in March 2010.

Release notes: http://docs.djangoproject.com/en/dev/releases/1.2-beta-1/

Krzysztof Klimonda (kklimonda) wrote :

The question is if upstream is going to release 1.2 before Lucid gets released - 1.1 has been released 4 months after the planned date and there was no indication of that before RC release - I'm going to ask developers about the shape of 1.2 and if they are able to release it before Lucid Beta 1.

Chuck Short (zulcss) wrote :

This will need a FFE exception and there is nothing to sponsor here. To find out about FFE please see:

https://wiki.ubuntu.com/FreezeExceptionProcess

Steven Wagner (stevenwagner) wrote :

I agree as well that it is important to have django 1.2 in lucid. 1.2 will be the new standard when it is released. Outdated packages in a distro make using distros rather purposeless. This is the same old issue of coordination for releases in the open source community. It has to be judged on a case by case basis by human beings.

Low impact - The django package does not have system wide dependencies that would cause instability. Django is a highly issolated backage that only effects django web development. As well, the django package will continue to function the same way for the install.Gr

Benefit - Keeping lucid Ubuntu 10.04 compatible with the community at large, and not having lucid's django packages be obsolete upon release.

Steven Wagner (stevenwagner) wrote :

quote from - http://www.djangoproject.com/weblog/2010/feb/06/12-beta-1/
on February 6, 2010 "Also, note that this release constitutes the final feature freeze for Django 1.2. No further new feature development will take place before the final 1.2 release; only bugfix work will be accepted in trunk until 1.2 lands."

If Django-1.2-beta1 is already in a feature freeze, it should be packaged into lucid. Ubuntu regularly has put software labeled beta into its distro releases. The final release of Django1.2 is already scheduled to come out on the week of March 9 which is before the lucid has its beta1 freeze.
see: http://docs.djangoproject.com/en/dev//releases/1.2-beta-1/#the-django-1-2-roadmap

Steven Wagner (stevenwagner) wrote :

Krzysztof Klimonda: the roadmap link attached to this bug shares how the now have an improved process to avoid schedule slippage, as well as feature freeze dates this time.

Krzysztof Klimonda (kklimonda) wrote :

The problem is the phrase: "If necessary, additional beta or release-candidate packages will be issued prior to the final 1.2 release". There are currently over 300 bugs milestoned for 1.2 release and this number is making me nervous.
@Chuck: Was your comment about FFE a generic one or did you take a look at django and decided that getting 1.2 into Lucid isn't going to be a problem?
If it's possible we could wait until march 9 and see how close Django developers are to releasing 1.2 and make our decision then. Are there any other expections we would have to get by then? :)

Robert Collins (lifeless) wrote :

@Krzysztof we can't do an FFe until the thing to make an exception for is ready. We're already in freeze, so its just going to be assessed more critically the later that we come to assess it.

Steven Wagner (stevenwagner) wrote :

@Chuck: Django 1.2 has Cross Site Request Forgery protection turned on by default. For security reasons, it could qualify for FFE exception. http://docs.djangoproject.com/en/dev/ref/contrib/csrf/

@Robert: Firefox beta was included in hardy, and that had a much higher impact because so many people use it.

On Feb 20, 2010, at 5:17 PM, Krzysztof Klimonda wrote:
> The problem is the phrase: "If necessary, additional beta or release-
> candidate packages will be issued prior to the final 1.2 release".
> There are currently over 300 bugs milestoned for 1.2 release and
> this number is making me nervous.
> @Chuck: Was your comment about FFE a generic one or did you take a
> look at django and decided that getting 1.2 into Lucid isn't going
> to be a problem?
> If it's possible we could wait until march 9 and see how close
> Django developers are to releasing 1.2 and make our decision then.
> Are there any other expections we would have to get by then? :)

It's worth noting that this week most of the Django team, myself (I'm
Django's release manager, for those who don't know me) included, are
at PyCon and participating in development sprints focused entirely on
bugfix work for 1.2. In the past we've been able to easily clear out a
hundred tickets or more in a single sprint, so I don't feel too
nervous about what's currently open in our tracker. Also, not
everything currently listed on the 1.2 milestone will necessarily
land; we'll be triaging this week to determine what can and should be
fixed for 1.2.0, and what should be punted to a later bugfix release.

As for additional packages: if there are any, they'll be release
candidates, and we'll only issue multiple RCs if a previously-unknown
critical bug shows up between RC1 and the projected final release.
There will not be any further beta packages for Django 1.2.

--
James Bennett
<email address hidden>

Matt Austin (mattaustin) wrote :

An update for everyone that Django has announced a delay to the release of 1.2:
http://www.djangoproject.com/weblog/2010/mar/09/django-1_2-release-schedule/

"It's difficult to know exactly how much work is left before we do the final ticket cull, but our first-cut revised estimate is for an RC1 release around March 22, with a final release around March 29. This is, for those of you who were following along during the early parts of the 1.2 cycle, roughly consistent with extra time added to the release schedule for the 1.2 alpha and beta milestones."

Thomas Bechtold (toabctl) wrote :

New Infos from a django-core-developer (see http://www.djangoproject.com/weblog/2010/apr/01/django-1_2-release-schedule-update-3/ )

"... This means we are now targeting a release candidate around April 19, with a final release around April 26."

I think it's important to have django 1.2 in Lucid. There are a lot of new features and i think a lot of projects/people are using django.
For new features, see http://code.djangoproject.com/wiki/Version1.2Features and http://djangoadvent.com/ . Main features are:
- multi DB support
- improved csfr protection
- I18N/L10N improvements
- Testing framework improvements
- improved If-template-tag
- improved message framework

Thomas Bechtold (toabctl) wrote :

debian has django-1.2 in experimental: http://packages.debian.org/experimental/python-django

Steven Wagner (stevenwagner) wrote :

@Robert Collins: With a lucid release date of April 29th, and a django 1.2 release date of April 26th, this package needs to be pulled over from debian now or not at all.

Krzysztof Klimonda (kklimonda) wrote :

Well, at this point of time, based on my (brief) discussion with one of the ubuntu-server members I'd say that we won't get 1.2 into lucid. It's too late to get it uploaded and check all rdepends, the chance that it's not going to get released before May 26th is pretty big.
I'm going to leave the bug open until maverick archive opens and we can upload 1.2 there.

Changed in python-django (Ubuntu):
importance: Undecided → Wishlist
status: New → Confirmed
Daniel Holbach (dholbach) wrote :

I'm unsubscribing the sponsors team. I can't see anything that should be sponsored right now.

https://wiki.ubuntu.com/FreezeExceptionProcess is the process for a freeze exception.

James Westby (james-w) wrote :

Someone could request a backport if they wished to have 1.2 available on lucid.

Thanks,

James

Chris Johnston (cjohnston) wrote :

Marking wontfix as it clearly didn't make it into Lucid. If there is a desire, a backport can now be filed.

Changed in python-django (Ubuntu):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers