Akihiro Motoki writes:
> Hi,
>
> Horizon logging depends on Django configuration which supports full python
> logging [1].
> [1] does not provide enough examples.
> Perhaps [2] will help you (though I haven't tested it).
Based on https://docs.djangoproject.com/en/2.1/topics/logging/ it looks
at sounds like a good
plan.
Thanks!
>
> Le 2018-11-07 18:43, Doug Hellmann a écrit :
>> Luka Peschke writes:
>>
>>> Hello,
>>>
>>> I'm making this e-mail to announce that the CloudKitty project will
>>> be
>>> holding IRC mee
Luka Peschke writes:
> Hello,
>
> I'm making this e-mail to announce that the CloudKitty project will be
> holding IRC meetings from now on. They will be held in the #cloudkitty
> channel on Freenode. They should (for now) be held on the first Friday
> of each month at 15h00 UTC. Of course,
Joshua Cornutt writes:
> On Wed, Nov 7, 2018 at 7:30 AM Doug Hellmann wrote:
>>
>> Joshua Cornutt writes:
>>
>> > Doug,
>> >
>> > I have such a list put together (my various installation documents for
>> > getting these clouds wo
Mohammed Naser writes:
> On Wed, Nov 7, 2018 at 2:07 PM Dr. Jens Harbott (frickler)
> wrote:
>>
>> 2018-11-07 12:47 GMT+00:00 Mohammed Naser :
>> > On Wed, Nov 7, 2018 at 1:37 PM Doug Hellmann wrote:
>> >>
>> >> Corey Bryant writes:
>>
Bernd Bausch writes:
> Thanks for educating me, Doug and Jeremy. Bug submitted.
>
> Just by the way: I checked [1] and [2] to find out where bugs might be
> tracked. The former doesn't mention bugs, the latter is outdated.
> Finding the way through the maze of OpenStack information is not always
Corey Bryant writes:
> On Wed, Oct 10, 2018 at 8:45 AM Corey Bryant
> wrote:
>
> I'd like to start moving forward with enabling py37 unit tests for a subset
> of projects. Rather than putting too much load on infra by enabling 3 x py3
> unit tests for every project, this would just focus on
Joshua Cornutt writes:
> Doug,
>
> I have such a list put together (my various installation documents for
> getting these clouds working in FIPS mode) but it's hardly ready for
> public consumption. I planned on releasing each bit as a code change
> and/or bug ticket and letting the community
Ghanshyam Mann writes:
> On Wed, 07 Nov 2018 06:51:32 +0900 Slawomir Kaplonski
> wrote
> > Hi,
> >
> > > Wiadomość napisana przez Jeremy Stanley w dniu
> 06.11.2018, o godz. 22:25:
> > >
> > > On 2018-11-06 22:05:49 +0100 (+0100), Slawek Kaplonski wrote:
> > > [...]
> >
Luke Hinds writes:
> On Tue, Nov 6, 2018 at 2:04 PM Julia Kreger
> wrote:
>
>>
>>
>> On Tue, Nov 6, 2018 at 5:07 AM Doug Hellmann
>> wrote:
>>
>>> Sean McGinnis writes:
>>>
>>> > I'm interested in some feedback from the
Bernd Bausch writes:
> Rocky Devstack sets up bash command completion for the openstack client,
> e.g. /openstack net[TAB]/ expands to /network/. Sadly, there is no
> command completion when using the client interactively:
>
> /$ openstack//
> //(openstack)
Sean McGinnis writes:
> I'm interested in some feedback from the community, particularly those running
> OpenStack deployments, as to whether FIPS compliance [0][1] is something folks
> are looking for.
>
> I've been seeing small changes starting to be proposed here and there for
> things like
Sean McGinnis writes:
> I'm interested in some feedback from the community, particularly those running
> OpenStack deployments, as to whether FIPS compliance [0][1] is something folks
> are looking for.
>
> I've been seeing small changes starting to be proposed here and there for
> things like
Matt Riedemann writes:
> On 11/5/2018 1:36 PM, Doug Hellmann wrote:
>> I think the lazy stuff was all about the API responses. The log
>> translations worked a completely different way.
>
> Yeah maybe. And if so, I came across this in one of the blueprints:
>
> https
Matt Riedemann writes:
> On 11/5/2018 1:36 PM, Doug Hellmann wrote:
>> I think the lazy stuff was all about the API responses. The log
>> translations worked a completely different way.
>
> Yeah maybe. And if so, I came across this in one of the blueprints:
>
> https
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:
TC members,
I have updated the liaison assignments to fill in all of the
gaps. Please take a moment to review the list [1] so you know your
assignments.
Next week will be a good opportunity to touch bases with your teams.
Doug
[1]
Matt Riedemann writes:
> This is a follow up to a dev ML email [1] where I noticed that some
> implementations of the upgrade-checkers goal were failing because some
> projects still use the oslo_i18n.enable_lazy() hook for lazy log message
> translation (and maybe API responses?).
>
> The
Matt Riedemann writes:
> This is a follow up to a dev ML email [1] where I noticed that some
> implementations of the upgrade-checkers goal were failing because some
> projects still use the oslo_i18n.enable_lazy() hook for lazy log message
> translation (and maybe API responses?).
>
> The
Doug Hellmann writes:
> Doug Hellmann writes:
>
> I asked the owners of the name "heat" to allow us to use it, and they
> rejected the request. So, I proposed a change to heat to update the
> sdist name to "openstack-heat".
>
> * https://review.openst
I have started a thread on the -dev list [1] to discuss the
community-wide goals for the T series, prior to the Forum session in
Berlin in a couple of weeks. Please join the conversation in that thread
if you have any input.
Thanks!
Doug
[1]
We will have a session at the forum to discuss the community-wide goals
[0] we want to select for the T cycle. That's a long way off, but given
the fact that we don't have a PTG between Berlin and Denver, and that
we've recently had feedback that we need to have tools finished better
before
Doug Hellmann writes:
> TC members,
>
> The TC will be meeting on 1 Nov at 1400 UTC in #openstack-tc to discuss
> some of our ongoing initiatives. Here is the agenda for this week.
>
> * meeting procedures
>
> * discussion of topics for joint leadership meeting
Jeremy Stanley writes:
> On 2018-11-01 08:52:05 -0400 (-0400), Doug Hellmann wrote:
> [...]
>> Did I miss any options or issues with this approach?
>
> https://review.openstack.org/578557
How high of a priority is rolling that feature out? It does seem to
eliminate this part
TC members,
I have a series of patches up for review starting at [1] to create a
small library for reading and manipulating the project reference data in
the YAML files in the openstack/governance repository. After copying
similar code into a 3rd repository that wants to consume it last cycle,
I
Doug Hellmann writes:
> z...@openstack.org writes:
>
>> Build failed.
>>
>> - publish-openstack-releasenotes-python3
>> http://logs.openstack.org/86/86022835fb39cb318e28994ed0290caddfb451be/tag/publish-openstack-releasenotes-python3/7347218/
>> : POST_FAILU
z...@openstack.org writes:
> Build failed.
>
> - publish-openstack-releasenotes-python3
> http://logs.openstack.org/86/86022835fb39cb318e28994ed0290caddfb451be/tag/publish-openstack-releasenotes-python3/7347218/
> : POST_FAILURE in 13m 53s
> - publish-openstack-releasenotes
>
| Champion |
+-+--+-+--+-++---++
| adjutant| 1/ 1 | - | +| 0 |
1 | 2 | Doug Hellmann |
| barbican| +| 1/ 3 | +| 1 |
1 | 7 | Dou
Alex Schultz writes:
> Hey everyone,
>
> Based on previous emails around this[0][1], I have proposed a possible
> reducing in our usage by switching the scenario001--011 jobs to
> non-voting and removing them from the gate[2]. This will reduce the
> likelihood of causing gate resets and
TC members,
The TC will be meeting on 1 Nov at 1400 UTC in #openstack-tc to discuss
some of our ongoing initiatives. Here is the agenda for this week.
* meeting procedures
* discussion of topics for joint leadership meeting at Summit in
Berlin
* completing TC liaison assignments
**
"Ian Y. Choi" writes:
> Hello,
>
> I got involved organizing & mentoring Korean people for OpenStack
> upstream contribution for about last two months,
> and would like to share with community members.
>
> Total nine mentees had started to learn OpenStack, contributed, and
> finally survived
Zane Bitter writes:
> On 19/10/18 11:17 AM, Zane Bitter wrote:
>> I'd like to propose that we handle this by setting up a unit test
>> template in openstack-zuul-jobs for each release. So for Stein we'd have
>> openstack-python3-stein-jobs. This template would contain:
>>
>> * A voting gate
Earlier today I learned that we have a few repositories with linter jobs
failing (or at least reporting warnings) because they are running
"python setup.py check" to test that the packaging meta-data is OK.
This method of testing has been deprecated in favor of using the command
"twine check",
AKHIL Jain writes:
> Hi Matt and Telemetry Team,
>
> I was going through the remaining project to be implemented with
> upgrade-checkers placeholder framework. I would like to know about the
> projects to implement the same under telemetry tab.
>
> According to my understanding from below
Monty Taylor writes:
> On 10/29/18 10:47 AM, Doug Hellmann wrote:
>> Monty Taylor writes:
>>
>>> Heya,
>>>
>>> Tobias and I were chatting at OpenStack Days Nordic about the Public
>>> Cloud Working Group potentially taking over as custodians o
Monty Taylor writes:
> Heya,
>
> Tobias and I were chatting at OpenStack Days Nordic about the Public
> Cloud Working Group potentially taking over as custodians of the vendor
> profile information [0][1] we keep in openstacksdk (and previously in
> os-client-config)
>
> I think this is a
Sean McGinnis writes:
> During the Stein PTG in Denver, the release management team talked about ways
> we can make things simpler and reduce the "paper pushing" work that all teams
> need to do right now. One topic that came up was the usefulness of pushing
> tags
> around milestones during
1 | 2 | Doug Hellmann |
| barbican| +| 1/ 3 | +| 1 |
1 | 7 | Doug Hellmann |
| blazar | +| + | +| 0 |
0 | 9 | Nguyen Hai |
| Chef
k to them about the
current status.
Doug
>
> Bests,
>
> On Fri, Oct 12, 2018 at 6:50 AM Doug Hellmann wrote:
>
>> Doug Hellmann writes:
>>
>> > TC members,
>> >
>> > Since we are starting a new term, and have several new members, we need
&
Doug Hellmann writes:
> TC members,
>
> Since we are starting a new term, and have several new members, we need
> to decide how we want to rotate the liaisons attached to each our
> project teams, SIGs, and working groups [1].
>
> Last term we went through a period
Doug Hellmann writes:
> We have about 17 remaining patches to import zuul job settings into a
> few repositories. Those are mostly in stable branches and the jobs are
> failing in ways that may take us a long time to fix.
>
> Rather than waiting for those, Andreas and I are pr
Ken Giusti writes:
> On Tue, Oct 9, 2018 at 11:56 AM Doug Hellmann wrote:
>
>> Matthew Thode writes:
>>
>> > On 18-10-09 11:12:30, Doug Hellmann wrote:
>> >> Matthew Thode writes:
>> >>
>> >> > several projects have had p
Matthew Thode writes:
> On 18-10-09 11:12:30, Doug Hellmann wrote:
>> Matthew Thode writes:
>>
>> > several projects have had problems with the new release, some have ways
>> > of working around it, and some do not. I'm sending this just to raise
>> &
Ben Nemec writes:
> On 10/9/18 10:19 AM, Doug Hellmann wrote:
>> Brian Rosmaita writes:
>>
>>> On 10/8/18 11:59 PM, Matthew Thode wrote:
>>>> several projects have had problems with the new release, some have ways
>>>> of working around it,
Lance Bragstad writes:
> Keystone is failing because it's missing a fix from oslo.messaging [0].
> That said, keystone is also relying on an internal implementation detail in
> oslo.messaging by mocking it in tests [1]. The notification work has been
> around in keystone for a *long* time, but
Brian Rosmaita writes:
> On 10/8/18 11:59 PM, Matthew Thode wrote:
>> several projects have had problems with the new release, some have ways
>> of working around it, and some do not. I'm sending this just to raise
>> the issue and allow a place to discuss solutions.
>>
>> Currently there is a
Matthew Thode writes:
> several projects have had problems with the new release, some have ways
> of working around it, and some do not. I'm sending this just to raise
> the issue and allow a place to discuss solutions.
>
> Currently there is a review proposed to blacklist 9.0.0, but if this is
Anne Bertucio writes:
> Hi all,
>
> I have had a fantastic time getting to work on the Release Management
> team and getting to know you all through the release marketing work,
> however, it is time for me to step down from my role on the Release
> Management team as I am moving on from my role
Doug Hellmann writes:
> Doug Hellmann writes:
>
>> Doug Hellmann writes:
>>
>>> Doug Hellmann writes:
>>
>>> I have filed requests with the maintainers of PyPI to claim the names
>>> "keystone" and "congress". That may
Sean McGinnis writes:
[snip]
> The only problem we've seen is without the milestone releases during the
> cycle,
> there is quite a gap before the version numbers get incremented for anyone
> doing more frequent testing. We wanted to reach out the operator community
> since I know there are at
y if your tests are running in the unit
test jobs. If you're running a functional test, it seems like it would
also be OK to just copy a file into the directory Apache is serving from
and then download it from there.
Doug
>
> Thanks & Best Regards,
>
> Abhishek Kekane
>
>
|
+--+-+---++--+-+---+---+
| import zuul job settings from project-config | openstack/aodh
| Telemetry | FAILED | NEW | https://review.openstack.org/598648 |
stable/ocata | Doug Hellmann |
| import zuul job settings from project-config | openstack/barbican
| barbican
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:
TC members,
Since we are starting a new term, and have several new members, we need
to decide how we want to rotate the liaisons attached to each our
project teams, SIGs, and working groups [1].
Last term we went through a period of volunteer sign-up and then I
randomly assigned folks to slots
TC members,
I have some PTO planned, so I will be away from 13 Oct - 28 Oct. I
approved the patch appointing Mohammed as vice chair this morning, so he
will be serving as chair during that time.
Doug
__
OpenStack
Based on the conversation in the other branch of this thread, I have
filed [1] to start monthly meetings on November 1 at 1400 UTC. It may
take a while before that actually shows up on the calendar, because it
required adding a feature to yaml2ical [2].
We talked about using email to add items to
Doug Hellmann writes:
> Doug Hellmann writes:
>
>> Doug Hellmann writes:
>>
>>> I think we are ready to go ahead and switch all of the python packaging
>>> jobs to the new set defined in the publish-to-pypi-python3 template
>>> [1]. We still hav
Doug Hellmann writes:
> Doug Hellmann writes:
>
>> I think we are ready to go ahead and switch all of the python packaging
>> jobs to the new set defined in the publish-to-pypi-python3 template
>> [1]. We still have some cleanup patches for projects that have not
Watch for changes in pip's behavior. - Doug
Pradyun Gedam writes:
> On behalf of the PyPA, I am pleased to announce that pip 18.1 has just
> been released.
>
> To install pip 18.1, you can run::
>
> python -m pip install --upgrade pip
>
> or use get-pip as described in
>
Trinh Nguyen writes:
> Dear release team,
>
> One thing comes up in my mind when preparing for the stein-1 release of
> Searchlight that is what should we do with the missing releases (i.e.
> Rocky)? Can I just ignore it or do I have to create a branch for it?
There was no rocky release, so I
Chris Dent writes:
> On Thu, 4 Oct 2018, Doug Hellmann wrote:
>
>> TC members, please reply to this thread and indicate if you would find
>> meeting at 1300 UTC on the first Thursday of every month acceptable, and
>> of course include any other comments you might h
Thierry Carrez writes:
> Ghanshyam Mann wrote:
>> On Fri, 05 Oct 2018 02:47:53 +0900 Jeremy Stanley
>> wrote
>> > On 2018-10-04 13:40:05 -0400 (-0400), Doug Hellmann wrote:
>> > [...]
>> > > TC members, please reply to this t
Gilles Dubreuil writes:
>> About the micro version, we discuss with your team mate dmitry in
>> another email [1]
>
> Obviously micro version is a point of contention.
> My take on this is because consuming them has been proven harder than
> developing them.
> The beauty of GraphQL is that
Abhishek Kekane writes:
> Hi Matt,
>
> Thanks for the input, I guess I should use '
> http://git.openstack.org/static/openstack.png' which will definitely work.
> Clark, Matt, Kindly let me know your opinion about the same.
That URL would not be on the local node running the test, and would
Trinh Nguyen writes:
> Thank Jeremy, Doug for explaining.
>
> On Fri, Oct 5, 2018 at 6:54 AM Doug Hellmann wrote:
>
>> Jeremy Stanley writes:
>>
>> > On 2018-10-04 23:11:22 +0900 (+0900), Trinh Nguyen wrote:
>> > [...]
>> >> Please
Jeremy Stanley writes:
> On 2018-10-04 17:57:06 -0400 (-0400), Doug Hellmann wrote:
> [...]
>> HTTPError: 400 Client Error: Invalid value for classifiers. Error:
>> 'Topic:: Utilities' is not a valid choice for this field for url:
>> https://upload.pypi.org/lega
Stephen Finucane writes:
> On Thu, 2018-10-04 at 07:21 -0400, Doug Hellmann wrote:
>> Stephen Finucane writes:
[snip]
>> > Anyway, we can go figure out what's changed here and handle it but this
>> > is, at best, going to be a band aid. The fact is 'sphinx_te
z...@openstack.org writes:
> Build failed.
>
> - release-openstack-python
> http://logs.openstack.org/b4/b4553baa59b1f13a57973f2a3cff9b57acf3d522/release/release-openstack-python/68d0da8/
> : POST_FAILURE in 5m 19s
> - announce-release announce-release : SKIPPED
> - propose-update-constraints
Jeremy Stanley writes:
> On 2018-10-04 23:11:22 +0900 (+0900), Trinh Nguyen wrote:
> [...]
>> Please avoid adding universal wheels to the project setup.cfg.
> [...]
>
> Why would you avoid also adding it to the setup.cfg? The change you
> cited is merely to be able to continue building universal
During the TC office hours today [1] we discussed the question of
resuming having formal meetings of the TC to ensure we are in compliance
with the section of the bylaws that says "The Technical Committee shall
meet at least quarterly." [2] As not all TC members were present today,
we decide to
Stephen Finucane writes:
> The tests in os-api-ref recently broke:
>
>
> http://logs.openstack.org/62/606362/1/check/openstack-tox-py35/8b709de/testr_results.html.gz
>
> Specifically, we're seeing errors likes this:
>
> ft1.1:
>
Doug Hellmann writes:
> Doug Hellmann writes:
>
>> Doug Hellmann writes:
>>
>>> == Things We Learned This Week ==
>>>
>>> When we updated the tox.ini settings for jobs like pep8 and release
>>> notes early in the Rocky session we on
We have 7 teams still working on the zuul setting migrations as part of
the python3-first goal [1].
Quite a few of the changes are on stable branches, so will need
attention from the stable teams for each project. If you need help
reviewing those stable branch patches, please speak up so we can
AdityaVaja writes:
> Hello Doug,
>
> I was going to send out an email or drop in on IRC to check how to fix that.
>
> We accidentally pushed 13.0.1 on stable/queens, instead of 12.0.5. (13.x.x
> is rocky and 12.x.x is queens)
> Tried reverting the situation by pushing 12.0.5 for the same commit
Wesley Hayutin writes:
[snip]
> The TripleO project has created a single node container based composable
> OpenStack deployment [2]. It is the projects intention to replace most of
> the TripleO upstream jobs with the Standalone deployment. We would like to
> reduce our multi-node usage to a
Zane Bitter writes:
> On 3/10/18 9:42 AM, Matt Riedemann wrote:
>> On 10/3/2018 7:58 AM, Doug Hellmann wrote:
>>> There is one more patch to import the zuul configuration for the
>>> heat-agents repository's stable/ocata branch. That branch is apparently
>
z...@openstack.org writes:
> Build failed.
>
> - release-openstack-python
> http://logs.openstack.org/d1/d1df2f75e0e8259ddaaf5136f421567733ba7f5b/release/release-openstack-python/8a89663/
> : FAILURE in 6m 19s
> - announce-release announce-release : SKIPPED
> - propose-update-constraints
There is one more patch to import the zuul configuration for the
heat-agents repository's stable/ocata branch. That branch is apparently
broken, and Zane suggested on the review [1] that we abandon the patch
and close the branch.
That patch is the only thing blocking the cleanup patch in
| Champion |
+-+-+--+-+--+-++---++
| adjutant| + | 1/ 1 | - | +
| 0 | 1 | 6 | Doug Hellmann |
| barbican| 7/ 13 | +| 1/ 3 | +
| 6 | 4 | 20 | Doug Hellmann
Miguel Angel Ajo Pelayo writes:
> Thank you for the guidance and ping Doug.
>
> Was this triggered by [1] ? or By the 1.1.0 tag pushed to gerrit?
The release jobs are always triggered by the git tagging event. The
patches in openstack/releases run a job that adds tags, but the patch
you linked
Dariusz Krol writes:
> Hello Doug,
>
> thanks for your explanation. I was a little bit confused by changes to
> stable branches with python3-first topic as I thought it has to do
> something with adding new test configuration for python3.
>
> But as you explained this is about moving
Doug Hellmann writes:
> Doug Hellmann writes:
>
>> == Things We Learned This Week ==
>>
>> When we updated the tox.ini settings for jobs like pep8 and release
>> notes early in the Rocky session we only touched some of the official
>> repositories. I'll be
Jeremy Stanley writes:
> On 2018-09-28 13:58:52 -0400 (-0400), William M Edmonds wrote:
>> Doug Hellmann wrote on 09/26/2018 06:29:11 PM:
>>
>> > * We do not want to set the override once in testenv, because that
>> > breaks the more specific versions
Doug Hellmann writes:
> I think we are ready to go ahead and switch all of the python packaging
> jobs to the new set defined in the publish-to-pypi-python3 template
> [1]. We still have some cleanup patches for projects that have not
> completed their zuul migration, but there ar
ches to the stable branch. See
http://lists.openstack.org/pipermail/openstack-dev/2018-August/133594.html
for details.
Doug
> I hope this helps.
>
>
> Best,
>
> Dariusz Krol
>
>
> On 09/27/2018 06:04 PM, Ben Nemec wrote:
>>
>>
>> On 9/27/18 10:36 AM
z...@openstack.org writes:
> Build failed.
>
> - release-openstack-python
> http://logs.openstack.org/d4/d445ff62676bc5b2753fba132a3894731a289fb9/release/release-openstack-python/629c35f/
> : FAILURE in 3m 57s
> - announce-release announce-release : SKIPPED
> - propose-update-constraints
Emmet Hikory writes:
> Please join me in congratulating the 6 newly elected members of the
> Technical Committee (TC):
>
> - Doug Hellmann (dhellmann)
> - Julia Kreger (TheJulia)
> - Jeremy Stanley (fungi)
> - Jean-Philippe Evrard (evrardjp)
> - L
writes:
> How will we handle which versions of libraries work together?
> And which combinations will be run thru CI?
Dependency management will work the same way it does today.
Each component (server or library) lists the versions of the
dependencies it is compatible with. That information
Dariusz Krol writes:
> Hello Champions :)
>
>
> I work on the Trove project and we are wondering if python3 should be
> supported in previous releases as well?
>
> Actually this question was asked by Alan Pevec from the stable branch
> maintainers list.
>
> I saw you added releases up to ocata
I think we are ready to go ahead and switch all of the python packaging
jobs to the new set defined in the publish-to-pypi-python3 template
[1]. We still have some cleanup patches for projects that have not
completed their zuul migration, but there are only a few and rebasing
those will be easy
Monty Taylor writes:
> Main difference is making sure these new deconstructed plugin teams
> understand the client support lifecycle - which is that we don't drop
> support for old versions of services in OSC (or SDK). It's a shift from
> the support lifecycle and POV of python-*client, but
Dean Troyer writes:
> On Wed, Sep 26, 2018 at 3:44 PM, Matt Riedemann wrote:
>> I started documenting the compute API gaps in OSC last release [1]. It's a
>> big gap and needs a lot of work, even for existing CLIs (the cold/live
>> migration CLIs in OSC are a mess, and you can't even boot from
Dean Troyer writes:
> On Wed, Sep 26, 2018 at 3:44 PM, Matt Riedemann wrote:
>> I started documenting the compute API gaps in OSC last release [1]. It's a
>> big gap and needs a lot of work, even for existing CLIs (the cold/live
>> migration CLIs in OSC are a mess, and you can't even boot from
Doug Hellmann writes:
> == Things We Learned This Week ==
>
> When we updated the tox.ini settings for jobs like pep8 and release
> notes early in the Rocky session we only touched some of the official
> repositories. I'll be working on making a list of the ones we missed so
>
hesitant to add those to
OSC in the past, but I can see the value. I wonder if having them in a
separate library makes sense? Or is it better to have commands in the
tool that regular users can't access, and just report the permission
error when they try to run the command?
Doug
>
>> ---
Ben Nemec writes:
> Okay, I found a few bugs that are in launchpad but not storyboard:
>
> https://bugs.launchpad.net/python-stevedore/+bug/1784823
> https://bugs.launchpad.net/pbr/+bug/1777625
> https://bugs.launchpad.net/taskflow/+bug/1756520
> https://bugs.launchpad.net/pbr/+bug/1742809
>
>
Jeremy Stanley writes:
> On 2018-09-26 09:22:30 -0500 (-0500), Sean McGinnis wrote:
> [...]
>> It tests the release automation machinery to identify problems
>> before the RC and final release crunch time.
> [...]
>
> More to the point, it helped spot changes to projects which made it
>
It's time to start thinking about community-wide goals for the T series.
We use community-wide goals to achieve visible common changes, push for
basic levels of consistency and user experience, and efficiently improve
certain areas where technical debt payments have become too high -
across all
It's time to start thinking about community-wide goals for the T series.
We use community-wide goals to achieve visible common changes, push for
basic levels of consistency and user experience, and efficiently improve
certain areas where technical debt payments have become too high -
across all
| Champion |
+-+-+--+-+--+-++---++
| adjutant| + | -| - | +| 0 |
0 | 5 | Doug Hellmann |
| barbican| 11/ 13 | +| 1/ 3 | +| 6 |
4 | 20 | Dou
1 - 100 of 3451 matches
Mail list logo
