A prompt 1.2.3 release

[Luke Plant]

Hi all,

It looks like we'll be needing a fairly prompt 1.2.3 release. So far
we've got:

One major/critical bug (depending on how many people are using the
deprecated CsrfResponseMiddleware):

http://code.djangoproject.com/ticket/14235

One significant regression:

http://code.djangoproject.com/ticket/14242

Packaging error(s):

http://code.djangoproject.com/ticket/14245

Many core devs are at Djangocon and are just starting sprints, I'm not
sure whether that will help or hinder.

Luke

--
A common mistake that people make when trying to design something
completely foolproof is to underestimate the ingenuity of complete
fools. -- Douglas Adams

Luke Plant || http://lukeplant.me.uk/

[Ramiro Morales]

On Thu, Sep 9, 2010 at 8:59 PM, Luke Plant <L.Pla...@cantab.net> wrote:
> Hi all,
>
> It looks like we'll be needing a fairly prompt 1.2.3 release.  So far
> we've got:
>
> One major/critical bug (depending on how many people are using the
> deprecated CsrfResponseMiddleware):
>
> http://code.djangoproject.com/ticket/14235
>
> One significant regression:
>
> http://code.djangoproject.com/ticket/14242
>
> Packaging error(s):
>
> http://code.djangoproject.com/ticket/14245

Add to that ticket #14247 -- A test suite error

http://code.djangoproject.com/ticket/14247

Unfortunately we didn't catch this failure in four weeks, the fact
that the buildbot
isn't running tests for the 1.2.X branch doeesn't help either.

--
Ramiro Morales  |  http://rmorales.net

[Paul McMillan]

> Unfortunately we didn't catch this failure in four weeks, the fact
> that the buildbot
> isn't running tests for the 1.2.X branch doeesn't help either.

The buildbot actually is running the 1.2.x tests, it is just
unfortunately named (and apparently re-naming it is a bit of a pain so
it hasn't happened yet). Look at the actual logs of any given build to
see what's actually checked out.

-Paul

[Luke Plant]

Which buildbot? http://buildbot.djangoproject.com/waterfall doesn't
seem to be doing 1.2.X - from the logs for the ones marked 1.1.X:

/usr/bin/svn checkout --revision 13706 --non-interactive --no-auth-cache
http://code.djangoproject.com/svn/django/branches/releases/1.1.X build

I can't find one that is checking out branches/releases/1.2.X

There was a hudson server running IIRC, but
http://hudson.djangoproject.com/ is not responding to me.

Luke

--
There was a young man from Peru
Whose limericks stopped at line two.

Luke Plant || http://lukeplant.me.uk/

[Paul McMillan]

> Which buildbot?  http://buildbot.djangoproject.com/waterfall doesn't
> seem to be doing 1.2.X - from the logs for the ones marked 1.1.X:

My mistake. It looks like it was partially converted to 1.2.x, but not
completely - the tests run when changes are made to 1.2.x, but as you
pointed out, it's still checking out the 1.1.x branch.

[Eric Holscher]

There was a hudson server running IIRC, but
http://hudson.djangoproject.com/ is not responding to me.

I took the hudson instance down because nobody was using it and it was costing me a decent amount of money to run per month. I still have the images around on Rackspace Cloud if the DSF or anyone actually wants to pay to have good CI.

Just as a data point, I took it down about a month ago, and people only just noticed during the sprints. I don't know how to fix that particular problem.

Cheers,
Eric
 

[Stephen Wolff]

Hi Eric,

Does this mean that the account we set up on our server is no longer necessary?

Stephen

--
You received this message because you are subscribed to the Google Groups "Django developers" group.
To post to this group, send email to django-d...@googlegroups.com.
To unsubscribe from this group, send email to django-develop...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.