Some patches are quite large; would it really make sense to send that much content via email to an entire list?
On Thu, Aug 12, 2010 at 9:24 PM, David Reiss <[email protected]> wrote: > Is it possible to configure JIRA to include patch content in notification > emails? > > On 08/12/2010 09:13 PM, Joe Schaefer wrote: > > > > > > > > > > ----- Original Message ---- > >> From: David Dabbs <[email protected]> > >> To: [email protected] > >> Sent: Thu, August 12, 2010 11:32:58 PM > >> Subject: RE: time for a reboot? > >> > >>>> sometimes that cuts against having multiple people involved. > >>> Do you have a sense for why that is? > >>> I think switching to the mailing list for code reviews would > >>> be a pain, and I'd rather fix whatever problem prevents > >>> people from contributing to JIRA discussions > >>> (or switch to a real code review tool) than just toss it. > >> > >> > >> > >> If you are using JIRA, oss license I presume, then why not also use > >> Atlassian's Cruicible? > > > > Some projects at Apache do use Crucible with some success, but the > > problem I'm driving at is based on the fact that patches attached > > to jira don't get looked at by more than a handful of people, whereas > > patches sent to the thrift-dev@ list are at least seen by every > subscriber. > > Open source is a very lazy development system, where the more stuff you > > put between the code and a person's eyeballs the less likely they'll > > actually bother. > > > > Email as the main communication vehicle for open source development > > has survived largely because it puts the patches right there in > > everyone's inbox. Even very lazy people don't mind skimming commit > > messages for interesting content ;-). That's why some projects > > at Apache don't keep the commit messages on a seperate list from the > > development list. > > > > > > >
