[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [glob2-devel] release policy
From: |
Kyle Lutze |
Subject: |
Re: [glob2-devel] release policy |
Date: |
Fri, 11 Aug 2006 20:18:29 -0700 |
User-agent: |
Thunderbird 1.5.0.5 (X11/20060731) |
Martin Voelkle wrote:
> That's what release candidates (RC) are for. Ideally, a release is the
> last RC without any modification.
> But you'd have to use branches to prevent people from commiting
> unwanted stuff on a RC.
>
> Martin
>
> On 8/10/06, Leo Wandersleb <address@hidden> wrote:
>> hi list
>>
>> to me it is bad practise to publicly announce a new release as soon as
>> we decided to release it. reasons:
>> we regularly find bugs just after releasing
>> release dates are when there is only source available. that's not
>> enough for our gamers community.
>>
>> i propose to make release versions ready and only announce the files
>> on this list and publicly announce it one week after the binaries for
>> at least mac, debian and windows have been completed. otherwise people
>> come and see how it goes and are frustrated as their platform doesn't
>> run smoothly or because they can't play against others as they have a
>> different version.
>>
>> greetings, leo
>>
>>
perhaps now is a good time for subversion over cvs? maybe that's just
because I know how to use subversion, and am just learning cvs though :)
Kyle