v0.1.0 Roadmap
See original GitHub issueThere seems to be enough activity on this repo to try and move forward with a release version of the community version of manim. For this, let’s use this issue to keep track of what needs to be done and when. Logistically, this should be the last issue to be closed in the v1.0.0 milestone, and once this one is closed, we should be able to push to pypi.
Things that need to be discussed
- I think there is a sense among @ManimCommunity/core devs that v1.0.0 should be fully backwards compatible. This has not been fully discussed, however.
- For full backwards compatibility, we need to determmine a timeline for deprecation.
- It has been decided that this repo will have both
manimandmanimcmas entrypoints. Some of us have started calling it manim CE (for Community Edition). Personally, I like “manim CE” as a name (and the accompanyingmanimceentrypoint) more than “manimcm”. Though I don’t ultimately care either way… - I think it would be nice to have a logo at the time of release #106
Things that need to be implemented
~Get rid of CONFIG dicts in each class and migrate to dataclasses #7~
-
Add extensive tests #133 -
Add documentation #103 #38 #104 with sphinix on ReadTheDocs #38, including a quickstart #120 -
Migrate configuration toconfigparserand cascading.cfgfiles #98. -
Clean upconstants.py#98. -
Make a logo #106 - There are a bunch of things that depend on #7,
#98, and#133, so we have to determine whether each one of those are required for a v1.0.0. -
Add a Scene Cacher #166 -
Additional documentation examples #458 -
Various small improvements #489, #490, #492, #496, #498 - Automate publishing to pypi
#500 - Update the README image containing an example command #572
Please feel free to edit this issue to add/remove/check off things as you see fit.
After the release
- make PangoText the default backend of Text (#487)
- invite developers of other manim-related projects to become part of the organization (or at least ask them to support manim CE). For example: https://github.com/krassowski/jupyter-manim
Issue Analytics
- State:
- Created 3 years ago
- Reactions:5
- Comments:14 (14 by maintainers)
Top Results From Across the Web
v0.1.0 roadmap · Issue #20 · frozenpandaman/s3s · GitHub
I'm not using GitHub's "projects" feature so this is going to sit as an open issue. :D v0.1.0 roadmap Upload to stat.ink! Get...
Read more >Daily Notes Release - Changelog v0.1.0
Daily Notes Release - Changelog v0.1.0 ... We're so excited for what's on the roadmap. Feel free to respond here if you have...
Read more >Development Road Map - Mealie - GitHub Pages
Development Road Map. Feature Requests. See the Github META issue for tracking feature requests. Progress. See the Github Projects to see what is...
Read more >PIG 5 - Gammapy 1.0 roadmap
Abstract#. This PIG describes the required short- and medium-term development work up to the Gammapy 1.0 release. The anticipated time scale for this ......
Read more >Releases and Roadmaps - SODA Foundation Documentation
SODA Releases and Roadmap. ... First SODA Foundation release v0.20.0 ... Zealand (v0.1.0). This is the v0.1.0 release of OpenSDS ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Folks, it seems we have completed every item on the list except for the logo, which should be decided upon by Tuesday Oct 20th noon GMT. I suggest we add the logo and also fix #407 and then release this bad boi. Objections? Comments? @ManimCommunity/core
If there are no objections, I move we put a freeze on PRs right now.
Just updated the check list at the top. Please refer to it for what to do next.