Hi decided it's time to upgrade so went with the git open and just
realized I grabbed 2.8.0 instead of the 2.7.x branch. Are there any
gotchyas going from 2.6.5 and 2.8.0 and is it stable enough or should I
stick with 2.7? I'm no stranger to cutting else releases so I don't
mind trying it.

Thanks,


--
End Of The Line BBS - Plano, TX
telnet endofthelinebbs.com 23

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi Nigel,

decided it's time to upgrade so went with the git open and just
realized I grabbed 2.8.0 instead of the 2.7.x branch. Are there any
gotchyas going from 2.6.5 and 2.8.0 and is it stable enough or should I
stick with 2.7?

Using CURRENT INN 2.8.0 is fine, it is as stable as the STABLE branch
2.7.x. There's not much development these days on INN; what is
committed on CURRENT can be considered stable and already tested by the committer. Usually, the changes are merged a few days or weeks after in
the STABLE branch. (The time to check that my news server still works
as expected.)

Have a look at the "Upgrading from 2.6 to 2.7" section at:
https://www.eyrie.org/~eagle/software/inn/docs/news.html

It applies to an upgrade from 2.6.5 to 2.8.0.

I'm no stranger to cutting edge releases so I don't mind trying it.

At that time, 2.8.0 does not really contain new features to test. Maybe
later this year or next year, I'll have a look at implementing RFC 3977
in innfeed (at last!) and integrate libevent to have native TLS and
COMPRESS support in innd and innfeed. It may introduce regressions but
I'll do my best not to break things ^^

--
Julien ÉLIE

« L'art de la médecine consiste à distraire le malade pendant que la
nature le guérit. » (Voltaire)

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Thu, 9 Mar 2023 20:14:19 +0100
Julien ÉLIE <[email protected]d> wrote:

Hi Nigel,

decided it's time to upgrade so went with the git open and just
realized I grabbed 2.8.0 instead of the 2.7.x branch. Are there any gotchyas going from 2.6.5 and 2.8.0 and is it stable enough or
should I stick with 2.7?

Using CURRENT INN 2.8.0 is fine, it is as stable as the STABLE branch
2.7.x. There's not much development these days on INN; what is
committed on CURRENT can be considered stable and already tested by
the committer. Usually, the changes are merged a few days or weeks
after in the STABLE branch. (The time to check that my news server
still works as expected.)

Have a look at the "Upgrading from 2.6 to 2.7" section at:
https://www.eyrie.org/~eagle/software/inn/docs/news.html

It applies to an upgrade from 2.6.5 to 2.8.0.

I'm no stranger to cutting edge releases so I don't mind trying it.

At that time, 2.8.0 does not really contain new features to test.
Maybe later this year or next year, I'll have a look at implementing
RFC 3977 in innfeed (at last!) and integrate libevent to have native
TLS and COMPRESS support in innd and innfeed. It may introduce
regressions but I'll do my best not to break things ^^

Thank you for this. I have upgraded to the latest 2.8 on git as of last
week and it seems to be running fine.

Thanks,

--
End Of The Line BBS - Plano, TX
telnet endofthelinebbs.com 23

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)