[Seaside] So where is the "release" version of 3.7?
tblanchard at mac.com
Tue Feb 27 02:31:43 UTC 2007
I don't understand the push back.
There are a bunch of branches.
I would like to see a branch
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
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.
The comment in the last version of 2.7a1 BTW gives me pause:
- backoff the change in mb-202 entitled "recovered essential lost
input conversion code"
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?
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.
I'm glad you're having fun. But I'm not.
On Feb 26, 2007, at 2:31 PM, Philippe Marschall wrote:
> So if there is a solution it must be one of the following:
> - someone currently doing no work for Seaside is stepping up to do
> "release management" or whatever you call it
> - some simple change that makes it easy for contributors to deliver
> "stable versions"
> I'd appreciate if the discussion focuses more on these two items and
> not on what we could all do if this was a big time Apache project and
> we were all paid for doing this.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Seaside