The ASF leaves almost all decisions like this up to the individual projects. There are only a few "must" items which have to be followed (releases build from source, code is owned by the ASF, code is licensed Apache License, notices for other licenses, brand management)
As you and I are the active developers, I think we can go with whatever rule makes the most sense, so long as the rest of the Velocity PMC doesn't object. I don't have a strong opinion on that one so we can go with what you propose. We just need to agree on what "affects" means :) On Tue, Jun 2, 2015 at 10:58 PM, Sergiu Dumitriu <sergiu.dumit...@gmail.com> wrote: > In other projects that I've been involved in, the rule was that "affects > version" should point to a released version, and if something doesn't > "affect" a release version, then this should be left blank. Does > Velocity / Apache in general follow a different rule? > > On 06/02/2015 10:53 PM, Mike Kienenberger (JIRA) wrote: >> >> Mike Kienenberger updated VELOCITY-864: >> --------------------------------------- >> Affects Version/s: (was: 1.7.x) >> 1.x >> > > -- > 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
