<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><br>
</p>
<br>
<div class="moz-cite-prefix">On 01/27/2018 01:16 PM, Colleen Murphy
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAJkgcEnvDTNW4trA-+HCzCCCYLOuxNTxW5EQgTLbOc5MHGcO9A@mail.gmail.com">
<pre wrap=""># Keystone Team Update - Week of 22 January 2018
## News
### Feature freeze
This week was feature freeze and client freeze. While we approved
everything we cared about for this release on time, some CI issues
(some unexpected and some predictable) delayed these features being
merged. The release team has extended the freeze deadline to Monday,
which should (hopefully) give us enough time for the last few changes
to land before we release RC1.
### RC bugs
We've started compiling a list of potential release-critical bugs[1].
Please continue to report bugs as you find them in the RC, and also
please focus your attention on fixing these bugs and reviewing
bugfixes.</pre>
</blockquote>
Looks like everything that is a possible RC bug is targeted
accordingly. Here is a LP link in case that's easier for some people
to track [0].<br>
<br>
[0] <a class="moz-txt-link-freetext" href="https://goo.gl/A5Wz4Z">https://goo.gl/A5Wz4Z</a><span style="color: rgb(68, 68, 68);
font-size: 13px; font-style: normal; font-variant-ligatures:
normal; font-variant-caps: normal; font-weight: 400;
letter-spacing: normal; text-align: start; text-indent: 0px;
text-transform: none; white-space: normal; word-spacing: 0px;
-webkit-text-stroke-width: 0px; text-decoration-style: initial;
text-decoration-color: initial; display: inline ! important;
float: none;"></span>
<blockquote type="cite"
cite="mid:CAJkgcEnvDTNW4trA-+HCzCCCYLOuxNTxW5EQgTLbOc5MHGcO9A@mail.gmail.com">
<pre wrap="">
[1] <a class="moz-txt-link-freetext" href="https://etherpad.openstack.org/p/keystone-queens-bug-list">https://etherpad.openstack.org/p/keystone-queens-bug-list</a>
### API Discovery
We had some interesting discussions this week about experimental APIs
and API discovery[2][3]. This was partly in the context of our new
"unified limits" API, which is step 1 in providing a cross-project
service where quotas for projects could be set and retrieved by other
OpenStack services. We're marking this API as "experimental" for the
time being while we shake out some of the cross-project usage patterns
we'll need to support, but this poses a discoverabiltiy problem. We
already expose a "home document" which lists all of our API routes and
their statuses, e.g. whether they're tagged as "experimental". While
this seems like a really useful feature for API consumers as well as a
great way to expose experimental features without committing to
stability, it seems like the JSON-home standard never quite made it
off the ground, so it's not a standard we can rely on API consumers
supporting. However, we could certainly build off of what we already
have to enhance our API discoverability
[2] <a class="moz-txt-link-freetext" href="http://eavesdrop.openstack.org/irclogs/%23openstack-keystone/%23openstack-keystone.2018-01-24.log.html#t2018-01-24T22:27:50">http://eavesdrop.openstack.org/irclogs/%23openstack-keystone/%23openstack-keystone.2018-01-24.log.html#t2018-01-24T22:27:50</a>
[3] <a class="moz-txt-link-freetext" href="http://eavesdrop.openstack.org/irclogs/%23openstack-keystone/%23openstack-keystone.2018-01-25.log.html#t2018-01-25T14:43:46">http://eavesdrop.openstack.org/irclogs/%23openstack-keystone/%23openstack-keystone.2018-01-25.log.html#t2018-01-25T14:43:46</a>
[4] <a class="moz-txt-link-freetext" href="https://mnot.github.io/I-D/json-home/">https://mnot.github.io/I-D/json-home/</a>
### GSoC Projects
OpenStack is applying to participate in the Google Summer of Code
project[5]. We've started compiling a list of potential projects that
a GSoC intern could work on[6]. Please help us add to the list! And if
you're interested in being a mentor, please step up! We'll likely
discuss this more at the next keystone meeting.
[5] <a class="moz-txt-link-freetext" href="http://eavesdrop.openstack.org/irclogs/%23openstack-keystone/%23openstack-keystone.2018-01-25.log.html#t2018-01-25T14:38:28">http://eavesdrop.openstack.org/irclogs/%23openstack-keystone/%23openstack-keystone.2018-01-25.log.html#t2018-01-25T14:38:28</a>
[6] <a class="moz-txt-link-freetext" href="https://etherpad.openstack.org/p/keystone-internship-ideas">https://etherpad.openstack.org/p/keystone-internship-ideas</a>
## Recently Merged Changes
Search query: <a class="moz-txt-link-freetext" href="https://goo.gl/hdD9Kw">https://goo.gl/hdD9Kw</a>
We merged 49 changes this week, though we approved quite a few that
are still making their way through the gate, including changes that
are part of our main feature objectives.
## Changes that need Attention
Search query: <a class="moz-txt-link-freetext" href="https://goo.gl/h9knRA">https://goo.gl/h9knRA</a>
There are 36 changes that are passing CI, not in merge conflict, have
no negative reviews and aren't proposed by bots. Expect to see a lot
more as we bugstomp over the next two weeks.
## Milestone Outlook
<a class="moz-txt-link-freetext" href="https://releases.openstack.org/queens/schedule.html">https://releases.openstack.org/queens/schedule.html</a>
This week marked feature freeze and client freeze, but due to a number
of CI problems the release team has extended the feature freeze till
Monday and the client freeze until Tuesday[7]. This just means the
approved changes that we still have moving through CI should hopefully
have time to finish and be merged.
[7] <a class="moz-txt-link-freetext" href="http://lists.openstack.org/pipermail/openstack-dev/2018-January/126621.html">http://lists.openstack.org/pipermail/openstack-dev/2018-January/126621.html</a>
## Shout-outs
Thanks to the whole team for working so hard this week!
## Help with this newsletter
Help contribute to this newsletter by editing the etherpad:
<a class="moz-txt-link-freetext" href="https://etherpad.openstack.org/p/keystone-team-newsletter">https://etherpad.openstack.org/p/keystone-team-newsletter</a>
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>