I've talked to a couple of people about this in person, but figured I'd put it out here.
I have access to a 16 node cluster in my lab that we typically use for R&D type projects. We have accumulo on it right now and is typically doing something hadoop related. If there is a need to do testing of accumulo release on bare metal with respectable equipment, let me know how we might be able to contribute. -Don On Thu, Jul 11, 2013 at 5:43 PM, Dave Marion <dlmar...@comcast.net> wrote: > Historically, how long has it taken to complete testing of release > candidates? Subtract that from 1 November and that should be the target > date. Based on 1.5.0, that means feature complete is tomorrow, right? :-) > > -----Original Message----- > From: Sean Busbey [mailto:bus...@cloudera.com] > Sent: Thursday, July 11, 2013 5:17 PM > To: dev@accumulo.apache.org > Subject: Schedule for 1.6.0 release? > > One of the action items out of the 1.6.0 discussion[1] was that we'd use > the list to decide on a target release date, feature set, and incremental > milestones for Accumulo 1.6.0. > > I know the initial plan was to aim for November, and right now Jira says > as much[2]. > > That's only ~4 months away, so we should lay out some plans. When do we > need to target feature complete to meet that goal? When does code freeze > need to happen? > > > > [1]: > > https://docs.google.com/a/cloudera.com/document/d/1FkP2dDE4zzH1ou89_-qpW6-7dtBj9XdMRGjFnnLGrTI/edit > [2]: https://issues.apache.org/jira/browse/ACCUMULO/fixforversion/12322468 > > -- > Sean > > -- * *Donald Miner Chief Technology Officer ClearEdge IT Solutions, LLC Cell: 443 799 7807 www.clearedgeit.com -- This communication is the property of ClearEdge IT Solutions, LLC and may contain confidential and/or privileged information. Any review, retransmissions, dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you receive this communication in error, please immediately notify the sender and destroy all copies of the communication and any attachments.
