+1, if we don't have a near term release plan for M2, we should stop maintain it now. It is really painful to commit codes twice.
2011/3/15 Shawn Jiang <[email protected]> > Considering the huge changes in m2/trunk, we've been suffering from the > code merge and verification between m2 branch and trunk. > > If we don't have a clear target date for m2 release. I suggest to drop > the current m2 branch and focus on trunk to avoid the effort to maintain two > code copies. We could rebranch m2 anytime when needed in the future . > > Thoughts ? > > -- > Shawn > -- Lei Wang (Rex) rwonly AT apache.org
