... but it's important to note that if we take this approach, we need to be careful not to just summarize the conclusion of the discussion, but also approaches that were examined and found to be unviable, and why. Otherwise people looking at the ticket will have to cross reference back to a much harder-to-follow discussion on the list archives.
On Mon, Aug 15, 2016 at 6:26 PM, Jonathan Ellis <jbel...@gmail.com> wrote: > On Mon, Aug 15, 2016 at 6:18 PM, Josh McKenzie <jmcken...@apache.org> > wrote: > >> 2: 8844 would have been a great candidate for being discussed on the >> mailing list rather than on JIRA. While I made it a point to front-load >> design, we still ran into some unforeseen consequences from the design >> that >> might have been prevented by more wide-spread discussion. In my opinion, >> it >> would have made sense to have the initial discussion(s) take place on the >> mailing list until a design had settled out, worked that design and the >> day-to-day back and forth on JIRA, then bringing it back to the mailing >> list when we ran into the problems with the design. >> > > This is a good example of what I had in mind here. > > -- > Jonathan Ellis > Project Chair, Apache Cassandra > co-founder, http://www.datastax.com > @spyced > -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced
