The change list is completed - CHANGES.md shows the latest changes as of
last release - 2.2.0 in this case - i.e. all changes from 2.2.0 towards
2.3.0. The 2.2.0 file shows the changes from 2.1.0 to 2.2.0. Once you
release 2.3.0, I will create a separate file for the 2.2.0 to 2.3.0
changes
[
https://issues.apache.org/jira/browse/SSHD-930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16880192#comment-16880192
]
Goldstein Lyor commented on SSHD-930:
-
Done - see https://github.com/lgoldstein/mina-sshd/tree/SSHD-930
[
https://issues.apache.org/jira/browse/SSHD-930?focusedWorklogId=273210=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-273210
]
ASF GitHub Bot logged work on SSHD-930:
---
Author: ASF GitHub Bot
lgoldstein opened a new pull request #105: SSHD-930 Send the client version
string after receiving the version string of the server
URL: https://github.com/apache/mina-sshd/pull/105
Leave default to be same as current - i.e., immediate
[
https://issues.apache.org/jira/browse/SSHD-930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on SSHD-930 started by Goldstein Lyor.
---
> Send the client version string after receiving the version string of the
>
[
https://issues.apache.org/jira/browse/SSHD-930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Goldstein Lyor reassigned SSHD-930:
---
Assignee: Goldstein Lyor
> Send the client version string after receiving the version string
I think the change list has not been updated yet.
If I read SSHD-872 correctly, we're now using one file per version, which
is fine, but I don't see any file for 2.3.0, nor any file pointing to the
existing one for 2.2.0.
Also, I see that ~/CHANGES.md still exists and contains the 2.2.0 changes ?
