[python-committers] Re: bedevere/issue-number and bedevere/news: waiting for status to be reported

[Eric V. Smith]

Thanks, Mariatta.

I just removed the "skip issue" tag, and presto: "All checks have 
passed". I'm not sure what's up, but at least I can merge this issue now.


Eric

On 12/19/2020 3:24 PM, Mariatta wrote:
I tried removing the labels and adding them back. I didn't see any 
error logged in heroku. The app is running, yet the webhooks appeared 
to be delivered successfully, returning 200 status.


Perhaps there's a problem from GitHub side.

I'm on my phone right now and not able to further investigate until 
later this evening.



On Sat., Dec. 19, 2020, 11:50 a.m. Eric V. Smith, > wrote:


I'm trying to merge this:
https://github.com/python/cpython/pull/23855


It says that it's waiting on bedevere/issue-number and
bedevere/news, with status "Waiting for status to be reported".
The PR is tagged with "skip issue" and "skip news" (even though it
has an issue). So I guess these are inspected by bedevere, which
isn't responding.

I've tried opening and closing the issue to re-trigger things, to
no avail.

What can I do to commit this PR? Does bedevere need to be kicked
into life somehow? Is anyone else seeing this problem?

Thanks.

Eric

___
python-committers mailing list -- python-committers@python.org

To unsubscribe send an email to python-committers-le...@python.org

https://mail.python.org/mailman3/lists/python-committers.python.org/

Message archived at

https://mail.python.org/archives/list/python-committers@python.org/message/4QD47S5OB4EVC6A2QTT7EH26EQBW4PGR/


Code of Conduct: https://www.python.org/psf/codeofconduct/


___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/L5FSQC4EEQ5LTLAWAZZ62GNT5US62HP3/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: Document the release process on devguide?

[Ned Deily]

On Dec 19, 2020, at 16:55, Guido van Rossum  wrote:
> I take it that PEP 101 is updated whenever the recipe changes in any way?

Yes, that’s the intent. And over the years, “the recipe” has become rather a 
multi-course banquet meal with all of the steps and systems now involved in 
putting out a release. 

I should point out that PEP 101 describes the mechanics of putting out a 
release. It is by no means a complete description of the role that a release 
manager plays in our development process. Perhaps a brief description could be 
written up and added to the devguide. That would be of much more value, I 
think. 
> 
>> On Sat, Dec 19, 2020 at 1:41 PM Ned Deily  wrote:
>> 
>> On Dec 19, 2020, at 14:57, joannah nanjekye  
>> wrote:
>> > I got to know from Pablo that the release process is documented in a PEP 
>> > here: https://www.python.org/dev/peps/pep-0101/
>> > 
>> > I wonder if it makes sense for us to formalize this process by documenting 
>> > it on devguide, and adding any extra/missing information?
>> 
>> PEP 101 is intended to be the primary documentation of the release process 
>> steps from the perspective of a release manager.  It is not aimed at any 
>> other audience.  There is release cycle information, aimed at developers, in 
>> various parts of the devguide.  It could certainly be improved.  Are there 
>> some things in particular of value to core developers that are missing or 
>> could use work there?
> 
  --
Ned Deily
n...@python.org -- []


___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/RNKQ375P2PZRXQ6R2ZKMW3IYL5TD4X6F/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: Document the release process on devguide?

[Guido van Rossum]

I take it that PEP 101 is updated whenever the recipe changes in any way?

On Sat, Dec 19, 2020 at 1:41 PM Ned Deily  wrote:

>
> On Dec 19, 2020, at 14:57, joannah nanjekye 
> wrote:
> > I got to know from Pablo that the release process is documented in a PEP
> here: https://www.python.org/dev/peps/pep-0101/
> >
> > I wonder if it makes sense for us to formalize this process by
> documenting it on devguide, and adding any extra/missing information?
>
> PEP 101 is intended to be the primary documentation of the release process
> steps from the perspective of a release manager.  It is not aimed at any
> other audience.  There is release cycle information, aimed at developers,
> in various parts of the devguide.  It could certainly be improved.  Are
> there some things in particular of value to core developers that are
> missing or could use work there?
>
> --
>   Ned Deily
>   n...@baybryj.net --  []
>
>
> ___
> python-committers mailing list -- python-committers@python.org
> To unsubscribe send an email to python-committers-le...@python.org
> https://mail.python.org/mailman3/lists/python-committers.python.org/
> Message archived at
> https://mail.python.org/archives/list/python-committers@python.org/message/BGNVTKM4YRHTOVRJEWZQ6DFZFGVORHF3/
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>


