Vote result: 4 +1, 0 0, 0 -1 Vote has passed. On 12 May 2010 21:06, Milinda Pathirage <[email protected]> wrote: > +1 > > Thanks > Milinda > > On Wed, May 12, 2010 at 6:20 AM, hbdrawn <[email protected]> wrote: > >> >> last week when using V1.3.3,I have the problem of mutyply-instancing the >> process.Althought it was resolved by 1.3.4,but to user using this , it is a >> great issue.And it take me times to fix it. >> so,binding +1 >> >> Rafal Rusin wrote: >> > >> > Hello, >> > >> > let's start a vote for moving trunk into experimental branch and 1.X >> > back to trunk. >> > Later (I think after 1.3.5 release), we'll continue 2.X versioning in >> > trunk and focus on redesign a few important parts of ODE (like for >> > example removing binary serialization of execution states in favor of >> > XML serialization). >> > >> > I think this move is one of the most important decisions for the project >> > now. >> > So what we have now is ODE-1.X in production and old fork ODE-trunk, >> > which is not. >> > We also have a lot of issues for 1.X in production (check out fix for >> > 1.3.5 >> > >> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=12310270&fixfor=12314243&resolution=-1&sorter/field=priority&sorter/order=DESC >> ). >> > The obvious thing is that we have to stabilize 1.X and make people >> > happy for using it. >> > We also have to make 1.X better code quality, more documented, >> > redesign for example message broadcasting, add bpel validation (David >> > Carver is doing it), etc., etc. >> > So basicly, we have a situation where we also want some of new >> > features to be implemented in 1.X. This contradicts to having current >> > ODE-trunk, where new features go. >> > >> > So, we have current ODE-trunk, which costs us 2 times more developers' >> > power >> > to migrate all changes, because it's very desynchronized. Moreover >> > newcomers, tend to make contributions to ODE-trunk, which is bad, >> > because it doesn't bring higher quality to whole product. >> > >> > So for me it's obvious we should drop current ODE-trunk ASAP and merge >> > it's >> > new features in smaller steps, still staying with latest 1.X in >> > production. >> > This way we'll focus our efforts on something we use. And using >> > product in production makes it's real value. >> > >> > -- >> > Regards, >> > Rafał Rusin >> > >> > >> >> -- >> View this message in context: >> http://old.nabble.com/-VOTE--Move-trunk-into-experimental-branch-and-1.X-back-to-trunk-tp28525921p28530956.html >> Sent from the Apache Ode Dev mailing list archive at Nabble.com. >> >> > > > -- > Milinda Pathirage > Senior Software Engineer & Product Manager WSO2 BPS; http://wso2.org/bps > WSO2 Inc.; http://wso2.com > E-mail: [email protected], [email protected] > Web: http://mpathirage.com > Blog: http://blog.mpathirage.com >
-- Regards, Rafał Rusin
