[Openstack-devel] dropping essex from wheezy?

[matt]

The security problems in essex that have not been backported from recent
openstack releases are in at least one specific case fairly severe.

Also at this point deployment of essex in any environment would be
detrimental to the person deploying it.  At least adding a clear warning
that proceeding is a bad idea for new deployers would make sense to me.
Maybe a "Yes I know what I am doing" prompt.

-Matt


On Tue, Sep 24, 2013 at 10:02 AM, Julien Cristau <jcristau at debian.org>wrote:

> On Mon, Sep 23, 2013 at 10:29:34 -0300, gustavo panizzo <gfa> wrote:
>
> > hello folks
> >
> >     i would like to propose the elimination of essex from wheezy, our
> > current stable release.
> >
> You should have thought of that before getting it in a stable release.
> At this point it's just not reasonable IMO.
>
> > - it's security maintenance is a pain, i've tried to backport some fixes
> > but a year, or more, in openstack is a lot. many fixes are not easily
> > back ported.
> >
> I don't think this matters much.  You wouldn't base a public cloud on
> that version anyway, and most of the security fixes aren't really all
> that important in a private/internal environment.
>
> > if we chose the "make our own patch" way, is really hard to test it.
> > you can create a test for the patch. but real world testing is almost
> > impossible (does anybody run an essex install?)
> >
> I run one.  (Thinking of upgrading it, but that's going to take a while,
> especially without a proper upgrade path.)
>
> Cheers,
> Julien
>
> _______________________________________________
> Openstack-devel mailing list
> Openstack-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/openstack-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/openstack-devel/attachments/20130924/aeed6d19/attachment.html>