Dave wrote:
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 .
Well, then that's something we should discuss and figure out. If we
can't do monthly releases then we need to figure out what we can do.
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 agree that both of those are problems right now. Testing is a
marginal problem in my mind. I think there is time to do testing on a
monthly basis if the code changes are small enough and there is decent
communication about what changed. The other thing that seems strange is
that we need a certain # of votes instead of a certain % of votes. Why
would it be not okay if you, me, and Elias (who did pretty much all the
work for 3.1) represented most of the votes? I would expect that when
ppl don't have time to work on the project they don't participate and
the whole project can't just wait for them when that happens.
The PMC voting thing is a real drag. I don't know how to get past 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.
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.
Sorry, but did you read my other email where I listed 2 fairly
significant blocks to releasing an RC today? ..
1. I still plan to commit the independent hit tracking code.
2. The UI for the upload form is not working properly because I was
under the impression that we wanted to change it's semantics a bit. I
can reverse those changes, but the reason for doing this was that if we
release now allowing full hierarchy for uploads then we can't go back.
Ultimately I am fine with doing a 3.1 release. I prefer the monthly
release cycle and would like to see us speed up the release process so
that we can stick with it. I am -1 on an RC today because quite frankly
we aren't ready. It's not really a release candidate if you know there
are problems with it.
-- Allen
- Dave
