>>>>> OKUJI Yoshinori writes:
OY> Gordon, please maintain the prepare_0_5_96 branch, and release it
OY> as 0.5.96 once it is stabilized enough.
[...]
OY> Another thing I'd like you to do is to emphasize that 0.5.96 is
OY> the _final_ test release when you anno
From: Alessandro Rubini <[EMAIL PROTECTED]>
Subject: Re: prepare_0_5_96
Date: Mon, 2 Oct 2000 10:28:22 +0200
> Again, sorry if my words looked harsh. I should have dropped the "in 2004"
> above. I'm not complaining that development is slow.
I'm not angry wit
> 3. I then merge the change on the branch with the main trunk.
Ok, I missed that pass. Sorry.
>> Then, 0.6 is planned for December and after that the cross-platform rewrite?
>> Or is the cross-platform stuff planned after 1.0, in 2004?
>
> I hope that the former will be true, but I don't kn
From: Alessandro Rubini <[EMAIL PROTECTED]>
Subject: Re: prepare_0_5_96
Date: Mon, 2 Oct 2000 00:11:53 +0200
> I disagree. Why should the docs get synced only for this release and
> remain outdated in the main trunk? I know work is often duplicated by
> chance, but duplicating
> Bug fixes and doc updates will only be allowed for pre-0.5.96, and
> new features should be applied only to the main trunk.
I disagree. Why should the docs get synced only for this release and
remain outdated in the main trunk? I know work is often duplicated by
chance, but duplicating it by d
Although I don't know how stable the current is, I have added a tag,
"prepare_0_5_96" into the CVS. Bug fixes and doc updates will only be
allowed for pre-0.5.96, and new features should be applied only to the
main trunk. Gordon, please maintain the prepare_0_5_96 branch, an
