Comment 10 for bug 505440

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>