Re: [openstack-dev] [craton] branch clean up and other stuff

[Jim Baker]

Sean, sounds good.

Today, among other things, we will be discussing the branch cleanup, which
should be straightforward. We look forward to discussing more about OneOps,
and I will briefly mention our thoughts to date on how this could work.

https://etherpad.openstack.org/p/craton-meetings for the full agenda



On Mon, Jul 18, 2016 at 8:29 AM, sean roberts 
wrote:

> I'm going to have to miss this mornings meeting again. Here out my
> outstanding issues
> - project patch https://review.openstack.org/#/c/332470/9, is pending a
> request to clean up the branches in the craton repo. Once the repo is
> moved, branch cleanup is expensive time wise. Branches are typically minor
> and major releases only.
> - allocating devs to the project. I'm getting spun up around a few teams.
> After the watcher, nova mid cycle this week. I will have a better idea who
> is available.
> - forking OneOps CMS repos as code base start. We are definitely
> interested internally in doing this. I suggest I get my devs to propose how
> the fork would look and what the implications are. Then the craton team as
> whole can discuss the merits and modifications to the approach.
>
>
>
> --
> ~sean
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [craton] branch clean up and other stuff

[sean roberts]

I'm going to have to miss this mornings meeting again. Here out my
outstanding issues
- project patch https://review.openstack.org/#/c/332470/9, is pending a
request to clean up the branches in the craton repo. Once the repo is
moved, branch cleanup is expensive time wise. Branches are typically minor
and major releases only.
- allocating devs to the project. I'm getting spun up around a few teams.
After the watcher, nova mid cycle this week. I will have a better idea who
is available.
- forking OneOps CMS repos as code base start. We are definitely interested
internally in doing this. I suggest I get my devs to propose how the fork
would look and what the implications are. Then the craton team as whole can
discuss the merits and modifications to the approach.



-- 
~sean
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev