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.
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 r
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/pep
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/
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 se
> 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
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/m
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 un
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
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 i
10 matches
Mail list logo
