On 10/20/06, Allen Gilliland <[EMAIL PROTECTED]> wrote:
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.
Hmm. I've never been a big fan of monthly releases. I think it adds
too much "overhead" (e.g. updating docs, test, RCs) each month .
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.
There are at least two problems that hold up our releases:
- Folks on the mailing list don't have time to test releases
especially not on a monthly basis. And most folks don't want
to +1 a release that they have not tested.
- We must rely on Incubator PMC member to vote on releases
Graduation should basically fix that problem.
I suggest that since 3.0 is not actually released yet that we probably
should not try and push a new 3.1 release.
I'm definitely +1 on releasing 3.1 and doing an RC today. We're at a
good breaking point, we're ready for testing and Elias wants to get
tagging into a release now.
- Dave
