hi all,
 
I'd like to offer up something here.   We are in the process of spinning up a 
local instance of suse's open build system.
 
I had brought up in the past about using the current public service as an 
option.   I know now that the public obs isn't really an option due to changes 
we are currently making to add additonal distros not getting into the public 
service fast enough.
 However, I would like to throw it out there for discussion.  If I were to 
provide our instance as an option for building packages for all distro's as a 
way to coordinate all the package builds w/o recreating the wheel....  Does the 
rest of the community see this as a viable option which they would consider 
using?  We will be using our instance for cross distro builds of the LIS 
components for hyperv, and are doing work to add the support for additional 
distro's we need to test on.

 p






On Thu, Aug 25, 2011 at 11:24:06PM +0800, Thomas Goirand wrote:
> On 08/25/2011 06:47 PM, Soren Hansen wrote:
> > ..and not every (in fact, hardly any at all) backport involves
> > cherry-picking anything.
> 
> But *maintaining* it does, while an issue is fixed in trunk. I've just
> read that this has been an issue in Cactus (eg: bugs fixed in Diablo,
> but not fixed in Cactus).
> 
> Thomas
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
> 

_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to     : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

Reply via email to