Jacques Le Roux wrote:
1) put more people in the "ofbiz-developers" Jira group; the advantages are:
Yes it would be useful. How to define eligible persons, asking persons or
waiting that they ask ?
I think that both ways are good... for example I already have a list in
my mind for persons that will be eligible.
2) create in Jira at least two target releases, one would be the post
graduation release (cooming soon), while the second could be a longer
term release, with no Release Date, that will be released as soon as all
the issues assigned to it will be completed; issues can be assigned to
the longer term release only in one of the following situations:
2a) by community vote ("Vote: set the target for Jira issue #OFBIZ-XYZ
to release X")
2b) the developer that assigns the issue to the release, also assigns
the issue to himself ("ok, I'll work on this issue, and I'll complete it
in a reasonable amount of time, because I want it in the X release");
these issues should be bug fixes or obvious improvements (I mean
something that doesn't need a community vote because the consensus is
implied)
Yes, I'm not sure it's the better way to manage releases (or it's enough I
mean) but surely it should help.
I agree with you that this is not enough... but it could be a starting
point.
Jacopo
