openstack
/
loci
Code Issues Proposed changes

Remove warning about stability 

LOCI is running in production and is pretty low entropy, i think its
safe to all it stable ;)

Change-Id: Ib4e5c74058748df39067a7aecdd5ade2d89f40e6
This commit is contained in:
Sam Yaple 2018-03-09 09:29:25 -05:00
parent 483a24fefa
commit 52b95fc20c
No known key found for this signature in database
GPG Key ID: 9329D8A45034DAB9
1 changed files with 4 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
README.md
View File

@ -122,18 +122,8 @@ RUN set -x \
### A Note on the Stability of LOCI
LOCI is still a relatively young project. While some of us have been using it
for going on a year, we have made breaking changes a few times while we flesh
out the best way to achieve goals. We are targeting a 1.0.0 release for
OpenStack Queens and will be following upstream practices as far as tagging and
branching.
LOCI is considered stable. There are production installs of OpenStack using
LOCI built images at this time.
We will be adding in a stable/ocata and stable/pike branch (possibly an
eol-newton and eol-mitaka tag as well) over the next few months so we can build
images for these versions of OpenStack as well. While the master branch of LOCI
is currently capable of building all of these versions right now, we will be
maintaining stable branches going forward so as not to rely on compatibility
for all versions of OpenStack on one branch.
We highly encourage people to use this, and some have even adopted it into
build pipelines internally already.
The project is very low-entopy with very little changing, but this is expected.
The highest traffic section of LOCI is the gates.