-
Notifications
You must be signed in to change notification settings - Fork 290
Project is not dead! #152
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
Comments
You may have received one or mail mail linked to this issue/announcement, just for a first feedback. Your emails are now filed in my gmail with Please be patient you'll receive a better reply. Regards. |
I'm going to close this issue, but feel free to add comments. |
Re-open, for visibility... |
👍 |
Thank you for voting up! If you think some PR or ISSUE should have precedence please tell, so a discussion can start. |
Not at the moment, @Nate-Wilkins, but is an interesting feature and will be when trunk stabilizes. The issue you pointed out is probably thought for latest stable, but I'm currently working on 2.0 pre-rel, which will not be abandoned. Backing to the feature, when finished with PR (as you can see from GitHub activity, I'm really back to work): I'll try to catch up with issue. Thank you for expressing your preference on feature requests. Stay tuned. Regards. PS:
|
Ok, but I think now it is dead. |
I apologize for not being able to coordinate issues, pull requests and for not replying to all emails.
I was very engaged in various heavy and challenging projects around Europe.
I next days (or may be weeks) I'll try to catch up with everything...
For now I repeat what I've said to few (of many, sorry) emails I've replied: please use the consolidated code base of latest stable on branch stable-1.9.71.2.
At the moment I can't make any preview for the future: maybe the new pre-release 2.0.0.0 (actual master branch) will be discarded, maybe not or maybe both versions will go ahead together. As always suggestions are welcome.EDIT
EDIT 2
Regards,
Giacomo Stelluti Scala
The text was updated successfully, but these errors were encountered: