On 10/20/06, Allen Gilliland <[EMAIL PROTECTED]> wrote:
Dave wrote:
>> 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.
Still, testing takes time -- even if its just an install and a sanity
test. Henri, Anil and others can't always find the time to spend a
couple of hours testing a monthly release.
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.
It's time to make a push for graduation. See separate thread.
>> 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? ..
My fault. I didn't realize those would not be resolved today.
1. I still plan to commit the independent hit tracking code.
Good.
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.
Are we ready to expose a hierarchy to the users via the UI? Do we have
to do it now? I don't think we should do it without a proper UI and what we
have now is too limited.
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.
OK. I'll continue my doc and testing work and revisit this question Monday.
- Dave
