nts).
I'm inclined to include it and either use a direct mailing or the
[tc] tag on the new discuss list to reach TC members, but I would
like to hear feedback from TC members and other interested parties
before calling that decision made. Please let me
Excerpts from Petr Kovar's message of 2018-09-19 11:50:22 -0700:
> Hi all,
>
> Based on our PTG discussion, I'd like to nominate Ian Y. Choi for
> membership in the openstack-doc-core team. I think Ian doesn't need an
> introduction, he's been around for a while, recently being deeply involved
> i
Excerpts from Chris Dent's message of 2018-09-19 12:31:26 +0100:
> On Tue, 18 Sep 2018, Doug Hellmann wrote:
>
> > [Redirecting this from the openstack-tc list to the -dev list.]
> > Excerpts from Melvin Hillsman's message of 2018-09-18 17:43:57 -0500:
> >>
[Redirecting this from the openstack-tc list to the -dev list.]
Excerpts from Melvin Hillsman's message of 2018-09-18 17:43:57 -0500:
> Hey everyone,
>
> UC is proposing a joint UC/TC meeting at the end of the month say starting
> after Berlin to work more closely together. The last Monday of the
Excerpts from Lance Bragstad's message of 2018-09-18 12:27:06 -0500:
> On Tue, Sep 18, 2018 at 12:17 PM Doug Hellmann
> wrote:
>
> > Excerpts from Lance Bragstad's message of 2018-09-18 11:56:22 -0500:
> > > On Tue, Sep 18, 2018 at 10:17 AM Doug Hellmann
> &
ple the tempest-full-py3 job [1] defines USE_PYTHON3 as
'true'.
What's probably missing is a version of the grenade job that allows us
to control that USE_PYTHON3 variable before and after the upgrade.
I see a few different grenade jobs (neutron-grenade,
neutro
Excerpts from Lance Bragstad's message of 2018-09-18 11:56:22 -0500:
> On Tue, Sep 18, 2018 at 10:17 AM Doug Hellmann
> wrote:
>
> > Excerpts from Zhipeng Huang's message of 2018-09-14 18:51:40 -0600:
> > > Hi,
> > >
> > > Based upon the discu
nication channels (especially
the mailing list), so that we can all collaborate there together.
There was support for an approach like that in the room during the
meeting last week.
Doug
__
OpenStack Development Mailing Lis
ul| tox defaults | Docs| 3.6 unit | Failing |
Total | Champion |
+-+-+--+-+--+-+---++
| adjutant| + | -| - | +| 0 |
5 | Doug Hellma
tack.org/p/community-goals) and then we can
see if we actually need to manage goals across multiple release
cycles as a single unit.
Doug
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-d
Excerpts from Jay Pipes's message of 2018-09-17 17:07:43 -0400:
> On 09/17/2018 04:50 PM, Doug Hellmann wrote:
> > Excerpts from Zane Bitter's message of 2018-09-17 16:12:30 -0400:
> >> On 17/09/18 3:06 PM, Jay Pipes wrote:
> >>> On 09/17/2018 01:31 PM,
Excerpts from Zane Bitter's message of 2018-09-17 16:12:30 -0400:
> On 17/09/18 3:06 PM, Jay Pipes wrote:
> > On 09/17/2018 01:31 PM, Doug Hellmann wrote:
> >> New Project Application Process
> >> ===
> >>
> >> We wra
Excerpts from Ken Giusti's message of 2018-09-17 13:18:28 -0400:
> On Thu, Sep 13, 2018 at 7:39 PM Doug Hellmann wrote:
> > Excerpts from Jim Rollenhagen's message of 2018-09-13 12:08:08 -0600:
[snip]
> > > A specific example brought up in the ironic room was the wa
k. We will still be working
on the problem, but since it may never be done we didn't feel like
tracking it as a "task" made sense. Doug, Thierry, and Jeremy talked
with the Infra team about upgrading and adding tools later in the
week.
We removed StarlingX from the tracker because the
now
(install, user, api, etc.). The latex builder supports extracting
different sections of the content to create separate output files by
starting at a different root file. I wonder if that's another reasonable
approach for us to take here?
Doug
Excerpts from Mathieu Gagné's message of 2018-09-13 20:09:12 -0400:
> On Thu, Sep 13, 2018 at 7:41 PM, Doug Hellmann wrote:
> > Excerpts from Mathieu Gagné's message of 2018-09-13 14:12:56 -0400:
> >> On Wed, Sep 12, 2018 at 2:04 PM, Doug Hellmann
> >> wrot
Excerpts from Mathieu Gagné's message of 2018-09-13 14:12:56 -0400:
> On Wed, Sep 12, 2018 at 2:04 PM, Doug Hellmann wrote:
> >
> > IIRC, we also talked about not supporting multiple versions of
> > python on a given node, so all of the services on a node would need
&
Excerpts from Jim Rollenhagen's message of 2018-09-13 12:08:08 -0600:
> On Wed, Sep 12, 2018 at 2:28 PM, Doug Hellmann
> wrote:
>
> > Excerpts from Doug Hellmann's message of 2018-09-12 12:04:02 -0600:
> > > Excerpts from Clark Boylan's message of 2018-09
Excerpts from Michel Peterson's message of 2018-09-13 10:04:27 +0300:
> On Thu, Sep 13, 2018 at 1:09 AM, Doug Hellmann
> wrote:
>
> > The longer version is that we want to continue to use the existing
> > tox environment in each project as the basis for the job, sinc
> I would appreciate if you handle releasenotes the same way as other
> documents, so if you want to change releasenotes in the end, please do
Good idea.
Doug
__
OpenStack Development Mailing List (not for usage question
Excerpts from Thomas Goirand's message of 2018-09-13 12:23:32 +0200:
> On 09/13/2018 12:52 AM, Chris Friesen wrote:
> > On 9/12/2018 12:04 PM, Doug Hellmann wrote:
> >
> >>> This came up in a Vancouver summit session (the python3 one I think).
> >>>
Excerpts from Chris Friesen's message of 2018-09-12 16:52:16 -0600:
> On 9/12/2018 12:04 PM, Doug Hellmann wrote:
>
> >> This came up in a Vancouver summit session (the python3 one I think).
> >> General consensus there seemed to be that we should have grenade jobs
d [3].
As usual, please let me know if I've left out or mistaken any
details.
Doug
[1] https://review.openstack.org/572559
[2] https://review.openstack.org/588110
[3] https://review.openstack.org/601659
__
OpenStack Deve
Excerpts from Doug Hellmann's message of 2018-09-12 12:04:02 -0600:
> Excerpts from Clark Boylan's message of 2018-09-12 10:44:55 -0700:
> > On Wed, Sep 12, 2018, at 10:23 AM, Jim Rollenhagen wrote:
> > > The process of operators upgrading Python versions across th
into gerrit and keep iterating on it to
make it usable for the goal. Maybe we can get one of the projects most
interested in working on this goal early to help with testing and UX
feedback.
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
so talked about not supporting multiple versions of
python on a given node, so all of the services on a node would need
to be upgraded together.
Doug
__
OpenStack Development Mailing List (not for usage questions)
Unsubscri
|0 | 0 | 4 | DONE | Doug
Hellmann |
| barbican| 11 | 6 | 13 | migration in progress | Doug
Hellmann |
| blazar | 16 | 0 |16 | migration in progress | Nguyen
Hai |
| Chef OpenStack
We usually want the things committed upstream to be testable in
some way. Do you have the ability to set up third-party CI of some
sort for the deployment tools you're talking about?
Doug
__
OpenStack Development Mailing
Here are the patches for the zuul migration for the OpenStack Charms
project.
+---+---+---+
| Subject | Repo
Here are the zuul migration patches for the trove team's repositories.
Please prioritize these reviews.
+--++---+
| Subject | Repo
| Branch
two release cycles, as per usual.
>
> Thank you to Mohammed for facilitating the discussion, we really
> appreciate it.
>
> Cheers,
> -melanie
>
This is good news. Thank you all for taking the time to sit down and put
this plan together.
Doug
_
t; Let me know if you have any questions or concerns,
> Michael
>
I see you've updated the wiki, too. Thanks for the heads-up!
Doug
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: open
Melanie gave me the go-ahead to propose the patches, so here's the list
of patches for the zuul migration, doc job update, and python 3.6 unit
tests for the nova repositories.
+--++---+
| Subject
nt times to
extract review statistics from gerrit. Is that the sort of thing you
mean?
What information would you find useful?
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 apparently missed the email Sean sent a while back saying it was OK to
start the migration, but we talked today and so I've submitted the
patches to move cinder's zuul settings. Here's
Excerpts from Ghanshyam Mann's message of 2018-08-31 19:56:33 +0900:
>
>
>
> Thanks Doug. QA is ready for this work. Let me know the link and ll review
> those.
Here's the list o
openstack-dev) will rely on me
being online, which is less likely if I'm in a session.
Doug
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubsc
error at [1], it looks like someone is manually
publishing releases from openstack/networking-ansible and then
tagging them, instead of letting the release machinery publish based
on the tag.
Doug
[1]
http://logs.openstack.org/63/639a3c3590ec20c33b1435e960d5331780298915/release/release-openstack-pyt
Excerpts from Lance Bragstad's message of 2018-09-06 15:01:01 -0500:
> I'm noticing some odd cases with respect to the python 3 community goal
> [0]. So far my findings are specific to keystone repositories, but I can
> imagine this affecting other projects.
>
> Do
need for our
CI? "generic"?
What is the "ID" of the webhook? The number at the end of the URL, or
the token associated with it?
Doug
>
> for what to do (if you read the failing job logs, it also points you
> to this).
>
> I (or #openstack-infra) can help,
wanted to say "merci" to the
> community who gave me a chance to be part of this team.
Thank you, Emilien. I've always appreciated having your perspective
and assistance on the TC.
Doug
__
OpenStack Developme
project! Please do consider running if you are at all interested.
>
> Thanks again,
> Paul
>
Thank you for serving this year, Paul!
Doug
__
OpenStack Development Mailing List (not for usage questions)
Unsubscri
Excerpts from Ben Nemec's message of 2018-09-04 18:39:35 -0500:
> Would it be helpful to factor some of the common code out into an Oslo
> library so projects basically just have to subclass, implement check
> functions, and add them to the _upgrade_checks dict? It's not a huge
> amount of code,
--+
| adjutant|4 | 4 | migration in progress
| Doug Hellmann |
| barbican| 13 |13 | migration in progress
| Doug Hellmann |
| blazar | 16 |
Excerpts from Jay Pipes's message of 2018-09-04 12:08:41 -0400:
> On 09/04/2018 11:44 AM, Doug Hellmann wrote:
> > Excerpts from Chris Dent's message of 2018-09-04 15:32:12 +0100:
> >> On Tue, 4 Sep 2018, Jay Pipes wrote:
> >>
> >>> Is there a r
Excerpts from Ade Lee's message of 2018-09-04 08:21:51 -0400:
> Barbican is ready.
>
> Thanks,
> Ade
Here you go:
+---+---+-+---+
| Subject
Excerpts from Chris Dent's message of 2018-09-04 15:32:12 +0100:
> On Tue, 4 Sep 2018, Jay Pipes wrote:
>
> > Is there a reason we couldn't have openstack-placement be the package name?
>
> I would hope we'd be able to do that, and probably should do that.
> 'openstack-placement' seems a find pyp
7;t have openstack-placement be the package name?
That would work fine. The package name is set in setup.cfg and we
have several examples where the value there and repo name don't
match.
Doug
>
> Best,
> -jay
>
rtunity to serve the
project through the Technical Committee over the coming year.
Thank you,
Doug
Candidacy submission: https://review.openstack.org/599582
Review history: https://review.openstack.org/#/q/reviewer:2472,n,z
Commit history: https://review.openstack.org/#/q/owner:2472,n,z
Foun
Excerpts from Matthew Thode's message of 2018-08-31 09:13:00 -0500:
> On 18-08-31 07:44:44, Jim Rollenhagen wrote:
> >
> > Tempest plugins, like tempest, are not meant to be branched:
> > http://lists.openstack.org/pipermail/openstack-dev/2018-August/133211.html
> >
>
> Yep, it's only on the li
Excerpts from Dirk Müller's message of 2018-08-31 15:26:10 +0200:
> Am Fr., 31. Aug. 2018 um 01:28 Uhr schrieb Doug Hellmann
> :
>
> Hi Doug,
>
> > | Packaging-rpm | 4 repos |
>
> We're ready - please send the patches.
&
Excerpts from Tobias Urdin's message of 2018-08-31 13:31:24 +0200:
> Oh, that's bad. I will abandon.
> It's a go for Puppet then.
>
> Best regards
There are quite a few patches for all of the Puppet modules.
+---+---
Excerpts from Christophe Sauthier's message of 2018-08-31 11:20:33 +0200:
> We are ready to start on the cloudkitty's team !
>
> Christophe
Here are the patches:
+-+-+-+--
Excerpts from Mehdi Abaakouk's message of 2018-08-31 08:09:00 +0200:
> Telemetry is ready
Here you go:
+++-+---+
| Subject| R
Excerpts from Adrian Turjak's message of 2018-08-31 17:51:15 +1200:
> Adjutant should be should be good to go. I don't believe there are any
> blockers (unless I've missed some).
I've proposed the needed patches:
+---++--
Excerpts from Samuel Cassiba's message of 2018-08-30 16:50:30 -0700:
> On Thu, Aug 30, 2018 at 4:24 PM, Doug Hellmann wrote:
> > Below is the list of project teams that have not yet started migrating
> > their zuul configuration. If you're ready to go, please respond to
Below is the list of project teams that have not yet started migrating
their zuul configuration. If you're ready to go, please respond to this
email to let us know so we can start proposing patches.
Doug
| adjutant| 3 repos |
| barbican| 5 repos |
| Chef Open
Excerpts from Doug Hellmann's message of 2018-08-29 20:04:16 -0400:
> Excerpts from Doug Hellmann's message of 2018-08-29 15:22:56 -0400:
> > Excerpts from David Peacock's message of 2018-08-29 15:12:03 -0400:
> > > On Wed, Aug 29, 2018 at 1:
will add a new
check job to all projects so that if any packaging-related files
are changed the ability to package the project is tested. Let me
know if you run into any difficulties.
Doug
[1] https://review.openstack.org/5
re the job
started failing.
So, again, please don't block the migration work on aesthetic concerns.
This will all go much more smoothly and quickly if we save those changes
for later.
Doug
__
OpenStack Development Mailin
can do more demos later.
>
> [1]
> https://github.com/edisonxiang/OpenAPI-Specification/blob/master/examples/v3.0/petstore.yaml
> [2] https://editor.swagger.io
>
> Best Regards,
> Edison Xiang
How does this proposal relate to the work that has already been
done to build the API
Excerpts from Michel Peterson's message of 2018-08-30 09:43:30 +0300:
> On Thu, Aug 30, 2018 at 3:11 AM, Doug Hellmann
> wrote:
>
> > > OK, there are somewhere just over 100 patches for all of the neutron
> > > repositories, so I'm going to wait for a quiete
Excerpts from Michel Peterson's message of 2018-08-30 12:51:04 +0300:
> On Thu, Aug 30, 2018 at 3:11 AM, Doug Hellmann
> wrote:
>
> > | import zuul job settings from project-config | openstack/networking-odl
> > | https://review.openstack.org/597870 | ma
Excerpts from Andreas Jaeger's message of 2018-08-30 17:32:46 +0200:
> On 2018-08-30 17:16, Nate Johnston wrote:
> > On Thu, Aug 30, 2018 at 08:28:40AM -0400, Doug Hellmann wrote:
> >> Excerpts from Michel Peterson's message of 2018-08-30 14:38:00 +0300:
> >&
the MM2 version
> we're currently using.
>
> Also, in case you were wondering, no the irony of cross-posting this
> message to four mailing lists is not lost on me. ;)
>
> [1] https://etherpad.openstack.org/p/YVR-ops-devs-one-community
> [2] https://ether
everal, like in the neutron case, it probably makes sense to
create a separate section of the page with a table for all of them,
just to keep things organized.
Doug
__
OpenStack Development Mailing List (not for usage quest
Excerpts from Doug Hellmann's message of 2018-08-29 17:49:28 -0400:
> Excerpts from Nate Johnston's message of 2018-08-29 17:14:11 -0400:
> > On Tue, Aug 28, 2018 at 05:46:09PM -0400, Doug Hellmann wrote:
> > > Excerpts from Michel Peterson's message of 2018-08-
Excerpts from Doug Hellmann's message of 2018-08-29 15:22:56 -0400:
> Excerpts from David Peacock's message of 2018-08-29 15:12:03 -0400:
> > On Wed, Aug 29, 2018 at 1:02 PM Doug Hellmann wrote:
> >
> > > Excerpts from Doug Hellmann's message of 2018-08-2
Excerpts from Nate Johnston's message of 2018-08-29 17:14:11 -0400:
> On Tue, Aug 28, 2018 at 05:46:09PM -0400, Doug Hellmann wrote:
> > Excerpts from Michel Peterson's message of 2018-08-28 16:30:02 +0300:
> > > On Mon, Aug 27, 2018 at 10:37 PM
ssues on our end.
>
> [0]
> https://review.openstack.org/#/q/(status:open+OR+status:merged)+project:openstack/keystone+topic:python3-first
I've submitted new versions of
Excerpts from David Peacock's message of 2018-08-29 15:12:03 -0400:
> On Wed, Aug 29, 2018 at 1:02 PM Doug Hellmann wrote:
>
> > Excerpts from Doug Hellmann's message of 2018-08-29 09:50:58 -0400:
> > > Excerpts from David Peacock's message of 2018-08-29 08
Excerpts from Doug Hellmann's message of 2018-08-29 09:50:58 -0400:
> Excerpts from David Peacock's message of 2018-08-29 08:53:26 -0400:
> > On Mon, Aug 27, 2018 at 3:38 PM Doug Hellmann wrote:
> >
> > > If your team is ready to have your zuul settings mig
Excerpts from David Peacock's message of 2018-08-29 08:53:26 -0400:
> On Mon, Aug 27, 2018 at 3:38 PM Doug Hellmann wrote:
>
> > If your team is ready to have your zuul settings migrated, please
> > let us know by following up to this email. We will start with the
> &
Excerpts from Nguyễn Trí Hải's message of 2018-08-29 12:02:12 +0900:
> For dealing with this problem, I turn off all the Timeline events in
> Preferences.
Nice tip! I didn't realize that was something I could control.
Thanks,
Doug
>
> On Wed, Aug 29, 2018 at 6:58 A
e community to start thinking
about who you want to have serving on the TC, and to encourage those
folks to run. Don't rely on them to nominate themselves without being
prompted.
Doug
__
OpenStack Develo
https://review.openstack.org/597244 has a tool to change the task
assignment for 1 task
The UX for the assignment tool is terrible, so you have to provide
your numerical user ID. The easiest way to find that may be to use
the list tool and copy it from one of the tasks already assigned
to you.
Excerpts from Michel Peterson's message of 2018-08-28 16:30:02 +0300:
> On Mon, Aug 27, 2018 at 10:37 PM, Doug Hellmann
> wrote:
>
> >
> > If your team is ready to have your zuul settings migrated, please
> > let us know by following up to this email. We will st
Excerpts from Doug Hellmann's message of 2018-08-28 17:42:29 -0400:
> Excerpts from Zane Bitter's message of 2018-08-28 16:47:06 -0400:
> > On 27/08/18 15:37, Doug Hellmann wrote:
> > > == Next Steps ==
> > >
> > > If your team is ready to have yo
Excerpts from Zane Bitter's message of 2018-08-28 16:47:06 -0400:
> On 27/08/18 15:37, Doug Hellmann wrote:
> > == Next Steps ==
> >
> > If your team is ready to have your zuul settings migrated, please
> > let us know by following up to this email. We will start w
nt misconception and follow up with a
> link to the review. I'm also going to post to the legal-discuss ML
> so as to make the subscribers there aware of this thread.
Yes, please do propose that documentation update in the governance
repo. I wonder if we should address this at all in the cont
This is week 3 of the "Run under Python 3 by default" goal
(https://governance.openstack.org/tc/goals/stein/python3-first.html).
== What we learned last week ==
We have a few enthusiastic folks who want to contribute to the goal
who have not been involved in the previous discussion with goal
cha
y, and have settled
on the idea of placing Eric's version of the code (with the thread-safe
fix and the module-level global) in oslo_utils.fixture to allow it to
easily reuse the oslo_utils.uuidutils module and still be clearly marked
as test code.
Doug
> On Aug 23, 2018, at 4:01 PM, Ben Nemec wrote:
>
>
>
>> On 08/23/2018 12:25 PM, Doug Hellmann wrote:
>> Excerpts from Eric Fried's message of 2018-08-23 09:51:21 -0500:
>>> Do you mean an actual fixture, that would be used like:
>>>
>>
sioned, yes. In the absence of a global,
which we do not want, what other API would you propose?
Doug
>
> efried
>
> On 08/23/2018 07:40 AM, Jay Pipes wrote:
> > On 08/23/2018 08:06 AM, Doug Hellmann wrote:
> >> Excerpts from Davanum Srinivas (dims)'s messag
On 23/08/18 13:34, Doug Hellmann wrote:
Excerpts from Doug Szumski's message of 2018-08-23 09:53:35 +0100:
Thanks Doug, we had a discussion and we agreed that the best way to
proceed is for you to submit your patches and we will carefully review them.
I proposed those patches this mo
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 Szumski's message of 2018-08-23 09:53:35 +0100:
> Thanks Doug, we had a discussion and we agreed that the best way to
> proceed is for you to submit your patches and we will carefully review them.
I proposed those patches this morning. With the aid of you
ts, but we hardly need to rely on that if
we're making a test fixture for oslotest.
My vote is to add a new fixture class to oslo_utils.fixture.
Doug
>
> On Wed, Aug 22, 2018 at 11:24 PM Jay Pipes wrote:
>
> >
> > On Wed, Aug 22, 2018, 10:13 AM Eric Fried
Reply in-line.
On 23/08/18 00:32, Doug Hellmann wrote:
Monasca team,
It looks like you have self-proposed some, but not all, of the
patches to import the zuul settings into monasca repositories.
I found these
gh
some of the ones I have generated locally may be bogus because of
the existing changes.
I realize Witold is OOO for a while, so I'm emailing the list to
ask the team how you want to proceed. Should I go ahead and propose
the patche
Excerpts from Eric Fried's message of 2018-08-22 09:13:25 -0500:
> For some time, nova has been using uuidsentinel [1] which conveniently
> allows you to get a random UUID in a single LOC with a readable name
> that's the same every time you reference it within that process (but not
> across proces
Excerpts from melanie witt's message of 2018-08-21 15:05:00 -0700:
> On Tue, 21 Aug 2018 16:41:11 -0400, Doug Hellmann wrote:
> > Excerpts from melanie witt's message of 2018-08-21 12:53:43 -0700:
> >> On Tue, 21 Aug 2018 06:50:56 -0500, Matt Riedemann wrote:
> >
Excerpts from William M Edmonds's message of 2018-08-22 07:42:43 -0400:
>
> Doug Hellmann wrote on 08/20/2018 11:27:09 AM:
> > If your team is ready to have your zuul settings migrated, please
> > let us know by following up to this email. We will start with the
> >
of a review team for the placement
repository after the code is moved out of openstack/nova?
How many of them are also members of the nova-core team?
What do you think those folks are more interested in working on than the
things you listed as needing to be done to support the nova use cases?
What can they do to reassure you that they will work on the items
nova needs, regardless of the governance structure?
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
s and lots of people who we
have to train to use the tools.
If you are not one of the people already listed as a goal champion
on [1], please PLEASE stop writing patches and get in touch with
me personally and directly (via IRC or email) BEFORE doing any more
work on the goal.
Thanks,
Doug
[1]
nce they cannot land without the project-config change.
Doug
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack
Excerpts from Doug Hellmann's message of 2018-08-20 16:34:22 -0400:
> Excerpts from Telles Nobrega's message of 2018-08-20 15:07:29 -0300:
> > Hi Doug,
> >
> > I believe Sahara is ready to have those patches worked on.
> >
> > Do we have to do anything
Excerpts from Telles Nobrega's message of 2018-08-20 15:07:29 -0300:
> Hi Doug,
>
> I believe Sahara is ready to have those patches worked on.
>
> Do we have to do anything specific to get the env ready?
Just be ready to do the reviews. I am generating the patches now and
wi
Excerpts from Doug Hellmann's message of 2018-08-08 09:18:44 -0400:
> 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. Base
This is week 2 of the roll-out of the "Run under Python 3 by default"
goal (https://governance.openstack.org/tc/goals/stein/python3-first.html).
== What we learned last week ==
As we worked on approving the changes to add the zuul settings to
a few Oslo repositories, we had trouble with some of t
101 - 200 of 3780 matches
Mail list logo
