Definitely dev@ Thanks, Sergiu!
On Sat, May 30, 2015 at 5:18 AM, Mike Kienenberger <mkien...@gmail.com> wrote: > I'd say dev. If you want to move discussion from an issue to the > mailing list, having them sent to dev makes replying easy. > > Plus, people who are subscribed to commits likely only want to see > actual changes, not potential problems. > > > On Sat, May 30, 2015 at 7:57 AM, Sergiu Dumitriu > <sergiu.dumit...@gmail.com> wrote: > > I was just about to send a similar mail. The issue is that it's > > configured to send emails to velocity-...@jakarta.apache.org, which I > > believe is not valid anymore. I don't know who can change this, since as > > a project administrator I can't change that. Probably something infra > > must handle (cc-ing). > > > > Infra: for the VELOCITY jira project, the notification scheme must be > > changed to send emails to dev@velocity.apache.org instead of the defunct > > velocity-...@jakarta.apache.org > > > > (or should that be comm...@velocity.apache.org?) > > > > On 05/30/2015 06:54 AM, Mike Kienenberger wrote: > >> I signed up for the commits mailing list, but as I was looking through > >> the archives, I noticed that there's no JIRA change notifications sent > >> to commit@, nor are they sent to dev@. Shouldn't these be going to a > >> mailing list? How do you subscribe to JIRA changes? > > > > -- > > Sergiu Dumitriu > > http://purl.org/net/sergiu/ > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org > > For additional commands, e-mail: dev-h...@velocity.apache.org > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org > For additional commands, e-mail: dev-h...@velocity.apache.org > >
