On Sun, Jan 16, 2011 at 4:47 PM, Ryan McKinley <ryan...@gmail.com> wrote: > uggg -- sorry to see this thread flare up again -- especially since > Steve is actively making great progress on better maven support -- > including integration tests and all that jazz. (LUCENE-2657) > > I *think* the consensus from the last thread was: > 1. the release manager does not need to worry about maven > 2. someone else (from lucene) may post maven artifacts > 2a. if the process becomes easy enough, the RM *may* post the artifacts. > 3. There needs to be some test to check if the artifacts are OK. > > With Steve's work on LUCENE-2657, things are looking for for #2a and #3 >
I think its more complicated than that, someone else (from lucene) may post artifacts? who votes on these separate maven artifacts? are you saying that I can pipe /dev/null to some large files and post them as maven artifacts without 3 +1 votes? Personally I think we should keep our artifacts to a minimum. Shipping jars is enough trouble if only source code is really whats needed. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
