Re: No JIRA changes sent to a mailing list?
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
Re: general@velocity mailing list
+1 On Sat, May 30, 2015 at 7:58 AM, Frederick N. Brier fnbr...@gmail.com wrote: Sounds good to me :). On 05/30/2015 04:11 AM, Mike Kienenberger wrote: And while we're at it, why have a general@apache mailing list? Something inherited from Jakarta? It's not archived or publicly visible on nabble or mail-archive.com. Users have a difficult enough time determining whether a posting should go to user@ and dev@. I see nothing that differentiates between general@ and user@. I propose we remove the mailing list from our mailing lists page, and post a last message to general@ that we're shutting down general@ and switching existing subscribers to user@, and include instructions on how to unsubscribe from user@. That's if we want to go opt-out. Or go with opt-in, and post a last message to general@ that we're shutting down general@ and include instructions on how to subscribe to user@. Opt-in is probably the better approach. Then we ask infra to shut down the mailing list and optionally set up a redirect from general@ to user@. - 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
Recent JIRA issues (with patches) by me
Since I'm not certain who, if anyone, is notified of JIRA changes, here's a list of the items I've been working on. VELOCITY-864 Download and install Apache Rat task in preparation target for ant rat VELOCITY-863 Regression: #settableft-paren no longer valid grammar VELOCITY-862 Rebuilding parser using javacc 4.2 loses Node import VELOCITY-861 Improve parser modification and build documentation VELOCITY-860 Fix Velocity 1.7.x, 1.6.x, 1.5 ant download dependency build script Things I would like to see happen before a 1.8 release: -- insure rat passes with an appropriate exclude list -- fix tests [merging in Frederick's changes and/or Sergiu's changes] -- compile natively under Java 1.7 [merging in Frederick's changes and/or Sergiu's changes] -- update dependencies [merging in Frederick's changes and/or Sergiu's changes] I will slowly plod toward these goals but any additional help will be appreciated. - To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org For additional commands, e-mail: dev-h...@velocity.apache.org
No JIRA changes sent to a mailing list?
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? - To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org For additional commands, e-mail: dev-h...@velocity.apache.org
general@velocity mailing list
And while we're at it, why have a general@apache mailing list? Something inherited from Jakarta? It's not archived or publicly visible on nabble or mail-archive.com. Users have a difficult enough time determining whether a posting should go to user@ and dev@. I see nothing that differentiates between general@ and user@. I propose we remove the mailing list from our mailing lists page, and post a last message to general@ that we're shutting down general@ and switching existing subscribers to user@, and include instructions on how to unsubscribe from user@. That's if we want to go opt-out. Or go with opt-in, and post a last message to general@ that we're shutting down general@ and include instructions on how to subscribe to user@. Opt-in is probably the better approach. Then we ask infra to shut down the mailing list and optionally set up a redirect from general@ to user@. - To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org For additional commands, e-mail: dev-h...@velocity.apache.org
Re: No JIRA changes sent to a mailing list?
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
Re: No JIRA changes sent to a mailing list?
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
Re: general@velocity mailing list
Sounds good to me :). On 05/30/2015 04:11 AM, Mike Kienenberger wrote: And while we're at it, why have a general@apache mailing list? Something inherited from Jakarta? It's not archived or publicly visible on nabble or mail-archive.com. Users have a difficult enough time determining whether a posting should go to user@ and dev@. I see nothing that differentiates between general@ and user@. I propose we remove the mailing list from our mailing lists page, and post a last message to general@ that we're shutting down general@ and switching existing subscribers to user@, and include instructions on how to unsubscribe from user@. That's if we want to go opt-out. Or go with opt-in, and post a last message to general@ that we're shutting down general@ and include instructions on how to subscribe to user@. Opt-in is probably the better approach. Then we ask infra to shut down the mailing list and optionally set up a redirect from general@ to user@. - 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
