Simone Tripodi wrote: > http://people.apache.org/~simonetripodi/ > http://simonetripodi.livejournal.com/ > http://twitter.com/simonetripodi > http://www.99soft.org/ > > > On Mon, Mar 18, 2013 at 9:51 AM, sebb <seb...@gmail.com> wrote: >> On 18 March 2013 08:46, Sebb (JIRA) <j...@apache.org> wrote: >>> >>> [ https://issues.apache.org/jira/browse/DIGESTER-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment- tabpanel&focusedCommentId=13604945#comment-13604945 >>> [ ] >>> >>> Sebb commented on DIGESTER-171: >>> bq. * When adding new classes, it is a good practice adding the @since >>> javadoc tag. >> >> I think it's the job of the Commons developer/release manager to >> ensure that the correct @since tags are added. >> Seems unfair to ask 3rd parties to work out what the next version >> number is - and it may change. > > The POM always contains the current development version, not a big > deal for contributors, especially if they aim to become committers, to > get familiar with Commons practices.
Actually, for my own projects I always add @since upcoming or @deprecated As of upcoming ... When I prepare a release I use a the regular expression "s/(since|As of) (\s+)upcoming/\1\2VERSION/" to set the proper VERSION. Just my 2¢, Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
