I see that team members informations are in both places: in the
master pom, and in the site pom (which does not depend on the master,
perfect). I'd be in favour of removing them from the master pom, for
several reasons:

1. it's redundant, and it better belongs to the site (oh and by the way
it isn't up to date, as Will is still mentioned as the PMC Chair)

2. we're not gonna release a new master (which implies new releases for
each and every subproject) each time we have a new committer, so if we
keep this information here, it will quickly become out-of-date

But I'm maybe missing something...


  Claude

On Thu, 10 May 2012 11:24:05 -0700
Nathan Bubna <[email protected]> wrote:

> +1
> 
> On Thu, May 10, 2012 at 11:18 AM, Antonio Petrelli
> <[email protected]> wrote:
> > The Velocity Master 1 test build has been available since 5th May
> > 2012.
> >
> > Distribution:
> >
> >  *
> > https://repository.apache.org/content/repositories/orgapachevelocity-027/org/apache/velocity/velocity-master/1/velocity-master-1-source-release.zip
> >
> > Maven 2 staging repository:
> >
> >  *
> > https://repository.apache.org/content/repositories/orgapachevelocity-027/
> >
> > If you have had a chance to review the test build, please respond
> > with a vote to release it or not:
> >
> > -1: Leave at test build
> > +1 Release it
> >
> > Everyone who has tested the build is invited to vote. Votes by PMC
> > members are considered binding. A vote passes if there are at least
> > three binding +1s and more +1s than -1s.
> >
> > Antonio
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected]
> > For additional commands, e-mail: [email protected]
> >
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to