e have said they "should
help further the OpenStack mission, by providing a cloud infrastructure
service, or directly building on an existing OpenStack infrastructure
service." [1]
I don't think there's any problem with writing down more detail
about what we mean by "shoul
go further.
Now, as you point out, the next step is to find out from the
contributors to placement what they want the ultimate home for the
service to be, and what steps need to be taken to reach that point.
Doug
__
https://review.openstack.org/#/c/593289/ should fix the similar
problem you found with CommentedSeq.
Doug
Excerpts from super user's message of 2018-08-18 11:15:20 +0900:
> The problem was fixed.
>
> Nguyen Hai
>
> On Fri, Aug 17, 2018 at 11:47 PM Doug Hellmann
> wrote
placement without installing the rest of the nova code
> and dependency tree. Artificially creating more "perceived" distance
> sounds really political to me, so let's be sure we're upfront about the
> reasoning for doing that if so :)
>
> --Dan
>
If we i
I was not able to reproduce the problem. Please test the fix in
https://review.openstack.org/#/c/593068/ to see if that helps.
Which version of Python are you using to run the tools? And on which OS?
Excerpts from Doug Hellmann's message of 2018-08-17 10:30:29 -0400:
> I will work on fix
aving to backport changes just to fix the linter
errors. We made code changes in master to address them and left
bandit uncapped there, for now.
Doug
__
OpenStack Development Mailing List (not for usage questi
I will work on fixing this today.
Has the designate team agreed to go ahead with their migration, or
are you still testing the scripts?
Doug
Excerpts from super user's message of 2018-08-17 15:37:03 +0900:
> Hi Doug,
>
> I'm Nguyen Hai. I proposed the python3-first patch
Excerpts from Tony Breeds's message of 2018-08-17 06:56:11 +1000:
> On Thu, Aug 16, 2018 at 10:45:32AM -0400, Doug Hellmann wrote:
>
> > Is there any reason we can't uncap pbr, at least within the CI jobs?
>
> It might work for the docs builds but jumping a major
rsion.
Is there any reason we can't uncap pbr, at least within the CI jobs?
Doug
__
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
castellan? Should it be running on
stable/queens?
If we need it, can someone familiar with the job look into the
failure and try to fix the problem?
Thanks,
Doug
https://review.openstack.org/#/c/588780/
__
OpenStack
Excerpts from Andreas Jaeger's message of 2018-08-15 09:28:51 +0200:
> On 08/15/2018 07:25 AM, Tony Breeds wrote:
> > On Tue, Aug 14, 2018 at 04:22:16PM -0400, Doug Hellmann wrote:
> >
> >> Now that https://review.openstack.org/#/c/591671/ has landed, we need
> >
Excerpts from Tony Breeds's message of 2018-08-15 15:25:29 +1000:
> On Tue, Aug 14, 2018 at 04:22:16PM -0400, Doug Hellmann wrote:
>
> > Now that https://review.openstack.org/#/c/591671/ has landed, we need
> > someone to propose the backports of the constraint updates to
Excerpts from Zane Bitter's message of 2018-08-14 16:26:09 -0500:
> On 14/08/18 15:45, Doug Hellmann wrote:
> > The python 3.6 unit test job has exposed an issue with mox3. It looks
> > like it might just be in the test suite, but I can't tell.
> >
> >
nd include whatever changes are needed.
https://review.openstack.org/#/c/589591/
Doug
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubs
Excerpts from Doug Hellmann's message of 2018-08-13 18:30:02 -0400:
> Excerpts from Matthew Thode's message of 2018-08-13 16:17:30 -0500:
> > On 18-08-13 20:28:23, Andreas Jaeger wrote:
> > > On 2018-08-13 19:16, Andreas Jaeger wrote:
> > > > On 2018-08-13 1
about the potential breadth of
impact to our own CI systems, which we can mitigate with the constraints
list. In this case we know we have a version of something we manage
that broke several other things we manage. We should be able to go
ahead with the release and k
nfiguration into each repo as part
of the python3 goal this cycle.
So, for now we need to update the constraints list on master. But we
also need to work quickly to update the constraints lists in the open
branches so that is done before we approve the goal-related changes in
those branches
Excerpts from Davanum Srinivas (dims)'s message of 2018-08-14 04:05:23 +0800:
> Jay, Doug,
>
> We need to blacklist 0.2.2 and 0.2.3 (looking at changelog in)
> https://github.com/dims/etcd3-gateway/releases
Done in https://review.openstack.org/591
Excerpts from Davanum Srinivas (dims)'s message of 2018-08-14 03:50:54 +0800:
> Thanks Jay. Pushed out a 0.2.4 with a revert to the offending PR
>
> On Tue, Aug 14, 2018 at 1:22 AM Jay Pipes wrote:
>
> > On 08/12/2018 04:11 PM, Doug Hellmann wrote:
> > > The
Excerpts from Jay Pipes's message of 2018-08-13 13:21:56 -0400:
> On 08/12/2018 04:11 PM, Doug Hellmann wrote:
> > The tooz tests on master and stable/rocky are failing with an error:
> >
> > UnicodeDecodeError: 'utf8' codec can't decode byte 0xc4 in
This is week 1 of the roll-out of the "Run under Python 3 by default"
goal (https://governance.openstack.org/tc/goals/stein/python3-first.html).
I intend to send a summary message like this roughly weekly to
report progress on the Zuul setting migrations, because that portion
of the goal needs to
Excerpts from Ghanshyam Mann's message of 2018-08-13 23:12:51 +0900:
>
>
>
> On Mon, 13 Aug 2018 23:01:33 +0900 Doug Hellmann
> wrote
> > Excerpts from Dmitry Tantsur's message of 2018-08-13 15:51:56 +0200:
> > > On 08/13/2018 03:46 PM
This is the weekly summary of work being done by the Technical
Committee members. The full list of active items is managed in the
wiki: https://wiki.openstack.org/wiki/Technical_Committee_Tracker
We also track TC objectives for the cycle using StoryBoard at:
https://storyboard.openstack.org/#!/pro
Excerpts from Dmitry Tantsur's message of 2018-08-13 15:51:56 +0200:
> On 08/13/2018 03:46 PM, Doug Hellmann wrote:
> > Excerpts from Dmitry Tantsur's message of 2018-08-13 15:35:23 +0200:
> >> Hi,
> >>
> >> The plugins are branchless and should st
Excerpts from Jim Rollenhagen's message of 2018-08-13 09:50:34 -0400:
> // jim
>
> On Mon, Aug 13, 2018 at 9:46 AM, Doug Hellmann
> wrote:
>
> > Excerpts from Dmitry Tantsur's message of 2018-08-13 15:35:23 +0200:
> > > Hi,
> > >
> > >
bers appear together on
releases.openstack.org on the relevant release page so that users
looking for the "rocky" version of a plugin can find it easily.
Doug
>
> Dmitry
>
> On 08/12/2018 10:41 AM, Ghanshyam Mann wrote:
> > Hi All,
> >
> > Rocky release i
The tooz tests on master and stable/rocky are failing with an error:
UnicodeDecodeError: 'utf8' codec can't decode byte 0xc4 in position 0:
invalid continuation byte
This is unrelated to the change, which is simply importing test job
settings or updating the .gitreview file. I need someon
Excerpts from Tony Breeds's message of 2018-08-10 07:44:42 +1000:
> On Thu, Aug 09, 2018 at 05:20:53PM -0400, Doug Hellmann wrote:
> > Excerpts from Tony Breeds's message of 2018-08-08 14:39:30 +1000:
> > > Hello all,
> > > With the PTL elections behind
that may not yet be perfect, but gives a starting point on which
> to accrete a reasonable solution.
>
> If you have opinions on the matter, please leave something on the
> review.
>
> Thanks.
>
Thanks for writing that up, Chris.
Doug
___
e a good thing.
> * TC candidates that can't travel to the PTG could be disadvantaged
> * The campaigning would all happen at the PTG and not on the mailing
> list disadvantaging community members not at the PTG.
>
> So thoughts?
>
> Yours Tony.
>
> [1] https://governanc
all would be the configuration management part.
Does that make the 4 things separate roles, then? Isn't the role
usually the unit of sharing between playbooks?
Doug
__
OpenStack Development Mailing List (not for usage que
s volunteered to serve as PTL for the Winstackers team.
The patch to confirm him is https://review.openstack.org/#/c/590386/
Doug
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: op
Excerpts from Lance Bragstad's message of 2018-08-09 12:55:52 -0500:
>
> On 08/09/2018 12:48 PM, Doug Hellmann wrote:
> > Excerpts from Matt Riedemann's message of 2018-08-09 12:18:14 -0500:
> >> On 8/9/2018 11:47 AM, Doug Hellmann wrote:
> >>> Excerpt
files need to be fixed so a new release candidate can be
prepared. The changes will need to be made on master and then backported
to the new stable/rocky branch.
Doug
http://logs.openstack.org/84/84135048cb372cbd11080fc27151949cee4e52d1/pre-release/release-openstack-python/095990b/ara-r
Excerpts from Matt Riedemann's message of 2018-08-09 12:18:14 -0500:
> On 8/9/2018 11:47 AM, Doug Hellmann wrote:
> > Excerpts from Jay Pipes's message of 2018-08-08 22:53:54 -0400:
> >> For evidence, see:
> >>
> >> http://logs.openstack.org/41/5900
[14403]:
>
> Is there any way we can get rid of these?
>
> Thanks,
> -jay
>
It looks like those are coming out of the policy library? Maybe file a
bug there. I added "oslo" to the subject
Excerpts from Andrey Kurilin's message of 2018-08-09 13:35:53 +0300:
> Hi Doug!
>
> I'm ready to port our job to openstack-zuul-jobs repo, but I expect that
> Community will not accept it.
>
> The result of rally unittests is different between environments with py
rg/election/
>
> Thank you to all involved in the PTL election process,
>
> Yours Tony.
>
> [1] The TC is currently evaluating options for these projects.
Thank you all for agreeing to take on this additional responsibility to
keep OpenStack humming along smoothly.
And tha
y37 env
It would be really useful if you could help set up a job definition in
openstack-zuul-jobs like we have for openstack-tox-py36 [1], so that other
projects can easily add the job, too. Do you have time to do that?
Doug
[1]
http://git.openstack.org/cgit/openstack-infra/openstack-zuul-jobs/tree/z
toring new developers is an important
responsibility, and your patient service in working with the Outreachy
program has set a good example.
Doug
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: opensta
Excerpts from Doug Hellmann's message of 2018-08-01 09:27:09 -0400:
> Moisés Guimarães (moguimar) did quite a bit of work on oslo.config
> during the Rocky cycle to add driver support. Based on that work,
> and a discussion we have had since then about general cleanup needed
>
Champions,
I have made quite a few changes to the tools for generating the zuul
migration patches today. If you have any patches you generated locally
for testing, please check out the latest version of the tool (when all
of the changes merge) and regenerate them.
Doug
er or later, also hit the gate.
The community is not prepared to support 3.7 today. That doesn't
mean we will never support it, just that it is not the most important
thing for us to be doing right now. We'll get there.
Doug
___
Excerpts from Thomas Goirand's message of 2018-08-07 16:57:59 +0200:
> On 08/02/2018 04:27 PM, Doug Hellmann wrote:
> >
> > The last I heard, a few years ago Ian moved away from Python to
> > JavaScript as part of his work at Mozilla. The support around
> > past
, so we can be prepared to start
generating patches after the final release for Rocky is done.
http://git.openstack.org/cgit/openstack/goal-tools/tree/README.rst#n22
Doug
__
OpenStack Development Mailing List (not for usage
This is the weekly summary of work being done by the Technical
Committee members. The full list of active items is managed in the
wiki: https://wiki.openstack.org/wiki/Technical_Committee_Tracker
We also track TC objectives for the cycle using StoryBoard at:
https://storyboard.openstack.org/#!/pro
Excerpts from Doug Hellmann's message of 2018-05-14 08:52:08 -0400:
> Excerpts from Doug Hellmann's message of 2018-03-25 16:04:11 -0400:
> > Excerpts from Doug Hellmann's message of 2018-03-22 16:16:06 -0400:
> > > Excerpts from Doug Hellmann'
project-config
before we start that, those patches will include the new settings,
for the branches where the jobs run.
Doug
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@l
patch.
Doug
https://review.openstack.org/#/c/588644/
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi
patch.
Doug
https://review.openstack.org/#/c/588645/
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin
Excerpts from Ben Nemec's message of 2018-08-03 11:58:29 -0500:
> Hi,
>
> Zane has been doing some good work in oslo.service recently and I would
> like to add him to the core team. I know he's got a lot on his plate
> already, but he has taken the time to propose and review patches in
> oslo.
n to
JavaScript as part of his work at Mozilla. The support around
paste.deploy has been sporadic since then, and was one of the reasons
we discussed a goal of dropping paste.ini as a configuration file.
Do we have a real sense of how many of the projects below, which
list Paste in requiremen
Excerpts from Thierry Carrez's message of 2018-08-02 10:58:53 +0200:
> Tony Breeds wrote:
> > [...]
> > There are 8 projects without candidates, so according to this
> > resolution[1], the TC will have to decide how the following
> > projects will proceed: Dragonflow, Freezer, Loci, Packaging_Rpm,
er, so if there
is one please let us know.
Doug
>
> Thanks,
> Omer Anson.
>
> On Thu, 2 Aug 2018 at 11:59, Thierry Carrez wrote:
>
> > Tony Breeds wrote:
> > > [...]
> > > There are 8 projects without candidates, so according to this
> > > resolu
Interop WG was reluctant to make any structural changes at the
time because they had just gone through a renaming process for the
working group. Changing "WG" to "SIG" feels much lighter weight, so
maybe we can move ahead with that now.
Doug
This is the weekly summary of work being done by the Technical
Committee members. The full list of active items is managed in the
wiki: https://wiki.openstack.org/wiki/Technical_Committee_Tracker
We also track TC objectives for the cycle using StoryBoard at:
https://storyboard.openstack.org/#!/pro
have
completed the Rocky release.
As the goal document describes, the champions for this goal will
propose the patches to move the zuul settings (we have some nice
tools to do this in a consistent way). I expect we will start with
that around the time of the PTG. Stand by for more details.
Doug
[1]
enid-connect driver to synapse.
>
This matches my expectations. We did talk about supporting a temporary
bridge to IRC, during the migration, but I don't think we need to run an
"open" home server to have that.
Doug
__
indicate your approval or concerns with +1/-1.
Doug
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin
>
> PS: I realize that OpenStack Community will never go away from Freenode and
> IRC, but I do not want to stay silent.
We are unlikely to select slack because the platform itself is
proprietary, even if there are OSS clients. That said, there have
been some discussions about platforms s
e that bad version never makes it back into the
constraints list.
We don't need to sync the exclusion setting into all of the projects
that depend on the client, so we won't need a new release of any of the
downstream consumers.
We coul
This is the weekly summary of work being done by the Technical
Committee members. The full list of active items is managed in the
wiki: https://wiki.openstack.org/wiki/Technical_Committee_Tracker
We also track TC objectives for the cycle using StoryBoard at:
https://storyboard.openstack.org/#!/pro
t the Adjutant team be included. We can also add Adjutant
to the list of projects on docs.openstack.org for Stein, after
updating your publishing job(s).
Doug
[1] https://review.openstack.org/553643
__
OpenStack Development Ma
branch. The unrelease changes
for those deliverables will not be available to Rocky users unless
they are backported to the stable branch.
If you manage one of these deliverables, please review the list and
consider proposing a release before the deadline.
Doug
[ Unreleased changes in openstack
Development Focus
-
Teams should be focused on implementing planned work. Work should be
wrapping up on non-client libraries to meet the lib deadline Thursday,
the 19th.
General Information
---
We are now getting close to the end of the cycle. The non-client libr
Excerpts from Sumit Naiksatam's message of 2018-07-10 13:24:25 -0700:
> Thanks Doug for noticing this. I am guessing this was a transient
> issue. How do we trigger this job again to confirm?
Someone from the infra team with access to the zuul interface can help
you with that.
>
This is the weekly summary of work being done by the Technical
Committee members. The full list of active items is managed in the
wiki: https://wiki.openstack.org/wiki/Technical_Committee_Tracker
We also track TC objectives for the cycle using StoryBoard at:
https://storyboard.openstack.org/#!/pro
he final release date for
non-client libraries.
Doug
__
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
Excerpts from zuul's message of 2018-07-10 06:38:24 +:
> Build failed.
>
> - release-openstack-python
> http://logs.openstack.org/5b/5bbcfd7b41d39339ff9b9f8654681406d2508205/release/release-openstack-python/269f8ce/
> : FAILURE in 6m 31s
> - announce-release announce-release : SKIPPED
> - pr
Excerpts from Ben Nemec's message of 2018-07-09 15:42:02 -0500:
>
> On 07/09/2018 11:16 AM, Eric Fried wrote:
> > Doug-
> >
> > How long til we can start relying on the new behavior in the gate? I
> > gots me some basepython to purge...
>
> I want
Excerpts from Eric Fried's message of 2018-07-09 11:16:11 -0500:
> Doug-
>
> How long til we can start relying on the new behavior in the gate? I
> gots me some basepython to purge...
>
> -efried
Great question. I have to defer to the infra team to answer, since
Heads-up, there is a new tox release out. 3.1 includes some behavior
changes in the way basepython behaves (thanks, Stephen Finucan!), as
well as other bug fixes.
If you start seeing odd job failures, check your tox version.
Doug
--- Begin forwarded message from toxdevorg ---
From: toxdevorg
Excerpts from Zane Bitter's message of 2018-07-09 11:04:28 -0400:
> On 05/07/18 16:46, Doug Hellmann wrote:
> > I have a governance patch up [1] to change the project-testing-interface
> > (PTI) for building documentation to restore the use of tox.
> >
> > We
definition restores the use of tox and specifies
a "docs" environment. I have started defining the relevant jobs [2]
and project templates [3], and I will be updating the python3-first
transition plan as well.
Let me know if you have any questions about any of that,
Doug
[1] https://review.ope
t; as one shouldn't be
> enabling that without ensuring a correct TLS config.
>
> Bonus points in that upstream wouldn't need any changes, and we won't need
> to change every project. :)
>
> // jim
Yes, this feels very much like something the deployment tools sho
ld welcome your input, we want
them to draw their own conclusions about the state of the project.
Doug
__
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
I want to compliment the Ironic team on writing such engaging and
comprehensive release notes. Nice work!
Doug
Excerpts from no-reply's message of 2018-07-05 10:24:19 +:
> We are gleeful to announce the release of:
>
> ironic 11.0.0: OpenStack Bare Metal Provisioning
>
Excerpts from Chris Dent's message of 2018-07-03 19:31:43 +0100:
> On Tue, 3 Jul 2018, Doug Hellmann wrote:
>
> > Chris and Thierry have been discussing a technical vision for OpenStack.
> >
> > * https://etherpad.openstack.org/p/tech-vision-2018
>
> Just so
This is the weekly summary of work being done by the Technical
Committee members. The full list of active items is managed in the
wiki: https://wiki.openstack.org/wiki/Technical_Committee_Tracker
We also track TC objectives for the cycle using StoryBoard at:
https://storyboard.openstack.org/#!/pro
port
different versions of python on different branches.
I plan to write up a governance change ASAP to have the PTI expect
to call "tox -e docs" to build the documentation and then define a
new job that works that way. It sounds like that change will also
help
leases tend to introduce bugs.
Have you tried the 'threading' executor?
Doug
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
h
- declare their minimum version of tempest in requirements.txt
>
> Why isn't it sufficient for us?
It is. We just haven't been doing it; in part I think because most
developers interact with the plugins via the CI system and don't real
Excerpts from Tony Breeds's message of 2018-06-27 12:42:47 +1000:
> On Tue, Jun 26, 2018 at 09:03:40AM -0400, Doug Hellmann wrote:
> > Requirements team,
> >
> > At some point in the next few months we're going to want to raise
> > the constraint on openstac
Excerpts from Doug Hellmann's message of 2018-06-20 11:34:10 -0400:
> I want to thank Nguyễn Trí Hải, Ma Lei, and Huang Zhiping for
> agreeing to be a part of the goal champion team for the python3
> goal for Stein.
>
> The next step for us is to build some tools to make th
Excerpts from Doug Hellmann's message of 2018-06-26 11:19:05 -0400:
> 29 out of 40 repos that have "tempest" in the name have not been
> tagged via the releases repo. Not all of those are plugins. Here's
> a list:
>
> $ for repo in $(grep openstack/ reference/p
Excerpts from Matthew Treinish's message of 2018-06-26 10:37:54 -0400:
> On Tue, Jun 26, 2018 at 10:12:30AM -0400, Doug Hellmann wrote:
> > Excerpts from Matthew Treinish's message of 2018-06-26 09:52:09 -0400:
> > > On Tue, Jun 26, 2018 at 08:53:21AM -0400, Doug Hell
Excerpts from Matthew Treinish's message of 2018-06-26 09:52:09 -0400:
> On Tue, Jun 26, 2018 at 08:53:21AM -0400, Doug Hellmann wrote:
> > Excerpts from Andrea Frittoli's message of 2018-06-26 13:35:11 +0100:
> > > On Tue, 26 Jun 2018, 1:08 pm Thierry Carrez,
> &
7;ll have to settle for
> not treating warnings as errors to unblock our documentation gate [0].
>
> [0] https://review.openstack.org/#/c/577974/
How are docstrings from a third-party library making their way into the
keystone docs and breaking the build?
Doug
>
> On 06/25/2018 07:
o do as part of the python3-first
goal, then we can take advantage of those patches to trigger doc
rebuilds in all of the projects.
Doug
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: ope
s statement seriously
when the current source of tension is that the Tempest API itself
is breaking for its plugins.
Maybe rather than talking about how to release compatible things
together, we should go back and talk about why Tempest's API is changing
in a way that can't be made ba
Excerpts from Jeremy Stanley's message of 2018-06-25 16:01:11 +:
> On 2018-06-25 11:26:29 -0400 (-0400), Doug Hellmann wrote:
> > Excerpts from Thierry Carrez's message of 2018-06-25 17:15:44 +0200:
> > > Doug Hellmann wrote:
> > > > Are we plannin
Excerpts from Matthew Thode's message of 2018-06-25 10:19:50 -0500:
> On 18-06-25 10:58:26, Doug Hellmann wrote:
> > Excerpts from Matthew Thode's message of 2018-06-25 09:38:28 -0500:
> > > On 18-06-25 08:59:23, Doug Hellmann wrote:
> > > > Excerpts from
Excerpts from Thierry Carrez's message of 2018-06-25 17:15:44 +0200:
> Doug Hellmann wrote:
> > Are we planning to have space for goal teams to answer
> > implementation questions?
>
> At previous PTGs the "goal rooms" ended up not being used (or very very
>
,
Doug
[1] https://review.openstack.org/#/c/575933/6
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin
Excerpts from Matthew Thode's message of 2018-06-25 09:38:28 -0500:
> On 18-06-25 08:59:23, Doug Hellmann wrote:
> > Excerpts from Matthew Thode's message of 2018-06-24 02:42:23 -0500:
> > > The short of it is that we are currently using eventlet 0.20.0. The bot
>
This is the weekly summary of work being done by the Technical
Committee members. The full list of active items is managed in the
wiki: https://wiki.openstack.org/wiki/Technical_Committee_Tracker
We also track TC objectives for the cycle using StoryBoard at:
https://storyboard.openstack.org/#!/pro
Are we planning to have space for goal teams to answer
implementation questions?
Doug
Excerpts from Kendall Nelson's message of 2018-06-20 11:24:38 -0700:
> Hello Everyone!
>
> Wanted to give you some updates on PTG4 planning. We have finalized the
> list of SIGs/ Groups/W
By "bugging" do you mean we should file bugs, or something else?
Which version of eventlet is actually being used in the various
distros?
Doug
__
OpenStack Development Mailing List (not for usage questions)
Unsu
Excerpts from zuul's message of 2018-06-25 12:14:34 +:
> Build failed.
>
> - xstatic-check-version
> http://logs.openstack.org/59/592a9d4c90f37cd33c6f861120f41ac8a67d909b/release/xstatic-check-version/a501dba/
> : FAILURE in 1m 31s
> - release-openstack-python release-openstack-python : SKIP
if
they do happen. But it's generally better for us to be releasing
libraries and tools as often as possible, so that any breaking
changes come as part of a small set and so new features are available
shortly after they are implemented.
Doug
201 - 300 of 3780 matches
Mail list logo
