[Openstack-devel] Fwd: keystone REMOVED from testing

Tue May 29 07:16:20 UTC 2012

Hi all,
    related to this bug, it was solved a long long time ago (around
2012~rc3) but nobody closed it. I did it yesterday, after the removal. I
plan to upload a new keystone package this week, so let's hope no other
issues come around.

    And about the team, I agree with you Loic. Openstack is too big and
fast moving that keeping things working all the time is almost impossible
unless you are working 100% on it, besides, Debian has a problem with
timing (I remember having this conversation with Loic some time ago, so
just copy/paste it with some more up-to-date data)

"The major problem of Debian and OpenStack, is Debian itself. In a so fast
moving project like OpenStack, having an "EveryThing-Ready-and-Included"
release every two years is not viable for this scenario. In the case of
OpenStack, Squeeze is too old to handle it the way it is right now (Too
many things not directly related with OpenStack, like qemu-xen,
python-modules, etc.,   should be backported to make it functional, and
with just volunteer packagers, make it a not so viable option). In the
other hand, the next release, is planned to 1Q 2013 (Wheezy being frozen in
later June), so Essex release will be outdated and Folsom we be the stable
release by then, and with G release knocking on the door (Essex is supposed
to be a LTS release, supported by Canonical/Ubuntu until around April
2017so is not that bad). Solutions?  Forget about Squeeze, focus in Wheezy
+ Essex as an official release , and Folsom (or G release) as a back-ported
option. The other option (not viable in a short term), is change the way
Debian makes it releases, and try to have something more "componentized"
(like Progeny tried to do some years ago) or "rolling-releases", so
trending-topic these days.  Neither GNOME, OpenStack, LibreOffice, linux-kernel
(just to name some) has a similar release cycle or core necessities to run
in a system, so why try to release, prepare, stabilized everything at the
same time no matter what's the status the upstream project is? (Just int he
case of OpenStack, and supposing everything thing is going according the
schedule, with a 6 month release cycle vs. 2 years in Debian + frozen
period, when Wheezy is released, we are going to release an outdated
version -essex (but LTS thanks to Canonical)-  when Folsom is 4 months old!
and the new release coming in less than two months!) I agree this needs a
lot of more development, but i think it's something that Debian should have
to think about."

Re-reading it, the situation is not that bad actually. We were lucky enough
that the new Ubuntu LTS was released, and we can use the excuse of Essex
being supported until 2017. But the key point is the same: "Debian is huge
and slow, while OpenStack (and so many other projects) are really
fast-moving"

Ghe Rivero

On Tue, May 29, 2012 at 8:14 AM, Loic Dachary <loic at enovance.com> wrote:

>  Hi,
>
> This (removal of keystone from testing) is a definitive sign that our team
> is understaffed :-) At the moment Ghe Rivero and Mehdi Abaakouk are active.
> Unless I'm mistaken, noone else has currently time to work on the OpenStack
> package issues. To address this problem I propose that my company hires a
> Debian GNU/Linux packager to resolve this crisis. Please let me know if you
> have a better idea.
>
> Cheers
>
>
> -------- Original Message --------  Subject: [Openstack-devel] keystone
> REMOVED from testing  Date: Mon, 28 May 2012 16:39:14 +0000  From: Debian
> testing watch <noreply at release.debian.org> <noreply at release.debian.org>  To:
> keystone at packages.debian.org
>
> FYI: The status of the keystone source package
> in Debian's testing distribution has changed.
>
>   Previous version: 2012.1-2
>   Current version:  (not in testing)
>   Hint: <http://release.debian.org/britney/hints/nthykier> <http://release.debian.org/britney/hints/nthykier>
>     #20120528
>     #20120528
>
> The script that generates this mail tries to extract removal
> reasons from comments in the britney hint files. Those comments
> were not originally meant to be machine readable, so if the
> reason for removing your package seems to be nonsense, it is
> probably the reporting script that got confused. Please check the
> actual hints file before you complain about meaningless removals.
>
> --
> This email is automatically generated once a day.  As the installation of
> new packages into testing happens multiple times a day you will receive
> later changes on the next day.
> See http://release.debian.org/testing-watch/ for more information.
>
> _______________________________________________
> Openstack-devel mailing listOpenstack-devel at lists.alioth.debian.orghttp://lists.alioth.debian.org/mailman/listinfo/openstack-devel
>
>
> _______________________________________________
> Openstack-devel mailing list
> Openstack-devel at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/openstack-devel
>
>

-- 
Pinky: "Gee, Brain, what do you want to do tonight?"
The Brain: "The same thing we do every night, Pinky—try to take over the
world!"

 .''`.  Pienso, Luego Incordio
: :' :
`. `'
  `-    www.debian.org    www.openstack.com

GPG Key: 26F020F7
GPG fingerprint: 4986 39DA D152 050B 4699  9A71 66DB 5A36 26F0 20F7
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/openstack-devel/attachments/20120529/dc9ca025/attachment.html>