Russ Allbery wrote:
> 1.3.x is the development series for 1.4.  Nothing is going into the 1.3.x
> releases that isn't also going to go into 1.4 (to do so would be very
> confusing, since people upgrading from 1.3 to 1.4 would see features go
> away).
>
> These changes *could* be committed to the trunk right now, and if Jim
> decides to do that, I certainly don't object.  In general, though, the
> more stuff that's on the trunk that isn't targetted for 1.4, the more
> there is to keep track of and the more complicated it is to be sure that
> we got everything for the release.
> 
> I'm sitting on several patches that I plan to commit as soon as 1.4 is
> released and it feels safer for the trunk to start diverging from the
> stable release again.
>
> 1.4 has already been delayed for several months and needs to be released
> as soon as we sort out the last few bugs.  There is absolutely no way that
> I'm going to do major new work in 1.4 right now.  Sorry, you're just going
> to have to live with that.
> 
> Many of these sorts of changes should be eligible for 1.4.1 or 1.4.2.

I completely agree with Russ.   1.3.xx is feature frozen in preparation
for the 1.4.0 release.   Once 1.4.0 is gold we will start a 1.5.xx
series for new development.  It is possible that some new development
will be back ported to the 1.4.xx branch and appear in future 1.4 series
releases.   However, those changes in general are going to be few and
far between.

As for the need to have documentation.  I certainly agree that
documentation is great to have but the reality is that the software can
be frozen and then documentation can be written while the developers go
off and work on the next major release.   In fact, in some ways that is
just easier since the documentation folks don't need to worry about the
software changing out from underneath them.

Jeffrey Altman
begin:vcard
fn:Jeffrey Altman
n:Altman;Jeffrey
org:Secure Endpoints Inc.
adr:;;255 W 94TH ST PHB;NEW YORK;NY;10025;United States
email;internet:[EMAIL PROTECTED]
title:President
tel;work:+1 212 769-9018
x-mozilla-html:TRUE
url:http://www.secure-endpoints.com
version:2.1
end:vcard

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to