19990120 is the end of 2.x?

19990120 is the end of 2.x?

Post by Louis Epste » Wed, 03 Feb 1999 04:00:00



Just verifying that that SNAP(should it be called 2.2.8.1?)
is the end of the branch?
 
 
 

19990120 is the end of 2.x?

Post by Steven G. Kar » Wed, 03 Feb 1999 04:00:00




Quote:> Just verifying that that SNAP(should it be called 2.2.8.1?)
> is the end of the branch?

Why do you draw that conclusion?

If some really * bug is found in 2.2.8.x (such as major
security problem), then a patch will be committed to the
2.2.8.x branch and released for general consumption.  Will
a new release, 2.2.8.y, be generated and distributed by Walnut
Creek.  Probably not.

Will there general development and back porting of 3.x enhancements?
No.

--
Steve

 
 
 

19990120 is the end of 2.x?

Post by Louis Epste » Thu, 04 Feb 1999 04:00:00





: > Just verifying that that SNAP(should it be called 2.2.8.1?)
: > is the end of the branch?
:
: Why do you draw that conclusion?
:
: If some really * bug is found in 2.2.8.x (such as major
: security problem), then a patch will be committed to the
: 2.2.8.x branch and released for general consumption.  Will
: a new release, 2.2.8.y, be generated and distributed by Walnut
: Creek.  Probably not.

I don't expect it to be CDROMmed,but would it be maintained
on the ftp.freebsd.org servers?2.1.7.1-RELEASE disappeared
after a while,with no real declaration as to when fixes would
no longer be offered anywhere...just a vague statement that
only desperately needed bugfixes would still be done on RELENG_2_1
as of some time before the disappearance.

Just when there is a "final state" seems a useful point.

: Will there general development and back porting of 3.x enhancements?
: No.

Didn't expect so.

 
 
 

19990120 is the end of 2.x?

Post by Steven G. Kar » Thu, 04 Feb 1999 04:00:00







>: > Just verifying that that SNAP(should it be called 2.2.8.1?)
>: > is the end of the branch?
>:
>: Why do you draw that conclusion?
>:
>: If some really * bug is found in 2.2.8.x (such as major
>: security problem), then a patch will be committed to the
>: 2.2.8.x branch and released for general consumption.  Will
>: a new release, 2.2.8.y, be generated and distributed by Walnut
>: Creek.  Probably not.

> I don't expect it to be CDROMmed,but would it be maintained
> on the ftp.freebsd.org servers?2.1.7.1-RELEASE disappeared
> after a while,with no real declaration as to when fixes would
> no longer be offered anywhere...just a vague statement that
> only desperately needed bugfixes would still be done on RELENG_2_1
> as of some time before the disappearance.

Checkout cvsup.  You should be able to pull down the 2.1.7.1-RELEASE
if you know the repository tag.  Again, checkout cvsup and
share/examples/cvsup which list valid tags.

--
Steve


http://www.veryComputer.com/~kargl/sgk.html