Hi Carsten,
Theses are very good questions but difficult to answer. For me it's more a felling than numbers. For the moment I only use this
metric http://tinyurl.com/yb3h4hv. So you see it's more in survival mode.
Also I presume that it would be difficult to organize things (and even more people) as you suggested because we all depend on
clients requests and that changes pretty much all the time. But yes we may think about it...
IMO, the backlog concept could be the one we could focus on 1st.
There has been some attempts but not directed to a release
http://docs.ofbiz.org/display/OFBADMIN/New+Features+Roadmap+-+Living+Document
Jacques
From: "Carsten Schinzer" <[email protected]>
However, the argument of "critical mass" being brought up above seems a
little vague to me: What is actually the number of comitters / contributors
required to switch into a good release plan? Any ideas? Is it dependant on
the BUG statistics reported on JIRA? How many are they and how good are we
contributors in fixing them? Are we currently building a backlog? Is it for
trunk or for releases only? How are bug reports/bugs distributed across
components? Is it possibly critical to have a certain number of committers
per component?
Kind regards
Carsten
