Re: [openstack-dev] [searchlight][release] Searchlight deliverable type

2018-04-23 Thread Sean McGinnis
On Mon, Apr 23, 2018 at 09:16:03AM -0500, Sean McGinnis wrote:
> Hello searchlighters,
> 
> The Rocky 1 milestone was last Thursday, and there has been no release request
> was submitted for the searchlight deliverables [1].
> 
> I remember some discussion at the last Denver PTG about searchlight and that 
> it
> is basically considered "code complete" at this point until any new
> requirements come up for it. Is this still (or ever) an accurate assessment of
> the current project state?
> 
> If so, I am wondering if this project's deliverables should be switched from
> being a cycle-based deliverable to being considered an independent 
> deliverable.
> This allows the project to release at any point as needed, and does not 
> require
> adherance to the milestone within cycle model that it is currently set up to
> follow.
> 
> I would like to hear from the team to get a better understanding of where this
> project is and how to best support its release needs.
> 

In a time honored tradition, I missed actually adding the link referred to
above.

[1] http://lists.openstack.org/pipermail/openstack-dev/2018-April/129617.html

__
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] [searchlight][release] Searchlight deliverable type

2018-04-23 Thread Sean McGinnis
Hello searchlighters,

The Rocky 1 milestone was last Thursday, and there has been no release request
was submitted for the searchlight deliverables [1].

I remember some discussion at the last Denver PTG about searchlight and that it
is basically considered "code complete" at this point until any new
requirements come up for it. Is this still (or ever) an accurate assessment of
the current project state?

If so, I am wondering if this project's deliverables should be switched from
being a cycle-based deliverable to being considered an independent deliverable.
This allows the project to release at any point as needed, and does not require
adherance to the milestone within cycle model that it is currently set up to
follow.

I would like to hear from the team to get a better understanding of where this
project is and how to best support its release needs.

Thanks,
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