On 10/06/2015 01:55 AM, Matt Frantz wrote: > I would like to be able to escalate certain tickets to the dev@ list, but > not by default, since it would only create more emails for people to > ignore. I think this is a natural process in many cases, and as Stephen > says, should probably be considered on a case-by-case basis. > > The JIRA comment history is not always the best way to experience a complex > issue with lots of discussion. Sometimes, you need to create a summary > (which should probably go in the ticket), and sometimes share that via dev@. > > Is it possible to link to a dev@ thread from JIRA? I like gremlin-users > because it gives you that stable topic URL. That would be nice to keep > JIRA in the loop when the conversation advances in the dev@ list.
Yes/no/maybe/soon. You can link to the mail-archives for now (mail-archives.apache.org), but we're working on adding Pony Mail to our stack as a replacement for the rather old and cumbersome mod_mbox system we currently use. You can see this dev list on PM at https://pony-poc.apache.org/[email protected] That URL is of course going to change a bit once/if/when we move it into production (the sub-domain is going to change). Also beware that it is a bit behind, as it's not been fully implemented in the mailing system yet, so it relies on mail-archives to catch up first, which may take a few minutes. committers and non-committers alike can also use the pony mail system to reply to emails and start new topics when logged in (committers should use the ASF Oauth system, non-committers may use Persona). With regards, Daniel. PS: The permalink for this thread on PM is: https://pony-poc.apache.org/thread.html/12da2e69cfdde349b4cd3a27123c77a76af45f7fc693703981cb73f0@1444073875@%3Cdev.tinkerpop.apache.org%3E > > On Mon, Oct 5, 2015 at 1:23 PM, Stephen Mallette <[email protected]> > wrote: > >> I don't think we need to explicitly create DISCUSS emails for every JIRA >> ticket. That's not getting at what I'm understanding to be the fundamental >> problem. The issue is that we have discussion in JIRA on, let's say, two >> kinds of things (to keep it simple): >> >> 1. Important - breaking changes, release planning, design changes, big idea >> proposals >> 2. Less-important - bug, performance enhancement/optimization, non-breaking >> feature/refactoring, javadoc/documentation >> >> For someone not in the project day in/out, it's hard for them to dig into >> what's "Important" because there is all this other activity in JIRA that is >> flying into the dev mailing list and thus it all gets ignored. I think we >> can go a long way to keeping folks in touch with the project and improving >> their ability participate by simply keeping emails to the dev list with >> DISCUSS focused on "important". I'm not saying we can't have them for >> "less important", but if it's a standard "bug", is there really much to >> discuss? someone just go fix the bug. if the documentation can better by >> adding a new section - go write the docs. In the end, those kind of things >> should be considered on a case-by-case basis. >> >> To the extent it's possible, we might also try to DISCUSS first prior to >> creating a JIRA issue. That's not always practical to do for whatever >> reason, but then it's easy to transfer the salient points from the DISCUSS >> to JIRA when the time comes and in the mean time the interaction happened >> in a way that was easy for folks to follow. >> >> >> On Mon, Oct 5, 2015 at 3:37 PM, Marko Rodriguez <[email protected]> >> wrote: >> >>> Hello, >>> >>> JIRA writes to dev@, but is seems that is not sufficient by Daniel >>> Gruno's standards as "people ignore" JIRA emails. >>> >>> Here is what I recommend. >>> >>> 1. If you make a JIRA ticket write an email to dev@ about that >>> ticket. [yes---even though that same email just came through via JIRA >>> emailing it to dev@] >>> 2. The subject of the mail should say: "[DISCUSS] >>> http://url.to.jira.ticket"; >>> 3. In the body of the email write: "If you do not have JIRA write >>> access, please reply to this email and we will copy/paste your email >> over." >>> - Also add the JIRA ticket URL in the body so its easy to >>> click. >>> 4. If you DO have JIRA access, please use the JIRA ticket for >>> comments so we have everything consolidated in JIRA and not split between >>> JIRA and dev@. >>> >>> Thoughts?, >>> Marko. >>> >>> http://markorodriguez.com >>> >>> >> >
