settingsLogin | Registersettings

[openstack-dev] [pbr] Migration to Storyboard

0 votes

The Python packaging ecosystem is shifting under our feet and we have a couple
of things in pbr we need to look at over the next few months (Pipfiles, pyenv,
changes in setuptools setup.cfg, ...). We should probably track these somewhere
and Storyboard [1] seems like a better candidate for doing this than Launchpad
(plus, I get to play with Storyboard).

I can initiate the transfer (it seems pretty easy to do [2]) but I'd like to
make sure there are no objections before doing so.

Speak now or forever hold your tongue.

Stephen

[1] https://docs.openstack.org/infra/storyboard/
[2] https://docs.openstack.org/infra/storyboard/migration.html


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
asked Oct 11, 2017 in openstack-dev by Stephen_Finucane (1,620 points)   2

6 Responses

0 votes

Excerpts from Stephen Finucane's message of 2017-10-11 15:05:50 +0100:

The Python packaging ecosystem is shifting under our feet and we have a couple
of things in pbr we need to look at over the next few months (Pipfiles, pyenv,
changes in setuptools setup.cfg, ...). We should probably track these somewhere
and Storyboard [1] seems like a better candidate for doing this than Launchpad
(plus, I get to play with Storyboard).

I can initiate the transfer (it seems pretty easy to do [2]) but I'd like to
make sure there are no objections before doing so.

Speak now or forever hold your tongue.

Stephen

[1] https://docs.openstack.org/infra/storyboard/
[2] https://docs.openstack.org/infra/storyboard/migration.html

We have a bunch of open bugs. It would be good to triage those to see
which, if any, need to be migrated.

Otherwise I'm +1.

Doug


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Oct 11, 2017 by Doug_Hellmann (87,520 points)   3 4 8
0 votes

Sounds like a plan to me.

On 10/11/2017 10:05 AM, Stephen Finucane wrote:
The Python packaging ecosystem is shifting under our feet and we have a couple
of things in pbr we need to look at over the next few months (Pipfiles, pyenv,
changes in setuptools setup.cfg, ...). We should probably track these somewhere
and Storyboard [1] seems like a better candidate for doing this than Launchpad
(plus, I get to play with Storyboard).

I can initiate the transfer (it seems pretty easy to do [2]) but I'd like to
make sure there are no objections before doing so.

Speak now or forever hold your tongue.

Stephen

[1] https://docs.openstack.org/infra/storyboard/
[2] https://docs.openstack.org/infra/storyboard/migration.html


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Oct 11, 2017 by Jay_Pipes (59,760 points)   3 10 14
0 votes

+1

On Wed, Oct 11, 2017 at 12:05 PM, Doug Hellmann doug@doughellmann.com wrote:
Excerpts from Stephen Finucane's message of 2017-10-11 15:05:50 +0100:

The Python packaging ecosystem is shifting under our feet and we have a couple
of things in pbr we need to look at over the next few months (Pipfiles, pyenv,
changes in setuptools setup.cfg, ...). We should probably track these somewhere
and Storyboard [1] seems like a better candidate for doing this than Launchpad
(plus, I get to play with Storyboard).

I can initiate the transfer (it seems pretty easy to do [2]) but I'd like to
make sure there are no objections before doing so.

Speak now or forever hold your tongue.

Stephen

[1] https://docs.openstack.org/infra/storyboard/
[2] https://docs.openstack.org/infra/storyboard/migration.html

We have a bunch of open bugs. It would be good to triage those to see
which, if any, need to be migrated.

Otherwise I'm +1.

Doug


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

--
Davanum Srinivas :: https://twitter.com/dims


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Oct 11, 2017 by Davanum_Srinivas (35,920 points)   2 4 7
0 votes

On 2017-10-11 12:05:33 -0400 (-0400), Doug Hellmann wrote:
[...]
We have a bunch of open bugs. It would be good to triage those to see
which, if any, need to be migrated.
[...]

Well, they'll all be migrated (whether open or closed), but closing
them in LP where possible will reduce the risk that people continue
trying to update them there later.

Unfortunately the degree to which bug handling can be disabled in LP
is somewhat lacking if you want to still have old bugs archived
there (so that existing links on mailing lists and such continue
working). You can disable reporting new bugs and hide links to the
bug tracker from the project page on LP, but bugs can still get
updated there. We've talked about the possibility for a bug-spammer
that adds a comment to and closes all LP bugs on a project pointing
to the corresponding URLs of imported SB stories. However, as you
know, dealing with API timeouts for LP is sort of un-fun so this
may be a foolish idea.
--
Jeremy Stanley


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

responded Oct 11, 2017 by Jeremy_Stanley (56,700 points)   3 5 7
0 votes

Excerpts from Jeremy Stanley's message of 2017-10-11 16:29:31 +0000:

On 2017-10-11 12:05:33 -0400 (-0400), Doug Hellmann wrote:
[...]

We have a bunch of open bugs. It would be good to triage those to see
which, if any, need to be migrated.
[...]

Well, they'll all be migrated (whether open or closed), but closing
them in LP where possible will reduce the risk that people continue
trying to update them there later.

Oh, nice, I didn't realize all of the bugs would be copied over.
Triaging will still help clean up the active items, but I don't think
it's a blocker.

Unfortunately the degree to which bug handling can be disabled in LP
is somewhat lacking if you want to still have old bugs archived
there (so that existing links on mailing lists and such continue
working). You can disable reporting new bugs and hide links to the
bug tracker from the project page on LP, but bugs can still get
updated there. We've talked about the possibility for a bug-spammer
that adds a comment to and closes all LP bugs on a project pointing
to the corresponding URLs of imported SB stories. However, as you
know, dealing with API timeouts for LP is sort of un-fun so this
may be a foolish idea.

Commenting on bugs seems to trigger the timeout less often than
trying to update some of the metadata. At least that's what I think
we've found with the release tools. It's also safe to ignore the
timeout errors in this case, I think.

On the other hand, I think just closing down the tracker is probably
sufficient. It's not like we have lots of people commenting on pbr bugs
right now.

Doug


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Oct 11, 2017 by Doug_Hellmann (87,520 points)   3 4 8
0 votes

Glad to see this conversation rolling and fully supported :) If there is
anything we can do to help please feel free to bother us in the #storyboard
channel and we will do what we can.

Also, thanks for the webclient patches :)

-Kendall (diablo_rojo)

On Wed, Oct 11, 2017 at 7:06 AM Stephen Finucane sfinucan@redhat.com
wrote:

The Python packaging ecosystem is shifting under our feet and we have a
couple
of things in pbr we need to look at over the next few months (Pipfiles,
pyenv,
changes in setuptools setup.cfg, ...). We should probably track these
somewhere
and Storyboard [1] seems like a better candidate for doing this than
Launchpad
(plus, I get to play with Storyboard).

I can initiate the transfer (it seems pretty easy to do [2]) but I'd like
to
make sure there are no objections before doing so.

Speak now or forever hold your tongue.

Stephen

[1] https://docs.openstack.org/infra/storyboard/
[2] https://docs.openstack.org/infra/storyboard/migration.html


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Oct 11, 2017 by Kendall_Nelson (3,720 points)   1 2 3
...