Re: Why Openstack: N/A for stemcell versions in v237 release notes?
Amit Kumar Gupta
Hi Tom,toggle quoted messageShow quoted text
Apologies for having had several releases with "N/A" under the OpenStack
stemcell. We had a very lengthy process of obtaining a working OpenStack
environment from our provider. While waiting for the environment, the
Release Integration team picked up a track of work on adding Diego to our
pipelines that we're still in the middle of, and we've also had several
high urgency security issues that have pre-empted other work in our
backlog. The Diego and security tracks are wrapping up, and rebooting our
OpenStack environment is one of our next two tracks of work in our roadmap [
0 <https://www.pivotaltracker.com/n/projects/1382120>]. At our current
team strength we are able to parallelize two tracks of work, so we will be
getting to this soon.
I'll use this as an opportunity for a shameless plug. If you're interested
in how Cloud Foundry is integrated, released, and deployed, I welcome you
to dojo [1 <https://www.cloudfoundry.org/community/contribute/dojos/>] with
Pivotal on the Release Integration team. This team is responsible for the
pipelines which fully certify and ship the Cloud Foundry release, and are
building the BOSH 2.0 manifests for Cloud Foundry for the community to use.
On Wed, Jun 8, 2016 at 6:05 AM, Tom Sherrod <tom.sherrod(a)gmail.com> wrote: