<HTML>
<HEAD>
<TITLE>Re: [Openstack] best practices for merging common into specific projects</TITLE>
</HEAD>
<BODY>
<FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>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?<BR>
<BR>
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?<BR>
<BR>
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.<BR>
<BR>
On 7/3/12 2:35 AM, "Thierry Carrez" <<a href="thierry@openstack.org">thierry@openstack.org</a>> wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Thierry Carrez wrote:<BR>
> Gabriel Hurley wrote:<BR>
>> 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...<BR>
><BR>
> This discussion should probably wait for markmc to come back, since he<BR>
> set up most of this framework in the first place. He would certainly<BR>
> produce a more compelling rationale than I can :)<BR>
<BR>
Actually <a href="http://wiki.openstack.org/CommonLibrary">http://wiki.openstack.org/CommonLibrary</a> explains it quite well.<BR>
In particular:<BR>
<BR>
"openstack-common also provides a process for incubating APIs which,<BR>
while they are shared between multiple OpenStack projects, have not yet<BR>
matured to meet the [library inclusion] criteria described above."<BR>
<BR>
"Incubation shouldn't be seen as a long term option for any API - it is<BR>
merely a stepping stone to inclusion into the openstack-common library<BR>
proper."<BR>
<BR>
--<BR>
Thierry Carrez (ttx)<BR>
Release Manager, OpenStack<BR>
<BR>
_______________________________________________<BR>
Mailing list: <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><BR>
Post to : <a href="openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><BR>
Unsubscribe : <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><BR>
More help : <a href="https://help.launchpad.net/ListHelp">https://help.launchpad.net/ListHelp</a><BR>
<BR>
</SPAN></FONT></BLOCKQUOTE>
</BODY>
</HTML>