atom feed48 messages in net.launchpad.lists.openstackRe: [Openstack] best practices for me...
FromSent OnAttachments
Andrew BogottJul 2, 2012 12:16 pm 
Russell BryantJul 2, 2012 12:26 pm 
Joshua HarlowJul 2, 2012 2:41 pm 
Joshua HarlowJul 2, 2012 2:54 pm 
Gabriel HurleyJul 2, 2012 3:18 pm 
John PostlethwaitJul 2, 2012 4:42 pm 
Christopher B FerrisJul 2, 2012 5:41 pm 
Thierry CarrezJul 3, 2012 2:31 am 
Thierry CarrezJul 3, 2012 2:34 am 
Doug HellmannJul 3, 2012 5:37 am 
James E. BlairJul 3, 2012 6:55 am 
Joshua HarlowJul 3, 2012 10:46 am 
Dan PrinceJul 3, 2012 10:59 am 
Gabriel HurleyJul 3, 2012 11:59 am 
Andrew BogottJul 3, 2012 12:47 pm 
Joshua HarlowJul 3, 2012 2:09 pm 
James E. BlairJul 3, 2012 2:54 pm 
Eric WindischJul 3, 2012 3:47 pm 
Andrew BogottJul 3, 2012 3:54 pm 
Gabriel HurleyJul 3, 2012 4:53 pm 
Timothy DalyJul 3, 2012 5:27 pm 
Monty TaylorJul 3, 2012 6:17 pm 
Thierry CarrezJul 4, 2012 2:56 am 
Gabriel HurleyJul 4, 2012 3:17 pm 
Eric WindischJul 4, 2012 4:11 pm 
Christopher B FerrisJul 5, 2012 4:29 am 
Sean DagueJul 5, 2012 6:55 am 
Doug HellmannJul 5, 2012 7:16 am 
Joshua HarlowJul 5, 2012 10:21 am 
Mark McLoughlinJul 18, 2012 2:01 am 
Mark McLoughlinJul 18, 2012 2:13 am 
Mark McLoughlinJul 18, 2012 2:16 am 
Mark McLoughlinJul 18, 2012 2:23 am 
Thierry CarrezJul 18, 2012 4:00 pm 
Doug HellmannJul 23, 2012 8:50 am 
Thierry CarrezJul 23, 2012 8:59 am 
Doug HellmannJul 23, 2012 9:04 am 
Eric WindischAug 2, 2012 1:05 pm 
Christopher B FerrisAug 2, 2012 2:08 pm 
Vishvananda IshayaAug 2, 2012 3:47 pm 
Jay PipesAug 2, 2012 5:18 pm 
Zhongyue LuoAug 2, 2012 5:24 pm 
Eric WindischAug 2, 2012 5:51 pm 
Mark McLoughlinAug 2, 2012 10:26 pm 
Thierry CarrezAug 3, 2012 2:49 am 
Thierry CarrezAug 3, 2012 4:02 am 
Jay PipesAug 3, 2012 9:25 am 
Eric WindischAug 3, 2012 9:34 am 
Subject:Re: [Openstack] best practices for merging common into specific projects
From:Joshua Harlow (harl@yahoo-inc.com)
Date:Jul 3, 2012 10:46:19 am
List:net.launchpad.lists.openstack

I think that's a good little explanation as to why we have openstack-common, but
when did it become a good reason to copy code around via an inclusion mechanism?

Lots of code is in packages (outside of openstack, in pypi and elsewhere) that
is also in 'incubation' (in fact, what code isn't in perpetual incubation),
that's why u still have version numbers?

I just worry about inclusion of code that isn't versioned into other projects,
and I don't see the benefit of that when u can just have a package that has that
code as well.

On 7/3/12 2:35 AM, "Thierry Carrez" <thie@openstack.org> wrote:

Thierry Carrez wrote:

Gabriel Hurley wrote:

On a more fundamental level, did I miss some tremendous reason why we have this
"merge from common" pattern instead of making OpenStack Common a standard python
dependency just like anything else? Especially with the work Monty has recently
done on versioning and packaging the client libs from Jenkins, I can't see a
reason to keep following this "update common and merge to everything else"
pattern at all...

This discussion should probably wait for markmc to come back, since he set up most of this framework in the first place. He would certainly produce a more compelling rationale than I can :)

Actually http://wiki.openstack.org/CommonLibrary explains it quite well. In particular:

"openstack-common also provides a process for incubating APIs which, while they are shared between multiple OpenStack projects, have not yet matured to meet the [library inclusion] criteria described above."

"Incubation shouldn't be seen as a long term option for any API - it is merely a stepping stone to inclusion into the openstack-common library proper."