Dave wrote:
On 10/20/06, Anil Gangolli <[EMAIL PROTECTED]> wrote:
Yowza!
I think we should ask the user community about the 3.0 v. 3.1 issue.
I'm on
the fence.
I'm hoping to test and upgrade to 3.0 this weekend.
I know. It's annoying. I hate to scrap a release, but I also dislike
having two releases so close together. And, if folks are going to be
testing -- wouldn't it be better to have them testing the latest and
greatest?
I am actually going with a strong -1 on ditching the 3.0 release. We
cannot continue to let our development outpace the release process. We
either need to speed up the release process, i.e. get from RC to release
faster, or slow it down so that our current process has time to happen.
My opinion is that our releases are taking way too long. 3.0 has been
in the RC process basically for a month, and I know it's a big release
but that's just too long. We need to be able to cut releases and get
them out faster than that.
I suggest that since 3.0 is not actually released yet that we probably
should not try and push a new 3.1 release.
-- Allen
- Dave
--a.
----- Original Message -----
From: "Dave" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Friday, October 20, 2006 7:58 AM
Subject: It's time for Roller 3.1 RC1
>I just upgraded my site to 3.1 and now I'm updating docs and preparing
> for Roller 3.1 RC1.
>
> I'd like to do the RC1 build today. Are we ready?
>
> Do we need a branch? I'd prefer to do one week of testing before
> creating a release branch. Does anybody have post-3.1 work that they
> need to do in the trunk? BTW, I intend to continue with
> sandbox/planetroller work in the trunk, but it's not included in the
> release so there should be no risk there.
>
> One one more thing. We're going to have simultaneous 3.0 and 3.1
> release candidates which, I'm sorry to say, begs the question --
> should we ditch the 3.0 release and go straight to 3.1?
>
> - Dave
>
