[core-workflow] Longer term idea: consider Rust's homu for CPython merge gating

[Brett Cannon]

Larry Hastings also wrote one that's attached to the issue regarding fixing
the NEWS merge problem.

On Thu, 31 Dec 2015, 20:47 Nick Coghlan <ncoghlan at gmail.com> wrote:

> On 1 January 2016 at 06:21, Brett Cannon <brett at python.org> wrote:
> > Thanks for the link! For those that didn't look at the link, Homu is
> > actually written in Python and not Rust (the website for the project is
> > what's written in Rust).
> >
> > Berker has actually said he is beginning to look into writing a bot for
> our
> > needs so he might be interested in this.
> >
> > A quick perusal suggests it probably needs to be modified to understand
> > supporting multiple branches. I also don't know if it supports the
> > fast-forwarding/rebasing commits we want, but I doubt that would be
> > difficult to add. It probably also needs to grow an extension system
> somehow
> > to support custom NEWS entries for us.
>
> Which reminds me, Amber Brown recently wrote a NEWS file generator
> based on the file-per-issue model, later assembled into a NEWS file
> section as part of the project's release process:
> https://github.com/hawkowl/towncrier
>
> It's aimed more at projects with a simple linear release history
> rather than CPython's branching sprawl, though.
>
> Cheers,
> Nick.
>
> --
> Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20160101/3ecbd462/attachment.html>