-
-
Notifications
You must be signed in to change notification settings - Fork 13
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
Push a first release of the new aspen #2
Comments
I'm waiting for #20 to land before going ahead with this. I'll need PyPI access when the time comes. About the version number, I think that using 0.43 as you suggested in AspenWeb/pando.py#357 (comment) would only increase confusion. This isn't "just another release", it's such a massive change that we almost changed the name of the project to aspen-core. |
👍
Done (username Changaco, right?).
I guess I didn't understand whether 1.0 here referred to Aspen or Pando. How about going ahead with 1.0.0 for this next release of Aspen, with 1.0.0 for Pando to follow in September? |
Yep. I can confirm that I now have access.
I was talking about Aspen, not Pando. Here's my current thinking: Soon: Aspen 1.0rc1 (instead of 0.90), Pando 0.43 or 0.50 |
Sounds good. I like 1.0rc1 for Aspen. I'd pick 0.43 over 0.50 for Pando. |
1.0rc1 released. The README isn't being rendered correctly on PyPI, and the built wheel is python 3 only (we probably need a |
Done \o/ |
Porting pando to aspen (AspenWeb/pando.py#548) is complicated by the fact that the new aspen hasn't been released yet.
The text was updated successfully, but these errors were encountered: