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
+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
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
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?
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
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
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).
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
