[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: development process
From: |
Kieren MacMillan |
Subject: |
Re: development process |
Date: |
Wed, 5 Feb 2020 20:59:33 -0500 |
Hi Graham (et al.),
> LilyPond has had a lot of patches get dropped because
> nobody feels comfortable reviewing / shepherding them.
Seems to me like one solution to that problem might be a subtle variant on
extreme programming: All features/fixes must be signed out for "patch-ing" by
two developers, at least one of which has committed to and is capable of being
the mentor (shepherding/reviewing).
The [well-documented] benefits of extreme programming should decrease poor
design choices out of the gate, reduce the number of errors, make the whole
process go faster, and guarantee that the "coding team" has the skills and
commitment to take it to the goal line [assuming the rest of the process is
relatively smooth and the gatekeepers receptive].
Cheers,
Kieren.
________________________________
Kieren MacMillan, composer (he/him/his)
‣ website: www.kierenmacmillan.info
‣ email: address@hidden
- Re: development process, (continued)
- Re: development process, Han-Wen Nienhuys, 2020/02/05
- Re: development process, David Kastrup, 2020/02/05
- Re: development process, Dan Eble, 2020/02/05
- Re: development process, Kevin Barry, 2020/02/05
- Re: development process, Kieren MacMillan, 2020/02/05
- Re: development process, David Kastrup, 2020/02/05
Re: development process, Thomas Morley, 2020/02/05
Re: development process, Graham Percival, 2020/02/05
Re: development process, Joram Noeck, 2020/02/05
Re: development process, Jürgen Reuter, 2020/02/05