release schedules (was Re: hosting an internal macports server with binaries)

Paul Guyot pguyot at kallisys.net
Tue May 8 01:57:00 PDT 2007


On May 8, 2007, at 12:17 PM, James Berry wrote:

>>> However, this functionality is broken in 1.4.3. This bug was  
>>> fixed three weeks ago, but the people in charge here think we  
>>> should not make too often releases, so you'll have to use trunk  
>>> or wait for the fix.
>>
>> I'm sure this has been discussed elsewhere but if this was a  
>> democracy, I would vote for more frequent/regular releases,  
>> especially if as alluded above, there is some breakage that can be  
>> fixed. I know we just went through a messy release of 1.4.[0123]  
>> but if the swelling has gone down from that one, when do you think  
>> the next release will be?
>
> I'm all for frequent releases, and have just been waiting for a bit  
> of time in my schedule, and concurrence from others, to make a  
> release. I don't think Paul is being quite fair.

I do not think that you should do releases more frequently, because I  
know this takes a lot of time. I was not criticizing the fact that  
you did not release 1.4.40 three weeks ago when the fix was committed.

Our infrastructure (language, user base, supported operating systems,  
developers) is such that having very frequent releases is the best  
policy, something I think you agree with, but jmpp@ disagrees with.

Yet, you, jmpp@ or whoever who could do releases are way too busy to  
do them. And if we are not busy, it's a waste of time compared to  
other MacPorts-related tasks, such as mwpa for example.

Consequently, I believe that we simply should not have releases at  
all, until we have some form of continuous integration.

Paul
-- 
http://paul-guyot.com/




More information about the macports-users mailing list