-- 
--Guido van Rossum (python.org/~guido)
*Pronouns: he/him **(why is my pronoun here?)*

___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/VOEA5QHBQ2YLV6IXWFHGTVEWX3ZOZAXO/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: Document the release process on devguide?

[Ned Deily]

On Dec 19, 2020, at 14:57, joannah nanjekye  wrote:
> I got to know from Pablo that the release process is documented in a PEP 
> here: https://www.python.org/dev/peps/pep-0101/
> 
> I wonder if it makes sense for us to formalize this process by documenting it 
> on devguide, and adding any extra/missing information?

PEP 101 is intended to be the primary documentation of the release process 
steps from the perspective of a release manager.  It is not aimed at any other 
audience.  There is release cycle information, aimed at developers, in various 
parts of the devguide.  It could certainly be improved.  Are there some things 
in particular of value to core developers that are missing or could use work 
there?

--
  Ned Deily
  n...@baybryj.net --  []




signature.asc
Description: Message signed with OpenPGP
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/BGNVTKM4YRHTOVRJEWZQ6DFZFGVORHF3/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: Document the release process on devguide?

[Ned Deily]

On Dec 19, 2020, at 16:26, joannah nanjekye  wrote:
> 
> > PEP 101 is intended to be the primary documentation of the release process 
> > steps from the perspective of a release manager. 
> 
> I think am talking about the documentation aimed at the release manager. And 
> yes whether it makes sense to move the details to devguide too.

The info in PEP 101 is very specialized and we have enough trouble keeping it 
up-to-date in one place :)  I don't see any value in trying to have it in two 
places. And I'm sure most people would find it tediously boring :) 

> Am assuming, that any core dev has the potential to be a release manager in 
> the future.

