-
-
Notifications
You must be signed in to change notification settings - Fork 366
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Announce NUT_NETVERSION=1.3 #1336
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You know my thoughts on numeric protocol versions.
The other parts of the PR look fine.
I might have missed those thoughts in older context, so would try a guess:
should they be integer numbers? :)
I don't have a strong opinion here since NUT code itself does not make use
of the version (string?) AFAIK. But numbers would compare more easily :)
…On Thu, Mar 24, 2022, 02:43 Charles Lepple ***@***.***> wrote:
***@***.**** commented on this pull request.
You know my thoughts on numeric protocol versions.
The other parts of the PR look fine.
—
Reply to this email directly, view it on GitHub
<#1336 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAMPTFALUOP4YCFPEFMKG6DVBPCDTANCNFSM5RNIHR7A>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
If two network protocol upgrades are being discussed, and both branches in Git propose an incremented protocol version, one will have to be updated a second time to avoid a conflict if both are not merged at the same time. It seems like very little gain for a lot of maintenance burden. (And that's if Other protocols have text-based "feature flags" where they indicate a set of features that are supported. In all of the previous NUT protocol iterations, a client could simply try a new command, and check for an appropriate "ERR" response. |
Update the
configure.ac
to report the new version innetmisc.c
, and update docs that referred to "2.7.5" as the new release to speak about "2.8.0" which sings to similar tune as #1263.Also documents
PRIMARY
command as alias toMASTER
(per #840) in protocol 1.3, although the practical implementation is expected to be compatible with protocol 1.2 client/server (see #1328).CC @NUT-RogerPrice