[Seaside] So where is the "release" version of 3.7?
jbjohns at libsource.com
Wed Feb 28 17:46:32 UTC 2007
I think the ad-hoc release culture that seaside currently has is a huge
benefit and advantage. Lukas usually has what ever bug I find fixed
before I get the email update. What needs to stop is the need of
updating from Monticello. Other open source projects use CVS or
Subversion, but when you go to their site how many recommend you
download from the repository? Most give it as an option, but nearly all
have a separate place for getting the latest
stable/unstable/foo-only/etc. This what needs to get adopted and this
would allow folks that are in a position to know to update the package,
so that people who can't keep up with it don't have to.
Avi Bryant wrote:
> On 2/26/07, Avi Bryant <avi at dabbledb.com> wrote:
>> Ok, but there are processes that work for that too. Have a branch
>> that is 2.7-stable, and generally commit to that. If you're doing a
>> refactoring or feature you're not sure about, do it on
>> 2.7-somerefactoring, then merge in when you're confident of it. The
>> important thing is just that everyone know what the system is.
> Let me hasten to add that I am more responsible than anyone for the
> ad-hoc release culture here. Now that I'm in a less active role, it's
> easy to preach from the sidelines :). But we've grown a lot (this
> list is nearly 600 strong, now), so we can probably afford to clean up
> our act a little.
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
More information about the Seaside