OK, so all I need is to reply and change the To to [email protected]? I'll give it a try.
Shai On Thu, Feb 13, 2014 at 11:02 AM, Uwe Schindler <[email protected]> wrote: > Hi Shai, > > > > It does not work with JIRA, because the reply is sent to dev@lao not the > issue server. The problem here is the mailing list configuration, which > sets the reply address to dev@lao: By default JIRA allows to post stuff > to the JIRA's mail address and its directed to the issue comments, but for > that to work, the "To" address has to also include [email protected] . > > > > Uwe > > > > ----- > > Uwe Schindler > > H.-H.-Meier-Allee 63, D-28213 Bremen > > http://www.thetaphi.de > > eMail: [email protected] > > > > *From:* Shai Erera [mailto:[email protected]] > *Sent:* Thursday, February 13, 2014 9:30 AM > *To:* [email protected] > *Subject:* Re: DISCUSS: Go "all in" on github integration > > > > +1. > > I read on the Apache page that part of the integration lets us reply to an > email from the GitHub issue, and the response is recorded on the issue. > Does that work w/ JIRA as well? I gave it a quick try and seems like it > doesn't.. > > Shai > > > > On Thu, Feb 13, 2014 at 9:41 AM, Tommaso Teofili < > [email protected]> wrote: > > +1 > > > > Tommaso > > > > 2014-02-12 23:29 GMT+01:00 Chris Hostetter <[email protected]>: > > > > > As some folks may know, apache infra has been making lots of improvements > to how the users of the github mirrors of ASF projects can interact with > the regular apache dev cycle. > > A while back, some of these features were enabled for the Lucene/Solr code > base, and we have already had a few contributions submitted as Github Pull > Requests that were then committed. > > Infra has recently announced more autoamted integration between github > concepts and regular Apache work flow on the mailing lists & Jira -- on a > per-project Opt-In basis... > > > https://blogs.apache.org/infra/entry/improved_integration_between_apache_and > > ...It's not entirely clear to me how fine grained the enable/disable > controls are for some of these features -- wether we already have all of > these features enabled based on our past infra requests, or if we need to > "opt-in again" to the new ones before we'll see any changes ... but my > suggestion is that we file a Jira with infra that says something to the > effect of... > > "The Lucene PMC wishs to opt-in on any and all github related project > linkages that are available that we may not already be opted-in to." > > > Any objections? > > > -Hoss > http://www.lucidworks.com/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > > >
