Django update demanded

[Kevin Fenzi]

On Thu, 29 Mar 2012 08:59:55 -0600
Stephen John Smoogen <smooge at gmail.com> wrote:

> On 29 March 2012 01:12, Matthias Runge <mrunge at matthias-runge.de>
> wrote:
> > Dear list,
> >
> > currently, there's version 1.2 of the web development framework
> > django included in epel6. A week ago, django 1.4 was released.
> > Afaik, the django developers support only two minor releases at a
> > time, so it's questionable if django-1.2 will get any
> > (security-)updates from now on.
> >
> > My question is: Is there a operation precedure to do an upgrade to
> > e.g. django-1.3 (and accepting possible breakage of old software)?
> > Is this even required? If nobody complains about this update, I'd
> > prepare an update to version 1.3 probably next weekend.
> 
> the procedure is:
> 
> 1) announce here there is going to be a break.
> 2) see what apps are requiring it and letting those maintainers know
> they will have a break to deal with.
> 3) work out when those updates can be done.
> 4) see if there is any way to document the breakages and add that as
> a README. 5) then put a 1.3 in testing and call for testers.

Yep. Sounds right to me. 

Might leave it in testing extra long as well... 

kevin


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/epel-devel-list/attachments/20120330/e9789338/attachment.sig>