Emmanuel Venisse wrote:
I don't know yet if we must add the second part in a second beta or in 1.2.
The first part will change the database and the second part too. We'll
need a migration tool between between actual db and first part and an
other between first part and second part. Maybe we can change all db
things in the first part so we won't need db migration between first and
second parts.
Do you know what will go to 1.2? It would be good to define it in jira.
It shouldn't go into 1.1 as 1.1 is already way behind schedule and
should focus on getting the features already in or scheduled to be added.
The idea is good and I think it will be a very useful feature, but the
focus should be on delivering a final 1.1 before anything else.
--
Trygve
