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
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
For backports see: https://bugs.launchpad.net/lucid-
backports/+bug/604711
--
django 1.2 for lucid
https://bugs.launchpad.net/bugs/505440
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Someone could request a backport if they wished to have 1.2 available on
lucid.
Thanks,
James
--
django 1.2 for lucid
https://bugs.launchpad.net/bugs/505440
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
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.
--
django 1.2 for lucid
https://bugs.launchpad.net/bugs/505440
You received this bug notification because you are a
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
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.
debian has django-1.2 in experimental:
http://packages.debian.org/experimental/python-django
--
django 1.2 for lucid
https://bugs.launchpad.net/bugs/505440
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
@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.
--
django 1.2 for lucid
https://bugs.launchpad.net/bugs/505440
You received this bug notification because you are a member
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
@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
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.
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
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
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.
--
django 1.2 for lucid
https://bugs.launchpad.net/bugs/505440
You received this bug notification because you are a member
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
@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.
--
django 1.2 for lucid
https://bugs.launchpad.net/bugs/505440
You received this bug notification
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
--
django 1.2 for lucid
https://bugs.launchpad.net/bugs/505440
You received this bug notification because you are a member of Ubuntu
Bugs, which
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.
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
19 matches
Mail list logo
