Hi folks,
With the move to a PR based workflow, I've been finding "make patchcheck"
less helpful than it used to be, as it was only checking the changes that
had yet to be committed at all, and ignoring those that had already been
checked in on the PR branch.
I've put together a proposed update t
On 26 February 2017 at 05:57, INADA Naoki wrote:
> Yes, right place to discussion is one of important things what I want.
> I haven't know about i18n-sig. Is it better than docs-sig?
>
>
> Another thing I want is agreement to use project name looks like
> (semi)official project.
>
> We used "pyt
tools, projects, changelog filenames
x-posting from
https://github.com/python/core-workflow/issues/6#issuecomment-282529194 :
...
changelog filenames
- CHANGELOG.rst
- HISTORY.rst
- whatsnew.rst
- Misc/NEWS
### ``Escaping M``arkup
NOTE: commit logs may contain (executable) markup
- **https:/
On Wed, 22 Feb 2017 at 13:30 Ned Deily wrote:
> On Feb 22, 2017, at 07:27, Victor Stinner
> wrote:
>
> > [...]My idea is not new, it's already discussed in the Python
> core-workflow:
> > https://github.com/python/core-workflow/issues/6
> >
> > I'm opening a thread on python-dev because Misc/NEW
On Feb 24, 2017, at 11:40 PM, Larry Hastings wrote:
>I'm for it too. Fixing up Misc/NEWS is probably the trickiest and most
>error-prone part of cutting a release.
Not to mention cherry picking for older releases.
>While I'm sure we can learn a lot by examining "reno", my suspicion is we'll
>wa
Yes, right place to discussion is one of important things what I want.
I haven't know about i18n-sig. Is it better than docs-sig?
Another thing I want is agreement to use project name looks like
(semi)official project.
We used "python-doc-jp" name on Transifex at first. But since some people
o
On Feb 25, 2017, at 13:19, Brett Cannon wrote:
> It's getting a little hard to tease out what exactly is being asked at this
> point. Perhaps it's time to move the discussion over to a translation SIG
> (which probably needs to be created unless the old
> https://mail.python.org/mailman/listinf
On Fri, 24 Feb 2017 at 03:50 INADA Naoki wrote:
> > Where should these translated docs live and how does one make it clear to
> > users reading them that doc bugs shouldn't be submitted to the main bug
> > tracker/github repo?
> >
>
> We setup github page. See https://python-doc-ja.github.io/py3
For the discussion about translating Python documentation I have
collected some statistics. See the attachment.
The difference of the documentation between recent feature releases is
only 5-7%. Early bugfix releases change about 1-2% of the documentation.
The tutorial is more stable. There is
