Hi, Below contains the revised milestone plan for BAM 2.4.0 release.
* M1 - 06/Sep/13 - https://wso2.org/jira/browse/BAM/fixforversion/11044 * M2 - 13/Sep/13 - https://wso2.org/jira/browse/BAM/fixforversion/11045 * M3 - 20/Sep/13 - https://wso2.org/jira/browse/BAM/fixforversion/11046 * RC - 25/Sep/13 * GA - 30/Sep/13 Cheers, Anjana. On Mon, Jul 15, 2013 at 5:29 PM, Anjana Fernando <[email protected]> wrote: > Hi Samisa, > > +1, yeah, that was actually the idea by having some smaller milestones. We > will provide packs for QA as soon as we are finishing any done-done > features that can be tested. > > Cheers, > Anjana. > > > On Mon, Jul 15, 2013 at 5:22 PM, Samisa Abeysinghe <[email protected]>wrote: > >> For QA by QA team, if we have done-done features in milestones, those can >> be given for formal QA with a working milestone pack. No need to wait till >> the release cycle. This way we can ensure some of the features will be well >> tested by the time we reach the release time. >> >> >> On Mon, Jul 15, 2013 at 5:14 PM, Anjana Fernando <[email protected]> wrote: >> >>> Hi Samisa, >>> >>> The time is not constant, we increased the release time by one more >>> month. We are currently working on a PoC for a possible feature that will >>> go into the release. After that, I can again map the time periods for the >>> milestones. >>> >>> Cheers, >>> Anjana. >>> >>> >>> On Mon, Jul 15, 2013 at 5:11 PM, Samisa Abeysinghe <[email protected]>wrote: >>> >>>> Adding more features keeping the time as constant will be a problem. Do >>>> we plan to re-prioritize and remove some items making room for some new >>>> ones? >>>> >>>> >>>> On Mon, Jul 15, 2013 at 10:50 AM, Anjana Fernando <[email protected]>wrote: >>>> >>>>> Hi, >>>>> >>>>> The current milestone plan for BAM 2.4.0 has changed, due to some >>>>> additional features we are planning on supporting. And also, we have some >>>>> problems in building the trunk at the moment, because of some changes done >>>>> there. I will send a updated milestone plan later. >>>>> >>>>> Cheers, >>>>> Anjana. >>>>> >>>>> >>>>> On Thu, Jun 27, 2013 at 7:50 AM, Anjana Fernando <[email protected]>wrote: >>>>> >>>>>> Hi Samisa, >>>>>> >>>>>> Yeah, I didn't mean actually only at the end we start working on >>>>>> bugs, I just meant in the schedule, at the end, all the bugs should be >>>>>> fixed. We would be fixing bugs throughout the time. >>>>>> >>>>>> Cheers, >>>>>> Anjana. >>>>>> >>>>>> >>>>>> On Wed, Jun 26, 2013 at 6:04 PM, Samisa Abeysinghe >>>>>> <[email protected]>wrote: >>>>>> >>>>>>> Guys, looking into the bugs, only at the last mile stage is >>>>>>> absolutely the wrong model to get quality right. >>>>>>> Specially given that we have 150 open bugs to start with: >>>>>>> https://wso2.org/jira/secure/Dashboard.jspa?selectPageId=10399 >>>>>>> >>>>>>> Resolving these 150 alone will take a month. And leave room to >>>>>>> another 100 that comes new. So we need to plan for 150 bugs. >>>>>>> >>>>>>> >>>>>>> On Wed, Jun 26, 2013 at 9:22 AM, Anjana Fernando <[email protected]>wrote: >>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> Below contains the milestone plan for BAM 2.4.0 release. >>>>>>>> >>>>>>>> M1 - 12'th July >>>>>>>> =========== >>>>>>>> >>>>>>>> * Annotation scheme for Hive scripts >>>>>>>> * Ship BAM Publisher library with the product >>>>>>>> * Add timestamp support for Cassandra and JDBC Hive Storage Handlers >>>>>>>> * Improve BAM Tolbox deployment >>>>>>>> * JMX Monitoring Improvements >>>>>>>> >>>>>>>> M2 - 26'th July >>>>>>>> =========== >>>>>>>> >>>>>>>> * Change NTask Component to use Hazelcast based Carbon Clustering >>>>>>>> Component >>>>>>>> * Activity Monitoring Toolbox Improvements >>>>>>>> * JMX Support for Data Agents >>>>>>>> * Improve BAM Analytics Engine >>>>>>>> * Improve ESB Monitoring >>>>>>>> * Data Agent for Servlet Containers >>>>>>>> >>>>>>>> M3 - 9'th August >>>>>>>> ============ >>>>>>>> >>>>>>>> * Improve the usabilty of BAM mediator configuration interface >>>>>>>> * Processing Time Slice of Data >>>>>>>> * Improve Data Archival Feature >>>>>>>> * Basic Tooling Support for BAM >>>>>>>> * Puppetize commonly used BAM setups >>>>>>>> * Data Agent for MS WCF >>>>>>>> >>>>>>>> RC - 23'rd August >>>>>>>> ============= >>>>>>>> >>>>>>>> * Fix all L1 / L2 >>>>>>>> >>>>>>>> GA - 30'th August >>>>>>>> ============= >>>>>>>> >>>>>>>> Cheers, >>>>>>>> Anjana. >>>>>>>> >>>>>>>> -- >>>>>>>> *Anjana Fernando* >>>>>>>> Technical Lead >>>>>>>> WSO2 Inc. | http://wso2.com >>>>>>>> lean . enterprise . middleware >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Dev mailing list >>>>>>>> [email protected] >>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> >>>>>>> Thanks, >>>>>>> Samisa... >>>>>>> >>>>>>> Samisa Abeysinghe >>>>>>> VP Engineering >>>>>>> WSO2 Inc. >>>>>>> http://wso2.com >>>>>>> http://wso2.org >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> *Anjana Fernando* >>>>>> Technical Lead >>>>>> WSO2 Inc. | http://wso2.com >>>>>> lean . enterprise . middleware >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> *Anjana Fernando* >>>>> Technical Lead >>>>> WSO2 Inc. | http://wso2.com >>>>> lean . enterprise . middleware >>>>> >>>> >>>> >>>> >>>> -- >>>> >>>> Thanks, >>>> Samisa... >>>> >>>> Samisa Abeysinghe >>>> VP Engineering >>>> WSO2 Inc. >>>> http://wso2.com >>>> http://wso2.org >>>> >>> >>> >>> >>> -- >>> *Anjana Fernando* >>> Technical Lead >>> WSO2 Inc. | http://wso2.com >>> lean . enterprise . middleware >>> >> >> >> >> -- >> >> Thanks, >> Samisa... >> >> Samisa Abeysinghe >> VP Engineering >> WSO2 Inc. >> http://wso2.com >> http://wso2.org >> > > > > -- > *Anjana Fernando* > Technical Lead > WSO2 Inc. | http://wso2.com > lean . enterprise . middleware > -- *Anjana Fernando* Technical Lead WSO2 Inc. | http://wso2.com lean . enterprise . middleware
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
