News. Development and release plan.
See original GitHub issueTwo weeks ago I was given full permissions to this repository, as well as to readthedocs and pypy. I see that there is a very small interest in this project from developers, so several things will be changed soon. This is an announcement about these changes.
- At the Sunday version
1.7.0
will be released to pypy. It will be the current master, with maybe some not-code related changes. - This will be the last release with full code reviews from several core committers. Just because it delays development.
- The final release of
1.7.x
expected on December 31. Only bugfixes for1.7.0
will be reviews at this time.
New year plan.
The history of this project shows two things.
- It is self-full at this moment. I.e. it does the thing that supposes to do at this moment. All problems have some kinds of workarounds.
- Waiting for a sponsor is non-effective.
So the decision:
Let’s make something new. With honor and respect to the past.
- From January 1st and later master branch will include new changes that can be non-compatible with the old version but should introduce new functions.
- Fixes for the old version will be included in new releases of
1.7.x
, but only bugfixes for confirmed bugs will be included. All new development should be made in the new version2.0.x
- Contributors list for versions 1.x and 2.x will be separated in the documentation.
- Templates links will be removed from the main master page, as we cannot control templates live and security. I will try to create issue at every template branch, how to implement correct keywords for GitHub search.
- Most of the issues and pull requests will be closed or merged to 2.0.0 without waiting for contributors. Only live work should be at issues/pr page.
Feel free to comment on this issue. Every thought will be included in the development plan.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:12
- Comments:10 (6 by maintainers)
Top Results From Across the Web
What is Agile release planning? | monday.com Blog
Find out what Agile release planning is, and how to put it into action in your company with this complete step-by-step guide.
Read more >The Ultimate Guide to Creating A Successful Agile Release Plan
Agile release planning is a product management technique that helps you with your software development and agile project plan. It acts as a...
Read more >7 Steps To Create a Successful Release Plan - Medium
Agile release planning is the dynamic document that suggests the group of tasks you should accomplish before the release of your final product....
Read more >Agile Release Planning: 5 Best Practices For Developers
Agile release planning is a release management strategy where development teams plan incremental product releases. Unlike traditional software ...
Read more >Agile Release Planning: A Guide | ZenHub Blog
Agile release planning helps software teams make decisions about how much functionality can be delivered and how long it will take to develop...
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 FreeTop 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
Top GitHub Comments
All future planning will be in projects tab.
@geerlingguy No problem, but I saw this accidentally. I checked for new bugs before sleep, but you answered in old topic 😃 Please create issue next time. Thank you.