-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Project status, roadmap, 2.0? #337
Comments
There is a roadmap, but there is no time to achieve it. Most of the development was done while me and @cmd-ntrf were doing graduate studies. Now we are both occupied with tons of other projects. All contributions are welcomed. |
Hmm @fmder Maybe it's a good idea to release the current master as 1.3.0 or 1.2.3 at least, if you think the current master is stable? |
I'm working on something that would make 1.3 a real release. Stay tuned.
Le mar. 30 avr. 2019 10 h 52, Xiao Liang <notifications@github.com> a
écrit :
… Hmm @fmder <https://github.com/fmder> Maybe it's a good idea to release
the current master as 1.3.0 or 1.2.3 at least, if you think the current
master is stable?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#337 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAHKXQRZFPODTLPDN4DIVWLPTBMMLANCNFSM4HAVA4PQ>
.
|
Then I would suggest release the current master as 1.2.3 😂 The master contains a bunch of fixes since 1.2.2 as far as I can see. @fmder |
1.3.0 is out! Check out the new NSGA-III selection! |
What's the development status of deap? Is there a roadmap for next releases? Is there a plan or schedule for a 2.0 release?
The last release was around 1.5 years ago, 1.2.2 in Nov 2017. It looks like there has been some activity in the last few years but that it significantly dropped off a few years ago.
There are some open issues for a 2.0 milestone, but these haven't seen any activity for around 8 months to a couple of years.
The text was updated successfully, but these errors were encountered: