Skip to content
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

Toward v4.2.0 #265

Closed
kaizu opened this issue Jun 12, 2018 · 5 comments
Closed

Toward v4.2.0 #265

kaizu opened this issue Jun 12, 2018 · 5 comments
Assignees
Labels
Milestone

Comments

@kaizu
Copy link
Member

kaizu commented Jun 12, 2018

No description provided.

@kaizu kaizu added this to the v4.x.0 milestone Jun 12, 2018
@kaizu kaizu added the proposal label Jun 12, 2018
@kaizu kaizu assigned kaizu and kozo2 Jun 12, 2018
@kaizu kaizu changed the title v4.2.0 Toward v4.2.0 Jun 12, 2018
@kaizu
Copy link
Member Author

kaizu commented Jun 12, 2018

Changes in the release policy:

  • Only support Python the latest v3 64bit
  • v2 and the old v3s are optionally supported only on Linux.

How about conda? #260

@kaizu
Copy link
Member Author

kaizu commented Jun 12, 2018

Changes in the version of C++ used:

  • C++11 is allowed.
  • Use std::unordered_map. Forget boost/tr1.
  • Switch to STL smart pointers?
  • Use the latest version of Boost, if possible

@kaizu
Copy link
Member Author

kaizu commented Jun 12, 2018

New and deprecated features:

kozo2 added a commit that referenced this issue Jun 13, 2018
Only support Python the latest v3 64bit #265
@kaizu
Copy link
Member Author

kaizu commented Jun 14, 2018

@kaizu
Copy link
Member Author

kaizu commented Mar 3, 2019

v4.2.0 is now replaced with v1.0 due to the new version scheme (see also #331).

@kozo2 Please check if all is done and close this issue.

@kozo2 kozo2 closed this as completed Jun 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants