This is a minor spelling correction, to align the projects list
entry with the reality in our infrastructure.
Change-Id: Ic844e970308e0dd94e5a6d970578306233f646e5
The project's stance on the Four Opens is currently in the wiki, which
isn't a great place for such an important piece of information. We
should make it a bit more official.
Change-Id: I96ccb0ef823aca95b1fd0e7c2e1be3207ad52d00
It has become clear that it's time for the TC to make a clear statement
about our intent on the point of Images and Kernels.
As an Open Source project, we have gone out of our way to enable
productization and differentiation by our vendors. Our 3rd Party CI
system is massive and Open- and our pluggability is almost cripplingly
comprehensive.
To give up on interoperable image uploads simply because a vendor would
like to do one thing that a little bit different isn't just wrong, it would
be giving up the ENTIRE effort.
We take a stand on very few things. We should take a stand on this.
Change-Id: I41247052240eaec19a9002cbefc52297d0d14566
Blueprint: use-cinder-without-nova
This adds the new cinder project python-brick-cinderclient-ext as
a subproject of Cinder
Related patch: Ifbf1ee3883e81713f665daf8ed8e6ca587206b81
Change-Id: I0c5d36bb1be9d435e15a5aac024bd969258cbdbb
we have aodh service for alarming. we now have python-aodhclient
rather than overloading ceilometerclient
Change-Id: I21a6d2d038d9aabd0a1c2e777b9f9223b5b56d38
Depends-On: Change-Id: I11cc63a3fb987c457595220d91315fdadcf41a12
Currently freezer uses an indipendent release model.
This is not suitable anymore as are aligning to
the other Openstack projects and having branches managed
by the stable maintenance team.
Change-Id: I793e297324ed6d8a3bcea8413c651b28807f635b
Now the freezer mission is more coincise and clear,
according to feedback and conversation with TC.
Change-Id: I36c3f61edd1413cb6c80f4b8b24701d4a06a3c2d
The Astara Neutron repo contains the drivers and plugins necessary to
load into Neutron to interface with the Astara RPC API. This repo is
being placed under Astara after considering the list conversation
regarding the Neutron Stadium [1]. Since our team will be handling
responsibility for release activities it made since to place it here.
[1] http://lists.openstack.org/pipermail/openstack-dev/2015-December/080865.html
Change-Id: Ie4a99316e60ca382f8d6323720f92ffb6642b66c
With the spin-off of the Stable branch maintenance subteam into
its own independent team, it makes sense to revisit the mission
of the Release Management team.
The old "Release Cycle Management" team used to regroup the
Release team, the Stable branch team and the Vulnerability
Management team. Now it's only the Release team left, so we
should also rename it to the name that everyone is calling us
anyway ("Release Management").
Also update the IRC channel and the wiki landing page.
Change-Id: I71b77d350dea2d2e697e6c59792d38a0274bda28
The ops tags team repo was migrated to the openstack
namespace with the death of stackforge. Update the
pointer.
Change-Id: I12b3de6c93178b895e8d594ca37a86f1e342d829
Trove's Horizon content is moving from integrated in Horizon to a
standalone Horizon plugin that will be managed by the Trove team.
Depends-On: I158eac980f767a4b8cd43294e8cc215fbb1586f3
Change-Id: Ief3829b45987dfb4078c78428f5f699912542868
Horizon does not maintain a database and configuration options
follow the standard deprecation process. New configuration options
that are required have sane defaults. The release notes contain
any unique items that are outside the standard upgrade process.
Change-Id: I821e51be9cc29084e50ca982bc636b552814ef6e
While horizon does not have an API, the project does follow the
standard deprecation process for features and configuration options.
Change-Id: Icb778ffc7a95eacf91a21a56a87dee3141d2e09d
