Slight change of position - i think the documentation with the pitch should reflect the end state. In other words, it should be suitable for committing on master when the feature is ready; and not be a pitch itself. This is slightly different from the doc linked above.
-=Bill On Mon, Oct 13, 2014 at 1:49 PM, Bill Farner <wfar...@apache.org> wrote: > Maxim's 'External Update Coordination' thread [1] sets a precedent for > pitching a feature via documentation before diving into code. I propose we > standardize on this practice for big and small features. This will take > some trial-and-error to get right, but i think for small changes requiring > documentation, they are both committed at once. For large features, the > documentation helps define the requirements and seed a discussion, and is > committed once the feature can be used. > > Any +/-1s on this approach? > > > [1] > http://mail-archives.apache.org/mod_mbox/incubator-aurora-dev/201410.mbox/%3CCAOTkfX7x2oipk4ZFysoS0uWZRizOnKJA3y15pvEW5K4YnUHw-A%40mail.gmail.com%3E > > > -=Bill >
