MEP Process - matplotlib-devel - Matplotlib
MEP Process Development matplotlib-devel juichenieder-nabb September 10, 2015, 1:03pm 1 Hi Matplotlibers, Now that we have moved over to MEPs as pull requests (which I love), we now need to decide how to "track" these PRs. As far as I see it, we have two options. 1. Keep the wiki, but use it as a stub to track the PR(s). 2. Create a script for Travis that auto-numbers MEPs (and renames the filename of the MEP accordingly?) once an MEP has been merged into master.
What do people think? Best, OceanWolf njs September 10, 2015, 11:18pm 2 I believe that what Python does for PEPs is just, when the first draft is written you assign the number, and if it ends up being rejected or whatever, then oh well, now that's the number for a rejected PEP. They just have to be unique, it doesn't matter whether they're strictly in order by acceptance date or anything like that. ··· On Thu, Sep 10, 2015 at 6:03 AM, OceanWolf <juichenieder-nabb at yahoo.co.uk> wrote: Hi Matplotlibers, Now that we have moved over to MEPs as pull requests (which I love), we now need to decide how to "track" these PRs.
As far as I see it, we have two options. 1. Keep the wiki, but use it as a stub to track the PR(s). 2. Create a script for Travis that auto-numbers MEPs (and renames the filename of the MEP accordingly?) once an MEP has been merged into master. What do people think? Best, OceanWolf _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel at python.org Matplotlib-devel Info Page -- Nathaniel J.
Smith -- http://vorpus.org juichenieder-nabb September 10, 2015, 11:58pm 3 Okay, that suggests the option 1 approach, as that way we can easily see which numbers we have already allocated, and allows us to easily keep track of MEP numbers while they still exist only in PR form. I just want to avoid numbering clashes later. If we agree on this, I can go through the wiki and get rid of the MEP specific pages there, replacing them with a list there, something like: MEP xx <short description> *Discussion*: <Link to PR> MEP xx <short description> *Progress* <Link to main site (falling back to te file on github if not updated yet)> ··· On 11/09/15 01:18, Nathaniel Smith wrote: I believe that what Python does for PEPs is just, when the first draft is written you assign the number, and if it ends up being rejected or whatever, then oh well, now that's the number for a rejected PEP.
They just have to be unique, it doesn't matter whether they're strictly in order by acceptance date or anything like that. On Thu, Sep 10, 2015 at 6:03 AM, OceanWolf > <juichenieder-nabb at yahoo.co.uk> wrote: Hi Matplotlibers, Now that we have moved over to MEPs as pull requests (which I love), we now need to decide how to "track" these PRs. As far as I see it, we have two options. 1. Keep the wiki, but use it as a stub to track the PR(s).
2. Create a script for Travis that auto-numbers MEPs (and renames the filename of the MEP accordingly?) once an MEP has been merged into master. What do people think? Best, OceanWolf _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel at python.org Matplotlib-devel Info Page tacaswell September 12, 2015, 6:56pm 4 I think we should get rid of the wiki-based MEPs all together, it is just one more place that data can get out of sync.
Ideally we make sure that MEPs are merged promptly and worst case changing the number of a MEP before it's PR is merged is an acceptable fallback. Tom ··· On Thu, Sep 10, 2015 at 8:00 PM OceanWolf <juichenieder-nabb at yahoo.co.uk> wrote: Okay, that suggests the option 1 approach, as that way we can easily see which numbers we have already allocated, and allows us to easily keep track of MEP numbers while they still exist only in PR form.
I just want to avoid numbering clashes later. If we agree on this, I can go through the wiki and get rid of the MEP specific pages there, replacing them with a list there, something like: MEP xx <short description> *Discussion*: <Link to PR> MEP xx <short description> *Progress* <Link to main site (falling back to te file on github if not updated yet)> On 11/09/15 01:18, Nathaniel Smith wrote: > I believe that what Python does for PEPs is just, when the first draft > is written you assign the number, and if it ends up being rejected or > whatever, then oh well, now that's the number for a rejected PEP.
They > just have to be unique, it doesn't matter whether they're strictly in > order by acceptance date or anything like that. > > On Thu, Sep 10, 2015 at 6:03 AM, OceanWolf > > <juichenieder-nabb at yahoo.co.uk> wrote: >> Hi Matplotlibers, >> Now that we have moved over to MEPs as pull requests (which I love), we now >> need to decide how to "track" these PRs. >> >> As far as I see it, we have two options. >> 1. Keep the wiki, but use it as a stub to track the PR(s). >> 2.
Create a script for Travis that auto-numbers MEPs (and renames the >> filename of the MEP accordingly?) once an MEP has been merged into master. >> >> What do people think? >> >> Best, >> OceanWolf >> _______________________________________________ >> Matplotlib-devel mailing list >> Matplotlib-devel at python.org >> Matplotlib-devel Info Page > > _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel at python.org Matplotlib-devel Info Page -------------- next part -------------- An HTML attachment was scrubbed...
URL: < http://mail.python.org/pipermail/matplotlib-devel/attachments/20150912/a8c07479/attachment-0001.html> ;