I have no problem to cut beta1 early. However, we need to leave sufficient time for beta2
(or CR, for that matter). Main reason being this is a major release. I think we need to do
some benchmark to make sure the performance does not suffer too much, and perform
necessary optimization. This will take some time, IMO.
-Ben
-----Original Message-----
From: jbosscache-dev-bounces(a)lists.jboss.org
[mailto:jbosscache-dev-bounces@lists.jboss.org] On Behalf Of Manik Surtani
Sent: Thursday, January 11, 2007 6:13 PM
To: jbosscache-dev(a)lists.jboss.org
Cc: QA
Subject: [jbosscache-dev] Habanero BETAs
Guys,
Now that Alpha2 has been released and is in the wild, can we focus on
BETA1 tasks and target to have these cleared by Monday the 22nd so QA has time to very
thoroughly test and release by the 25th.
Please let me know your thoughts on this, or if you have any concerns about tasks that may
not be complete by then. Pls refer to
http://jira.jboss.com/jira/browse/JBCACHE
for the tasks I have scheduled for BETA1. The goal is to be both feature complete and to
freeze the API. Profiling, benching and refactoring for BETA2.
Thanks,
--
Manik Surtani
Lead, JBoss Cache
JBoss, a division of Red Hat
Email: manik(a)jboss.org
Telephone: +44 7786 702 706
MSN: manik(a)surtani.org
Yahoo/AIM/Skype: maniksurtani
_______________________________________________
jbosscache-dev mailing list
jbosscache-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosscache-dev