Excerpts from Akihiro Motoki's message of 2018-05-12 00:14:33 +0900:
> Hi zigo and horizon plugin maintainers,
>
> Horizon itself already supports Django 2.0 and horizon unit test covers
> Django 2.0 with Python 3.5.
>
> A question to all is whether we change the upper bound of Django from <2.0
Excerpts from Zane Bitter's message of 2018-05-10 16:38:37 -0400:
> On 17/04/18 05:24, Thierry Carrez wrote:
> > Hi everyone,
> >
> > As you know the Technical Committee (the governance body representing
> > contributors producing OpenStack software) meets with other OpenStack
> > governance
Excerpts from Ilya Etingof's message of 2018-05-10 15:48:34 +0200:
> On 05/10/2018 03:01 PM, Julia Kreger wrote:
> > On Mon, May 7, 2018 at 4:34 PM, Doug Hellmann <d...@doughellmann.com> wrote:
> >
> >> As a consumer of team updates from outside of the team
Excerpts from Julia Kreger's message of 2018-05-10 09:01:42 -0400:
> On Mon, May 7, 2018 at 4:34 PM, Doug Hellmann <d...@doughellmann.com> wrote:
>
> > As a consumer of team updates from outside of the team, I do find
> > them valuable.
>
> Ditto, if I have tim
Excerpts from Doug Hellmann's message of 2018-05-09 16:06:01 -0400:
>
> The last time we had a joint leadership meeting, several TC members
> expressed the desire to have more information about what was going
> to be covered before the meeting. The agenda for the next meeting
> (to be held in
The last time we had a joint leadership meeting, several TC members
expressed the desire to have more information about what was going
to be covered before the meeting. The agenda for the next meeting
(to be held in Vancouver), is in the wiki at
I have created the etherpad for the TC Retrospective session planned for
Thursday at the Forum. I set up the document structure, but have not
added any substantive content. Please consider the questions in the
etherpad before the session and either add content or be prepared to add
it in the room
I have created the etherpad for the forum session to discuss
deprecating python 2.
https://etherpad.openstack.org/p/YVR-python-2-deprecation-timeline
I pre-populated it with some of the details from the earlier mailing
list thread, but please add any additional notes you have that will
help
Excerpts from Alexandra Settle's message of 2018-05-09 13:13:44 +:
> Hi all,
>
> It is with a super heavy heart I have to say that I need to step down as core
> from the OpenStack-Ansible and Documentation teams – and take a step back
> from the community.
>
> The last year has taken me in
Excerpts from Lance Bragstad's message of 2018-05-04 15:16:09 -0500:
>
> On 05/04/2018 02:55 PM, Harry Rybacki wrote:
> > Greetings All,
> >
> > After a discussion in #openstack-tc[1] earlier today, the Keystone
> > team is adjusting its approach in proposing default roles[2].
> > Subsequently, I
Excerpts from Matthew Treinish's message of 2018-05-08 13:55:43 -0400:
> On Tue, May 08, 2018 at 01:34:11PM -0400, Doug Hellmann wrote:
> >
> > (added [glance] subject tag)
> >
> > Excerpts from Matthew Treinish's message of 2018-05-08 12:22:56 -0400:
> > >
(added [glance] subject tag)
Excerpts from Matthew Treinish's message of 2018-05-08 12:22:56 -0400:
> On Tue, May 08, 2018 at 05:01:36PM +0100, Graham Hayes wrote:
> > On 08/05/18 16:53, Doug Hellmann wrote:
> > > Excerpts from Graham Hayes's message of 2018-05-08 16:28:46 +010
(I added the [qa] topic tag for the QA team, since they own hacking, and
[requirements] for that team since I have a question about capping.)
Excerpts from Julia Kreger's message of 2018-05-08 12:43:07 -0400:
> About two hours ago, we started seeing Ironic CI jobs failing pep8
> with new
Excerpts from Graham Hayes's message of 2018-05-08 17:01:36 +0100:
> On 08/05/18 16:53, Doug Hellmann wrote:
> > Excerpts from Graham Hayes's message of 2018-05-08 16:28:46 +0100:
> >> On 08/05/18 16:09, Zane Bitter wrote:
> >>> On 30/04/18 17:16, Ben Nemec wro
Excerpts from Doug Hellmann's message of 2018-05-07 10:53:04 -0400:
[snip]
> The Adjutant project application [10] is still under review, and
> the only votes registered are opposed. I anticipate having the topic
> of how we review project applications as one of several items we
> discuss during
Excerpts from Graham Hayes's message of 2018-05-08 16:28:46 +0100:
> On 08/05/18 16:09, Zane Bitter wrote:
> > On 30/04/18 17:16, Ben Nemec wrote:
> >>> Excerpts from Doug Hellmann's message of 2018-04-25 16:54:46 -0400:
> 1. Fix oslo.service functional tests -- the Oslo team needs help
>
Excerpts from Michel Peterson's message of 2018-05-07 17:54:02 +0300:
> On Fri, Apr 20, 2018 at 11:06 PM, Doug Hellmann <d...@doughellmann.com>
> wrote:
>
> >
> > We have made great progress on this but we do still have quite a
> > few of these patches t
Excerpts from Julia Kreger's message of 2018-05-07 13:53:13 -0400:
> Greetings everyone,
>
> For some time, Rama Yeleswarapu (rama_y) has been graciously sending
> out a weekly update for Ironic to the mailing list. We found out late
> last week that this contributor would be unable to continue
Excerpts from Jeremy Stanley's message of 2018-05-07 14:06:35 +:
> On 2018-05-07 09:52:16 -0400 (-0400), Doug Hellmann wrote:
> [...]
> > 3. We could do nothing to record the work related to the goal.
> [...]
>
> For situations like 557863 I think I'd prefer either the st
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:
There is a patch to update the Python 3.5 goal for Kolla [1]. While
I'm glad to see the work happening, the change adds a new deliverable
to an old goal, and it isn’t clear whether we want to use that
approach for tracking goal work indefinitely. I see a few options.
1. We could update the
Excerpts from Jean-Philippe Evrard's message of 2018-05-07 13:36:34 +0200:
> We've been juggling with python3, ansible and multiple distros for a while
> now.
> That dance hasn't been fruitful: many hidden issues, either due to
> ansible modules, or our own modules, or upgrade issues.
>
> I've
Excerpts from Graham Hayes's message of 2018-05-02 20:15:14 +0100:
> On 02/05/18 20:11, Doug Hellmann wrote:
> > Excerpts from Zane Bitter's message of 2018-05-02 11:38:55 -0400:
> >> On 01/05/18 16:21, Doug Hellmann wrote:
> >>> Excerpts from Andreas Jaeger's messag
Excerpts from Petr Kovar's message of 2018-05-02 15:56:36 +0200:
> On Tue, 01 May 2018 10:08:23 -0400
> Doug Hellmann <d...@doughellmann.com> wrote:
>
> > The TC has had an item on our backlog for a while (a year?) to
> > document "constellations" of O
Excerpts from Zane Bitter's message of 2018-05-02 11:38:55 -0400:
> On 01/05/18 16:21, Doug Hellmann wrote:
> > Excerpts from Andreas Jaeger's message of 2018-05-01 21:51:19 +0200:
> >> On 05/01/2018 04:08 PM, Doug Hellmann wrote:
> >>> The TC has had an item on o
Excerpts from Jean-Philippe Evrard's message of 2018-05-02 17:14:07 +0200:
> Hello everyone,
>
> Now that we are all part-time, I'd like to toy with a new idea,
> proposed in the past by Jesse, to rotate the duties with people who
> are involved in OSA, or want to get involved more (it's not
Excerpts from Andreas Jaeger's message of 2018-05-01 21:51:19 +0200:
> On 05/01/2018 04:08 PM, Doug Hellmann wrote:
> > The TC has had an item on our backlog for a while (a year?) to
> > document "constellations" of OpenStack components to make it easier
> > for de
The TC has had an item on our backlog for a while (a year?) to
document "constellations" of OpenStack components to make it easier
for deployers and users to understand which parts they need to have
the features they want [1].
John Garbutt has started writing the first such document [2], but
as
Excerpts from Kendall Nelson's message of 2018-05-01 00:02:36 +:
> Hello Everyone :)
>
> Please join me in congratulating the 7 newly elected members of the
> Technical Committee (TC)!
>
>
>- Thierry Carrez (ttx)]
>- Chris Dent (cdent)
>- Sean McGinnis (smcginnis)
>- Davanum
Excerpts from Alex Schultz's message of 2018-04-30 15:43:16 -0600:
> On Mon, Apr 30, 2018 at 3:16 PM, Ben Nemec <openst...@nemebean.com> wrote:
> > Resending from an address that is subscribed to the list. Apologies to
> > those of you who get this twice.
> >
>
Excerpts from Ben Nemec's message of 2018-04-30 16:16:35 -0500:
> Resending from an address that is subscribed to the list. Apologies to
> those of you who get this twice.
>
> On 04/30/2018 10:06 AM, Doug Hellmann wrote:
> > It would be useful to have more input from PTLs on
Excerpts from Clark Boylan's message of 2018-04-26 11:22:15 -0700:
> On Thu, Apr 26, 2018, at 7:27 AM, Sean McGinnis wrote:
> > On Wed, Apr 25, 2018 at 04:54:46PM -0400, Doug Hellmann wrote:
> > > It's time to talk about the next steps in our migration from python
&
Excerpts from Doug Hellmann's message of 2018-04-27 10:02:08 -0400:
> The latest release of reno tries to add anchors to the page in a way
> that ensures they are named consistently across builds. For projects
> with the same version number in multiple series (which can happen for
> non-milestone
The latest release of reno tries to add anchors to the page in a way
that ensures they are named consistently across builds. For projects
with the same version number in multiple series (which can happen for
non-milestone projects that haven't tagged for rocky yet), this causes
duplicate anchors
For a while now I've been encouraging folks to propose follow-up patches
to fix nits on proposed changes, rather than waiting ages for someone to
respond to a -1 for a little typo. Today I've release git-nit, a tool to
make doing that easier.
The idea is that you would run a command like:
$
Excerpts from Jeremy Stanley's message of 2018-04-25 21:40:37 +:
> On 2018-04-25 16:54:46 -0400 (-0400), Doug Hellmann wrote:
> [...]
> > Still, we need to press on to the next phase of the migration, which
> > I have been calling "Python 3 first". This
It's time to talk about the next steps in our migration from python
2 to python 3.
Up to this point we have mostly focused on reaching a state where
we support both versions of the language. We are not quite there
with all projects, as you can see by reviewing the test coverage
status information
Excerpts from Adam Spiers's message of 2018-04-25 18:15:42 +0100:
> [BTW I hope it's not considered off-bounds for those of us who aren't
> TC election candidates to reply within these campaign question threads
> to responses from the candidates - but if so, let me know and I'll
> shut up ;-) ]
Excerpts from Doug Hellmann's message of 2018-04-25 15:06:37 -0400:
> Excerpts from zuul's message of 2018-04-25 18:04:07 +:
> > Build failed.
> >
> > - release-openstack-python
> >
Excerpts from zuul's message of 2018-04-25 18:04:07 +:
> Build failed.
>
> - release-openstack-python
> http://logs.openstack.org/25/25ef4b82d1d21f6e0ab442405eeb8b12e2024fb1/release/release-openstack-python/d9d8142/
> : SUCCESS in 4m 00s
> - announce-release
>
Excerpts from Sean McGinnis's message of 2018-04-25 11:55:43 -0500:
> > >
> > > [1] https://review.openstack.org/#/c/564232/
> > >
> >
> > The only concern I have is that it may slow the transition to the
> > python 3 version of the jobs, since someone would have to actually
> > fix the
Excerpts from Monty Taylor's message of 2018-04-25 16:40:47 +0200:
> Hi everybody,
>
> We've been working on navigating through from an interesting situation
> over the past few months, but there isn't a top-level overview of what's
> going on with it. That's my bad - I've been telling AJaeger
Excerpts from Sean McGinnis's message of 2018-04-25 09:59:13 -0500:
> > > > >
> > > > > I'd be more in favour of changing the zuul job to build with the '-W'
> > > > > flag. To be honest, there is no good reason to not have this flag
> > > > > enabled. I'm not sure that will be a popular opinion
Excerpts from Andrey Pavlov's message of 2018-04-23 21:42:56 +0300:
> Hello Sean,
>
> EC2-api team always used manual tagging because I know only this procedure.
> I thought that it's more convenient for me cause I can manage
> commits/branches.
> But in fact I don't mind to switch to automatic
Excerpts from Matt Riedemann's message of 2018-04-23 12:35:07 -0500:
> On 4/23/2018 12:18 PM, Doug Hellmann wrote:
> > I would like for us to collect some more data about what efforts
> > teams are making with encouraging new contributors, and what seems
> > to be working or n
ontributors.*
>
>
>
> May The Force of OpenStack Be With You,
>
> *Rico Lin*irc: ricolin
>
> 2018-04-23 22:06 GMT+08:00 Doug Hellmann <d...@doughellmann.com>:
>
> > [This is meant to be one of (I hope) several conversation-provoking
> > question
Excerpts from Chris Dent's message of 2018-04-23 17:50:31 +0100:
> On Mon, 23 Apr 2018, Tim Bell wrote:
>
> > One of the challenges in the academic sector is the time from
> > lightbulb moment to code commit. Many of the academic resource
> > opportunities are short term (e.g. PhDs, student
Excerpts from Jeremy Stanley's message of 2018-04-23 17:02:07 +:
> On 2018-04-23 12:02:14 -0400 (-0400), Zane Bitter wrote:
> [...]
> > The main thing I will be looking out for in those cases is that
> > the project followed the Four Opens *from the beginning*. Projects
> > that start from a
Excerpts from Graham Hayes's message of 2018-04-23 17:23:20 +0100:
> On 23/04/18 17:14, Doug Hellmann wrote:
> > Excerpts from Graham Hayes's message of 2018-04-23 16:27:04 +0100:
> >> On 23/04/18 16:04, Doug Hellmann wrote:
> >>> Excerpts from Graham Hayes's messag
Excerpts from Graham Hayes's message of 2018-04-23 16:27:04 +0100:
> On 23/04/18 16:04, Doug Hellmann wrote:
> > Excerpts from Graham Hayes's message of 2018-04-23 12:15:24 +0100:
> >> 7On 20/04/18 22:26, Doug Hellmann wrote:
> >>
> >>> Without le
Excerpts from Graham Hayes's message of 2018-04-23 15:36:32 +0100:
> On 18/04/18 11:38, Chris Dent wrote:
> > On Tue, 17 Apr 2018, Thierry Carrez wrote:
> >
> >> So... Is there any specific topic you think we should cover in that
> >> meeting ?
> >
> > The topics:
> >
> > 1. What are we to do,
Excerpts from Graham Hayes's message of 2018-04-23 12:15:24 +0100:
> 7On 20/04/18 22:26, Doug Hellmann wrote:
>
> > Without letting the conversation devolve too much into a discussion
> > of Adjutant's case, please talk a little about how you would evaluate
> > a project'
Excerpts from Chris Dent's message of 2018-04-23 12:09:42 +0100:
> On Fri, 20 Apr 2018, Doug Hellmann wrote:
>
> > [This is meant to be one of (I hope) several conversation-provoking
> > questions directed at prospective TC members to help the community
> > understan
Excerpts from Sean McGinnis's message of 2018-04-22 21:01:46 -0500:
> >
> > We are discussing adding at least one new project this cycle, and
> > the specific case of Adjutant has brought up questions about the
> > criteria we use for evaluating new projects when they apply to
> > become
Excerpts from Thierry Carrez's message of 2018-04-22 15:10:40 +0200:
> Doug Hellmann wrote:
> > [This is meant to be one of (I hope) several conversation-provoking
> > questions directed at prospective TC members to help the community
> > understand their positions before co
Excerpts from Rico Lin's message of 2018-04-22 16:50:51 +0800:
> Thanks, Doug, for raising this campaign question
>
>
> Here are my answers:
>
>
> ***How you would evaluate a project's application in general
>
> First I would work through the requirements ([1]) to evaluate projects.
> Since
e of the control of the new teams.
What role can, or should, the TC play in mediating these situations?
Doug
>
> Well I guess that is my two cents :)
>
> [0] https://hannibalhuang.github.io/
>
>
>
> On Sat, Apr 21, 2018 at 5:26 AM, Doug Hellmann <d...@doughellmann.com
on this matter now since TC
> has been doing rather well on this matter , but I guess this could be a
> precautious action :)
>
> On Mon, Apr 23, 2018 at 9:35 PM, Doug Hellmann <d...@doughellmann.com>
> wrote:
>
> > Excerpts from Doug Hellmann's message of 20
[This is meant to be one of (I hope) several conversation-provoking
questions directed at prospective TC members to help the community
understand their positions before considering how to vote in the
ongoing election.]
Over the last year we have seen some contraction in the number of
companies
[This is meant to be one of (I hope) several conversation-provoking
questions directed at prospective TC members to help the community
understand their positions before considering how to vote in the
ongoing election.]
In the course of evaluating new projects that have asked to join
as official
Excerpts from Doug Hellmann's message of 2018-04-23 09:27:09 -0400:
> [This is meant to be one of (I hope) several conversation-provoking
> questions directed at prospective TC members to help the community
> understand their positions before considering how to vote in the
> ongoing election.]
>
[This is meant to be one of (I hope) several conversation-provoking
questions directed at prospective TC members to help the community
understand their positions before considering how to vote in the
ongoing election.]
We frequently have discussions about whether the TC is active enough,
in terms
[This is meant to be one of (I hope) several conversation-provoking
questions directed at prospective TC members to help the community
understand their positions before considering how to vote in the
ongoing election.]
We are discussing adding at least one new project this cycle, and
the specific
Excerpts from Doug Hellmann's message of 2018-04-11 12:20:46 -0400:
> Excerpts from Matthew Thode's message of 2018-04-05 10:47:37 -0500:
> > eventlet-0.22.1 has been out for a while now, we should try and use it.
> > Going to be fun times.
> >
> > I have a review projects can depend upon if they
Excerpts from Doug Hellmann's message of 2018-04-19 09:15:49 -0400:
> Today is the deadline for proposing a release for the Rocky-1 milestone.
> Please don't forget to include your libraries (client or otherwise) as
> well.
>
> Doug
A few projects have missed the first milestone tagging
Excerpts from zuul's message of 2018-04-20 13:59:14 +:
> Build failed.
>
> - release-openstack-python
> http://logs.openstack.org/fa/fabeaffa6efe8b1ef3d828f5b8c2cdc896e4afe9/pre-release/release-openstack-python/c624655/
> : FAILURE in 6m 07s
> - announce-release announce-release : SKIPPED
>
Excerpts from Jim Rollenhagen's message of 2018-04-20 09:05:23 -0400:
> On Fri, Apr 20, 2018 at 7:33 AM, Jim Rollenhagen <j...@jimrollenhagen.com>
> wrote:
>
> > On Thu, Apr 19, 2018 at 3:21 PM, Doug Hellmann <d...@doughellmann.com>
> > wrote:
> >&g
Excerpts from Jim Rollenhagen's message of 2018-04-20 07:33:51 -0400:
> On Thu, Apr 19, 2018 at 3:21 PM, Doug Hellmann <d...@doughellmann.com>
> wrote:
> >
> >
> > Reading through that log more carefully, I see an early attempt to pin
> > pycodestyle <= 2
Excerpts from Matt Riedemann's message of 2018-04-19 13:34:44 -0500:
> On 4/19/2018 1:15 PM, Doug Hellmann wrote:
> > Second, releasing early and often gives us more time to fix issues,
> > so we aren't rushing around at deadline trying to solve a problem
> > while the gate
Excerpts from Jim Rollenhagen's message of 2018-04-18 13:44:08 -0400:
> Hi all,
>
> We have a number of stable branch jobs failing[0] with an error about pep8
> not being importable[1], when it's clearly installed[2]. We first saw this
> when installing networking-generic-switch on queens in our
to do a client library release prior
> >to R-3? The practice seems to change from cycle to cycle.
> >
> >On 4/19/18, 6:15 AM, "Doug Hellmann" <d...@doughellmann.com> wrote:
> >
> >>Today is the deadline for proposing a release for the Rocky-1 mileston
Excerpts from zuul's message of 2018-04-19 13:22:40 +:
> Build failed.
>
> - release-openstack-python
> http://logs.openstack.org/c9/c9263cde360d37654c4298c496cd9af251f23ce7/pre-release/release-openstack-python/541ad7d/
> : FAILURE in 3m 48s
> - announce-release announce-release : SKIPPED
>
Excerpts from Doug Hellmann's message of 2018-04-19 09:38:31 -0400:
> Excerpts from zuul's message of 2018-04-19 13:22:40 +:
> > Build failed.
> >
> > - release-openstack-python
> >
Today is the deadline for proposing a release for the Rocky-1 milestone.
Please don't forget to include your libraries (client or otherwise) as
well.
Doug
__
OpenStack Development Mailing List (not for usage questions)
Excerpts from Mark Kirkwood's message of 2018-04-19 16:47:58 +1200:
> Swift has had storage policies for a while now. These are enabled by
> setting the 'X-Storage-Policy' header on a container.
>
> It looks to me like this is not possible using openstack-client (even in
> master branch) -
Excerpts from Jim Rollenhagen's message of 2018-04-18 13:44:08 -0400:
> Hi all,
>
> We have a number of stable branch jobs failing[0] with an error about pep8
> not being importable[1], when it's clearly installed[2]. We first saw this
> when installing networking-generic-switch on queens in our
Excerpts from Graham Hayes's message of 2018-04-17 13:40:05 +0100:
> On 17/04/18 07:10, Adrian Turjak wrote:
> > Hello devs,
> >
> > The python27 clock of doom ticks closer to zero
> > (https://pythonclock.org/) and officially dropping python27 support is
> > going to have to happen eventually,
Excerpts from Monty Taylor's message of 2018-04-12 13:54:46 -0500:
> On 04/12/2018 11:27 AM, Clark Boylan wrote:
> > On Wed, Apr 11, 2018, at 5:45 PM, Matt Riedemann wrote:
> >> I also seem to remember that [extras] was less than user-friendly for
> >> some reason, but maybe that was just because
I thought some folks from our community would be interested in the
ongoing work on the Python Package Index (PyPI). The article
mentioned in this post to the distutils mailing list provides a
good history and a description of the new and planned features for
"Warehouse".
Doug
--- Begin
Excerpts from Doug Hellmann's message of 2018-04-11 12:20:46 -0400:
> Excerpts from Matthew Thode's message of 2018-04-05 10:47:37 -0500:
> > eventlet-0.22.1 has been out for a while now, we should try and use it.
> > Going to be fun times.
> >
> > I have a review projects can depend upon if they
Excerpts from Matthew Thode's message of 2018-04-05 10:47:37 -0500:
> eventlet-0.22.1 has been out for a while now, we should try and use it.
> Going to be fun times.
>
> I have a review projects can depend upon if they wish to test.
> https://review.openstack.org/533021
I have proposed a bunch
t.gz
>
> Best Regards!
>
> Kevin (Chen) Ji 纪 晨
>
> Engineer, zVM Development, CSTL
> Notes: Chen CH Ji/China/IBM@IBMCN Internet: jiche...@cn.ibm.com
> Phone: +86-10-82451493
> Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian District,
> Beijing 100193, PRC
&g
Excerpts from IWAMOTO Toshihiro's message of 2018-04-11 18:19:02 +0900:
> On Mon, 09 Apr 2018 22:58:28 +0900,
> Doug Hellmann wrote:
> >
> > Excerpts from Tony Breeds's message of 2018-04-09 13:39:30 +1000:
> > > On Fri, Apr 06, 2018 at 09:41:07AM -0700, Clark Boyl
Excerpts from Tony Breeds's message of 2018-04-09 13:39:30 +1000:
> On Fri, Apr 06, 2018 at 09:41:07AM -0700, Clark Boylan wrote:
>
> > My understanding of our use of upper constraints was that this should
> > (almost) always be the case for (almost) all dependencies. We should
> > rely on
Excerpts from super user's message of 2018-04-06 17:10:32 +0900:
> Hope you fix this soon, there are many patches depend on the 'match the
> minimum version' problem which causes requirements-check fail.
The problem is with *those patches* and not the check.
I've been trying to update some, but
Excerpts from Doug Hellmann's message of 2018-03-28 18:53:03 -0400:
>
> Because we had some communication issues and did a few steps out
> of order, when this patch lands projects that have approved
> bot-proposed requirements updates may find that their requirements
> and lower-constraints files
Excerpts from melanie witt's message of 2018-04-03 15:30:07 -0700:
> On Tue, 3 Apr 2018 15:26:17 -0700, Melanie Witt wrote:
> > On Wed, 4 Apr 2018 07:54:59 +1000, Michael Still wrote:
> >> Thanks to jichenjc for fixing the pep8 failures I was seeing on master.
> >> I'd decided they were specific
Excerpts from Michael Still's message of 2018-04-03 22:23:10 +:
> I think the bit I am lost on is the concept of running pep8 "under" a
> version of python. Is this an artifact of what version of pep8 I have
> installed somehow?
>
> If the py3 pep8 is stricter, couldn't we just move to only
Excerpts from Michael Still's message of 2018-04-04 07:54:59 +1000:
> Thanks to jichenjc for fixing the pep8 failures I was seeing on master. I'd
> decided they were specific to my local dev environment given no one else
> was seeing them.
>
> As I said in the patch that fixed the issue [1], I
stack.org/#/c/558084/
> [3] https://review.openstack.org/#/c/557012/
>
> -efried
Thanks, Eric! That looks like it should do the trick. I'll give it
a try.
Doug
>
> On 03/30/2018 06:35 AM, Doug Hellmann wrote:
> > Anyone?
> >
> >> On Mar 28, 2018, at 1:26 PM, Doug Hellman
On Mar 30, 2018, at 4:08 AM, Renat Akhmerov <renat.akhme...@gmail.com
<mailto:renat.akhme...@gmail.com>> wrote:
> On 29 Mar 2018, 20:20 +0700, Doug Hellmann <d...@doughellmann.com
> <mailto:d...@doughellmann.com>>, wrote:
>
>> What sorts of tools are
Anyone?
> On Mar 28, 2018, at 1:26 PM, Doug Hellmann <d...@doughellmann.com> wrote:
>
> In the course of preparing the next release of oslo.config, Ben noticed
> that nova's unit tests fail with oslo.config master [1].
>
> The underlying issue is that the tests mock
Excerpts from Renat Akhmerov's message of 2018-03-29 15:33:58 +0700:
> After some discussion in IRC on this topic there was an idea just to write
> and push upstream needed tools using objgraph w/o having it in the
> requirements.txt at all. We just need to make sure that those tools are never
Excerpts from corvus's message of 2018-03-28 13:21:38 -0700:
> Hi,
>
> I've proposed a change to devstack which slightly alters the
> LIBS_FROM_GIT behavior. This shouldn't be a significant change for
> those using legacy devstack jobs (but you may want to be aware of it).
> It is more
We're making good progress. Some of the important parts of the
global job changes are in place. There are still a lot of open
patches to add the lower-constraints jobs to repos, however.
Excerpts from Doug Hellmann's message of 2018-03-15 07:03:11 -0400:
[...]
> What I Want to Do
>
In the course of preparing the next release of oslo.config, Ben noticed
that nova's unit tests fail with oslo.config master [1].
The underlying issue is that the tests mock things that oslo.config
is now calling as part of determining where options are being set
in code. This isn't an API change
Excerpts from Thierry Carrez's message of 2018-03-26 15:33:03 +0200:
> Hi!
>
> TL;DR:
> We used to do complex things with ACLs for stable/* branches around
> releases. Let's stop doing that as it's not really useful anyway, and
> just trust the $project-stable-maint teams to do the right thing.
Excerpts from zuul's message of 2018-03-26 18:11:49 +:
> Build failed.
>
> - publish-openstack-releasenotes
> http://logs.openstack.org/94/94bb28ae46bd263314c9d846069ca913d225e625/tag/publish-openstack-releasenotes/9440894/
> : POST_FAILURE in 3m 29s
>
This release notes build failure is
Excerpts from melanie witt's message of 2018-03-26 12:28:02 -0700:
> On Mon, 26 Mar 2018 14:12:52 -0500, Matt Riedemann wrote:
> > On 3/26/2018 6:24 AM, ChangBo Guo wrote:
> >> What's your use case for ListOpt, just make sure the value(a list) is
> >> part of 'choices' ? Maybe we need another
Excerpts from Matt Riedemann's message of 2018-03-26 14:12:52 -0500:
> On 3/26/2018 6:24 AM, ChangBo Guo wrote:
> > What's your use case for ListOpt, just make sure the value(a list) is
> > part of 'choices' ? Maybe we need another parameter to distinguish
>
> It came up because of this
401 - 500 of 3301 matches
Mail list logo
