Re: [openstack-dev] Program Proposal: DevStack

2013-07-16 Thread Flavio Percoco
On 15/07/13 14:14 -0400, Russell Bryant wrote: On 07/15/2013 11:39 AM, Dean Troyer wrote: DevStack plays multiple roles in the development process for OpenStack. Does it really make sense to be its own program? There was mention of just making it a part of infra or QA. QA actually makes the

Re: [openstack-dev] Program Proposal: DevStack

2013-07-16 Thread John Griffith
On Tue, Jul 16, 2013 at 7:42 AM, Mark McLoughlin mar...@redhat.com wrote: On Mon, 2013-07-15 at 14:14 -0400, Russell Bryant wrote: On 07/15/2013 11:39 AM, Dean Troyer wrote: DevStack plays multiple roles in the development process for OpenStack. Does it really make sense to be its own

Re: [openstack-dev] Program Proposal: DevStack

2013-07-16 Thread Thierry Carrez
Mark McLoughlin wrote: On Mon, 2013-07-15 at 14:14 -0400, Russell Bryant wrote: On 07/15/2013 11:39 AM, Dean Troyer wrote: DevStack plays multiple roles in the development process for OpenStack. Does it really make sense to be its own program? There was mention of just making it a part of

Re: [openstack-dev] Program Proposal: DevStack

2013-07-16 Thread Joshua Harlow
Anvil seems to fit in said program. It's role is similar, helps build openstack as packages (rpms) for deployers/developers or for quick testing. Provides similar functionality as devstack http://anvil.readthedocs.org/ Both are actively supported and both are tools for developers and

[openstack-dev] Program Proposal: DevStack

2013-07-15 Thread Dean Troyer
DevStack plays multiple roles in the development process for OpenStack. Official Title: DevStack PTL: Dean Troyer dtro...@gmail.com Mission Statement: To provide an installation of OpenStack from git repository master, or specific branches, suitable for development and operational testing. It

Re: [openstack-dev] Program Proposal: DevStack

2013-07-15 Thread Russell Bryant
On 07/15/2013 11:39 AM, Dean Troyer wrote: DevStack plays multiple roles in the development process for OpenStack. Does it really make sense to be its own program? There was mention of just making it a part of infra or QA. QA actually makes the most sense to me, since devstack's primary use