Next release items

[Justin Sherrill]

I don't think anyone is using the two in conjunction - so just document.

On Mon, Oct 20, 2014 at 8:50 PM, Zachary Crownover <
zachary.crownover at gmail.com> wrote:

> Do tcpwrappers need to be updated at all with changes to the OpenSSH or
> just documentation updated to show that they're not compatible with the new
> OpenSSH release?
>
> On Mon, Oct 20, 2014 at 5:00 PM, Justin Sherrill <
> justin at shiningsilence.com> wrote:
>
>> Dangit, I even had "6.7" in my head.  This is very helpful.
>>
>> With this stuff added, it sounds like a release candidate should be
>> buildable later this week.
>>
>> On Mon, Oct 20, 2014 at 7:52 PM, Robin Hahling <
>> robin.hahling at gw-computing.net> wrote:
>>
>>> On Monday 20 October 2014 19.42:25 Justin Sherrill wrote:
>>> > Here's my mental list of things-before-the-next-release:
>>> >
>>> > - OpenSSH update (to 6.5)
>>> > - OpenSSL update (version J)
>>> > - ftigeot's drm1 cleanout
>>> > - Testing of Matt's /dev/upmap, /dev/kpmap changes
>>> >
>>> > Anyone want to volunteer to get the Open* material in?  The testing on
>>> the
>>> > last one is for anyone using -master; Postgres may be a good testcase.
>>>
>>> I'm almost done with the OpenSSH update (which is from 6.1 to 6.7 and
>>> not 6.5
>>> btw). I hope to find enough time to finish this tomorrow but at least it
>>> should
>>> be done before the end of the week.
>>>
>>> As for the OpenSSL update, I think Sasha already started something (at
>>> least
>>> he planned to). If no one is working on updating it, I can volunteer to
>>> do it
>>> as well (after the OpenSSH update). It usually is not a big deal when it
>>> comes
>>> to a security fix release update.
>>>
>>
>>
>
>
> --
> Sincerely,
>
> Zachary Crownover
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.dragonflybsd.org/pipermail/kernel/attachments/20141020/b45503e1/attachment-0002.html>