openerp-community-leaders team mailing list archive

[Raphaël Valyi <rvalyi@xxxxxxxxx>]

Hello,

The community doesn't spend a lot of time currently on bug planning because
we still can't do it efficiently unless you do what I list here:

****** problems for 5.0.x bug planning ******

We can't plan bugs on 5.0.x releases because we don't know any release
calendar. 5.0.7 was announced at mid December, it's still not released at
mid January. We asked the community to test it urgently in mid December,
even during the week end. I assume some made the effort and indeed
regressions where unlikely during that test effort. But if we ask work from
the community and Tiny don't do what it announce (release 5.0.7, work on
discovered regressions only lately), then it's not credible to ask more from
the community.

Currently we don't know why Tiny doesn't release 5.0.7, I list here
hypotheses:

1) is it because of the regressions found here
https://launchpad.net/openobject-addons/+milestone/5.0.7 ?
If yes, why those regressions receive less priority than the other
unimportant bugs or bugs that were always present?

2) is that because of the new important bugs found and target for 5.0.7 such
as: https://bugs.launchpad.net/bugs/452854 ?
Well, working on those is great, but those bugs were always present so, why
delay 5.0.7 forever letting instead lots of new install be done on 5.0.6
which have hundreds of more bugs, possibly very important?

3) other reason?


The result is that even if we see an important bug, now we don't have the
courage to target it to 5.0.7 because we fear it will delay 5.0.7 even more
forever.
We don't target bugs on 5.0.8 either because we have no idea how many bugs
we can target to 5.0.8 (eg relative priority) because we don't know at all
if 5.0.8 will be released in 2 weeks (like time period between 5.0.2 and
5.0.3) or in 5 months (like time period between 5.0.6 and 5.0.7).

I talked about that with Fabien, Quentin and Christophe and we all agreed
that we need some scheduled released at least (like one per month or per 2
months, this is up to you but I personnaly prefer one per months to make
users benefit the more possible bugfix), so why is that not done? Can't you
do it? We community have no admin rights neither authority to do the
schedule nor the releases.
Of course, having scheduled versions doesn't prevent some intermediary
release in case of critical bugfix/exceptionnal regression.


****** problems for 5.2.x bug planning  ******

There are some bugs that are whishlist for 5.0.x but that we need to plan
for 5.2. Here are examples:
https://bugs.launchpad.net/bugs/510161
https://bugs.launchpad.net/openerp/+bug/257581

But this time we can't do it because no milestones have been created for
those projects.

So can please Tiny create at least a 5.2 milestone for:
- openobject-server
- openobject-client


Thank you very much and good luck with the dev.