Creation of a to-do list for the next 2.3 release and update milestone list

[eldemet]

It has already been 5 years since our previous release, and a large number of important and exciting commits have been made towards the new version.

Shall we create a To-do like we did for the 2.2 version, to set the roadmap for the next release?

Also we probably need to update (add/remove) issues associated with the 2.3 milestone (currently there are some old issues pending there, and many are missing).

@LRossman @eladsal @samhatchett let me know what you think.

Demetris (@eldemet)

[LRossman]

@eldemet I totally agree. Let's get the ball rolling for a v.2.3 release!

[eldemet]

That's great @LRossman, I've tried to create a roadmap, like the one we used for 2.2. @eladsal, @samhatchett, @LRossman please let me know if I have missed something.

• Check open issues which were assigned to Milestone 2.3 in the past. Close issues that have been resolved, or decide to more to 2.4.
• Check other open issues, if they have been resolved or if there are any bugs that need to be resolved for the 2.3 version, or decide if they need to go to 2.4 release.
• Update "2.2" references in the code to "2.3" where appropriate
• merge dev into master
• Update list of authors
• Update gh-pages
• Update & check release notes
• Check and update dox documentation
• Update the PDF User's Manual and the read-the-docs
• Announce release candidate, for user feedback. Build shared libraries to allow user checks on different operating systems (Windows/Linux/MacOS), compatibility with external toolkits (e.g., MATLAB, Python, R, etc.)
• Collect feedback and respond to any issues.
• Finalize and publish release