Ralph Goers wrote:
Upayavira wrote:
I couldn't agree more. Personally I'd be -1 on porting ECM++ back to
2.1.x. 2.1.x should be a _maintenance_ branch, and unless we can focus
on getting 2.2 out in some form, we risk some serious geopardy for our
community, I think.
So, let's release 2.2, make that the main branch, and start adding
OSGi, Maven, etc, into 2.3. \
I really think we should get into the mindset that the branch with real
blocks and OSGi will be 3.0.
With Carsten's proposal to release every two months, we're almost back
into release early, release often, but, problem is, we'd be releasing
a branch often, which is seriously broken, IMO.
I'd say, let's release 2.2M1 at the same time as 2.1.8, say, just
after the GetTogether.
+1 - If Carsten (or whomever) can move ECM++ by then.
Huh? Nono, we shouldn't move ECM++. We should release 2.2M1 with ECM++,
and 2.1.x should start its death/deprecation process soon, releasing
2,1.8 which hopefully will be the last in that branch.
Regards, Upayavira
