David E Jones wrote:
I don't mean to dilute the framework release effort. But at the same
time, it seems to me issues are coming up in R4 that have been
addressed in the trunk.
While to some extent this depends on the type of issue, in general
issues in the 4.0.0 branch should be fixed in that branch by the
"sub-community" that has formed around the branch. If things are not
getting fixed, to me that means the branch has not attracted enough of a
user and contributor community. I don't know how to fix that problem...
It is true that most of the bugs discovered in R4 are fixed as they come
up. I was thinking more along the line of the kinds of things that were
corrected by refactorings and such.
I've run across a number of people using R4 and service providers who
are using R4 for their customer's deployments. In addition, Opentaps is
based on R4. So, there is a sizeable R4 community out there, even if
they aren't vocal on the mailing lists and such.
I guess the goal or purpose of a Release 5 would be the same as Release
4 - to provide the opportunity to build on a target that isn't moving.
I agree that there needs to be a community of people who want it and are
willing to support it. I was just tossing the idea out there, but at
this point in time there doesn't seem to be much interest.
-Adrian
