<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; ">I don't understand the push back.<DIV><BR class="khtml-block-placeholder"><DIV>There are a bunch of branches.</DIV><DIV>Seaside2.50</DIV><DIV>Seaside2.5b7</DIV><DIV>Seaside2.5b8</DIV><DIV>...</DIV><DIV>Seaside2.7a1</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>I would like to see a branch</DIV><DIV>Seaside2.7 - which I would expect to be the release version. The really great email by Philippe that lists all the features in the new release should be in the class comment of the oldest version in this branch.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Any new changes in this branch are minor bug fixes. Minor bugs discovered in 2.8 and fixed will have to have their fixes backported. Keeping the list apprised of those fixes you make will help people improve the quality of 2.7 while still letting you press on in 2.8.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>The comment in the last version of 2.7a1 BTW gives me pause:</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>- backoff the change in mb-202 entitled "recovered essential lost input conversion code"</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>That doesn't sound like a minor bug fix. It sounds like a big change. It makes versions from 202-204 suspect. Not good versions to use for production, probably. But this is the immediate ancestor of the Seaside2.8a1 branch?</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>So my complaint is that the version numbering only makes sense to you. The criteria for bumping the version number only makes sense to you. There is nothing for someone doing production code and desiring a stable platform to hang his hat on. </DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>I'm glad you're having fun. But I'm not.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>-Todd Blanchard</DIV><DIV><BR><DIV><DIV>On Feb 26, 2007, at 2:31 PM, Philippe Marschall wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite"><P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">So if there is a solution it must be one of the following:</FONT></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">- someone currently doing no work for Seaside is stepping up to do</FONT></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">"release management" or whatever you call it</FONT></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">- some simple change that makes it easy for contributors to deliver</FONT></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">"stable versions"</FONT></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica; min-height: 14.0px"><BR></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">I'd appreciate if the discussion focuses more on these two items and</FONT></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">not on what we could all do if this was a big time Apache project and</FONT></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">we were all paid for doing this.</FONT></P> </BLOCKQUOTE></DIV><BR></DIV></DIV></BODY></HTML>