Re: Branching for V2.1?

On Fri, 2013-04-19 at 21:06 +0100, Philip Wyett wrote:
> Before we think of branching for another release. We need to:
> 
> * Define new features to be complete.

The set of functionalities currently in trunk seems already great. There
are a good set of new features and having them working sounds already
good enough. On the other hand, I also plan to add new features in trunk
in some near future, but wouldn't them to go directly in v2.2.

On my side, I also still plan to fix some problems within the physics2
and cseditor plugins, but that wouldn't be real API changes and this can
be made after the branching is made.

> * Define legacy items to be removed.

I'm not aware of anything that can be removed now. Any idea someone?

> * Define testing schedule.

The rule until now was kinda 'ASAP', meaning there 'nobody will really
care about that'.

We may decide some fixed deadline, e.g. 3 months after branching,
whatever happens?

> * Define QA testing criteria and schedule.

Testing criteria might be a little tough to be found out of manual
testing and user feedback.

We might consider releasing finally a win32 binary demo package in order
to get more feedback (and, why not, users)?



------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter