On 03/15/2013 11:59 AM, Vincent Untz wrote:
Le vendredi 15 mars 2013, à 11:12 +0100, Sascha Peilicke a écrit :
On 03/15/2013 11:02 AM, Christian Berendt wrote:
Hello Sasche.
Shouldn't we first make all packages usable? At the moment there are at least issues in openstack-quantum and I think openstack-ceilometer, openstack-cinder and openstack-heat will also have issues. I have not tested them yet.
Right, the posting may have been a bit premature, we're ATM (internally) discussing various options to have a more stable Grizzly without breaking the development model of Cloud:OpenStack:Master much. It seems like we will settle with updating packages there less frequently (i.e. only weekly) and set fixed revisions for all linked packages (i.e. python dependencies and co). I'll keep the list posted.
Yeah, I think what we care about is making sure that we have Grizzly packages that don't break every day. That was the case recently because the trackupstream jenkins job was configured to run daily; it got fixed to run weekly now (thanks Daniel!). So it should help.
It seems people prefer to stay with C:O:M for now, so that's definitely an option on the table. We might also look at other things we can do to help stabilize C:O:M in that case (Dirk was talking about freezing the python packages, instead of blindly following what's in d:l:p, iirc)
While following devel:languages:python (d:l:p) was ok as long as Grizzly development was open, we now have set a fixed revision on all python package links to d:l:p. This complements some fixed revisions we already had previously (i.e. Django-1.4 and jsonschema-0.7). Of course we can still bump particular packages when there is demand. -- With kind regards, Sascha Peilicke SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nuernberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org