Perhaps we could add a few sentences to the devguide about the role of the 
release manager, with a link to PEP 101 for those interested in getting more of 
a feel for the mechanics (although that is about to change somewhat anyway 
thanks to Pablo's work at further automating the process), and with who to 
contact if one is interested in becoming a release manager for a future release 
(today, that would be the current and past release managers).

> On Sat, Dec 19, 2020 at 5:22 PM Ned Deily  wrote:
> On Dec 19, 2020, at 14:57, joannah nanjekye  wrote:
> > I got to know from Pablo that the release process is documented in a PEP 
> > here: https://www.python.org/dev/peps/pep-0101/
> > 
> > I wonder if it makes sense for us to formalize this process by documenting 
> > it on devguide, and adding any extra/missing information?
> 
> PEP 101 is intended to be the primary documentation of the release process 
> steps from the perspective of a release manager.  It is not aimed at any 
> other audience.  There is release cycle information, aimed at developers, in 
> various parts of the devguide.  It could certainly be improved.  Are there 
> some things in particular of value to core developers that are missing or 
> could use work there?
> 
> --
>   Ned Deily
>   n...@python.org -- []
> 
> 
> 
> -- 
> Best,
> Joannah Nanjekye
> "You think you know when you learn, are more sure when you can write, even 
> more when you can teach, but certain when you can program." 
> Alan J. Perlis

--
  Ned Deily
  n...@python.org -- []
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/PVIN6ISJ4AAGEQZBXPS7HLLDJQ6WVGBB/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: Document the release process on devguide?

[joannah nanjekye]

> PEP 101 is intended to be the primary documentation of the release
process steps from the perspective of a release manager.

I think am talking about the documentation aimed at the release manager.
And yes whether it makes sense to move the details to devguide too.

Am assuming, that any core dev has the potential to be a release manager in
the future.

On Sat, Dec 19, 2020 at 5:22 PM Ned Deily  wrote:

> On Dec 19, 2020, at 14:57, joannah nanjekye 
> wrote:
> > I got to know from Pablo that the release process is documented in a PEP
> here: https://www.python.org/dev/peps/pep-0101/
> >
> > I wonder if it makes sense for us to formalize this process by
> documenting it on devguide, and adding any extra/missing information?
>
> PEP 101 is intended to be the primary documentation of the release process
> steps from the perspective of a release manager.  It is not aimed at any
> other audience.  There is release cycle information, aimed at developers,
> in various parts of the devguide.  It could certainly be improved.  Are
> there some things in particular of value to core developers that are
> missing or could use work there?
>
> --
>   Ned Deily
>   n...@python.org -- []
>
>

-- 
Best,
Joannah Nanjekye

*"You think you know when you learn, are more sure when you can write, even
more when you can teach, but certain when you can program." Alan J. Perlis*
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/WBGSP5EG7WFQNXJEQG5MBH7LSHQPL76S/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: Document the release process on devguide?

[Ned Deily]

On Dec 19, 2020, at 14:57, joannah nanjekye  wrote:
> I got to know from Pablo that the release process is documented in a PEP 
> here: https://www.python.org/dev/peps/pep-0101/
> 
> I wonder if it makes sense for us to formalize this process by documenting it 
> on devguide, and adding any extra/missing information?

PEP 101 is intended to be the primary documentation of the release process 
steps from the perspective of a release manager.  It is not aimed at any other 
audience.  There is release cycle information, aimed at developers, in various 
parts of the devguide.  It could certainly be improved.  Are there some things 
in particular of value to core developers that are missing or could use work 
there?

--
  Ned Deily
  n...@python.org -- []
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/DRUJNTA5JVSDEDLW3X3TP5KUMVWOWXWU/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: bedevere/issue-number and bedevere/news: waiting for status to be reported

[Mariatta]

I tried removing the labels and adding them back. I didn't see any error
logged in heroku. The app is running, yet the webhooks appeared to be
delivered successfully, returning 200 status.

Perhaps there's a problem from GitHub side.

I'm on my phone right now and not able to further investigate until later
this evening.


On Sat., Dec. 19, 2020, 11:50 a.m. Eric V. Smith, 
wrote:

> I'm trying to merge this: https://github.com/python/cpython/pull/23855
>
> It says that it's waiting on bedevere/issue-number and bedevere/news, with
> status "Waiting for status to be reported". The PR is tagged with "skip
> issue" and "skip news" (even though it has an issue). So I guess these are
> inspected by bedevere, which isn't responding.
>
> I've tried opening and closing the issue to re-trigger things, to no avail.
>
> What can I do to commit this PR? Does bedevere need to be kicked into life
> somehow? Is anyone else seeing this problem?
>
> Thanks.
>
> Eric
> ___
> python-committers mailing list -- python-committers@python.org
> To unsubscribe send an email to python-committers-le...@python.org
> https://mail.python.org/mailman3/lists/python-committers.python.org/
> Message archived at
> https://mail.python.org/archives/list/python-committers@python.org/message/4QD47S5OB4EVC6A2QTT7EH26EQBW4PGR/
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/RXLEJSSRA6TB6JMIBO427DZVGP4LEMQR/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Document the release process on devguide?

[joannah nanjekye]

I got to know from Pablo that the release process is documented in a PEP
here: https://www.python.org/dev/peps/pep-0101/

I wonder if it makes sense for us to formalize this process by documenting
it on devguide, and adding any extra/missing information?

Happy to help.
-- 
Best,
Joannah Nanjekye

*"You think you know when you learn, are more sure when you can write, even
more when you can teach, but certain when you can program." Alan J. Perlis*
___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/C3FAFJPUZKLHQAAQRCSKRUYWW4EFKWXH/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] bedevere/issue-number and bedevere/news: waiting for status to be reported

[Eric V. Smith]

I'm trying to merge this: https://github.com/python/cpython/pull/23855

It says that it's waiting on bedevere/issue-number and bedevere/news, 
with status "Waiting for status to be reported". The PR is tagged with 
"skip issue" and "skip news" (even though it has an issue). So I guess 
these are inspected by bedevere, which isn't responding.


I've tried opening and closing the issue to re-trigger things, to no avail.

What can I do to commit this PR? Does bedevere need to be kicked into 
life somehow? Is anyone else seeing this problem?


Thanks.

Eric

___
python-committers mailing list -- python-committers@python.org
To unsubscribe send an email to python-committers-le...@python.org
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/python-committers@python.org/message/4QD47S5OB4EVC6A2QTT7EH26EQBW4PGR/
Code of Conduct: https://www.python.org/psf/codeofconduct/