I guess I'm fine with whatever, making fast releases of collections is in fact pretty cool, it will give us practice with making releases in mahout in general. And if we can do this for mahout-math as well, some of us who care about, for example, eventually adding unit tests for all of the old Colt stuff, can do so bit by bit, and undeprecate code which is now tested, and then re-release with new version number frequently there as well.
I'm in favor, I guess, of: 1: remove collections-codegen and collections from the top-level pom's module list. 2: change their parents to point to the apache parent. 3: tweak their poms so that the release plugin works right with them. 4: release them 5: change rest of mahout to consume release. -jake On Tue, Apr 6, 2010 at 12:44 PM, Benson Margulies <bimargul...@gmail.com>wrote: > Where are we on the consensus process? > > Jake, have Ted and I satisfied you? Does this call for a VOTE to be > sure that we're on the same page? > > > On Tue, Apr 6, 2010 at 3:33 PM, Benson Margulies <bimargul...@gmail.com> > wrote: > > On Tue, Apr 6, 2010 at 3:10 PM, Ted Dunning <ted.dunn...@gmail.com> > wrote: > >> I should have said "there should SOON be a vanishingly small number of > >> collections releases". Clearly that isn't so just yet. > >> > >> On Tue, Apr 6, 2010 at 12:09 PM, Ted Dunning <ted.dunn...@gmail.com> > wrote: > >> > >>> if only because there should be a vanishingly small number of > collections > >>> releases > > > > Until we all all the unit tests and remove all the deprecations, I > > expect a some releases, as per Ted's later message. Then, it should > > get really, really, quiet. Unless we decide that it's the right place > > for things like bloom filters. > > > > > > I should also add that I still have hopes that collections will > > transmigrate to commons, so making it more independent of mahout is > > better. > > > >> > > >
