If you have visited the Sanic GitHub, you may have noticed something different.
Sanic is now a community driven organization!
A great deal of thanks goes out to the men and women that built Sanic when it was an individual repository. Sanic is now in the hands of the community to work together to push it forward and keep it going fast.
Here are some changes you will see:
Versioning and release schedule
Calendar versioning promotes regularity. The goal of the Sanic project is to move fast. To accomplish this as a group (and not just in the benchmarks) we are adopting a cycle of 4 releases per year. They will be evenly spaced every three months (March, June, September, December).
Next release date
The next release will happen in December 2018.
The December releases will be marked as
LTS (aka Long-Term Support). This means that the team will continue to push bug and security fixes so long as that version is supported. Any non-LTS release will be supported up until the next release.
For this first community-backed release, the team is going through the backlog of issues and PRs to merge what we can to make "small" changes and fixes. The goal is to cleanup the project where we can, increase the testing coverage, and begin the first LTS cycle with a solid build.
We are still working through to decide what will be included, but you can expect a feature freeze in the next month or so.
We are adopting a strategy of naming a year long position of "release manager", or "RM". The main job of the RM is to keep the core dev team and the community moving towards the release dates. They will lead the charge in identifying and scheduling features, bug fixes and enhancements into the release calendar.
It is with great pleasure that we announce the 2019 Release Managers:
Yun and Stephen will be overseeing the next four releases of Sanic: 18.12-LTS, 19.3, 19.6, and 19.9.
Good luck to Yun and Stephen, and thanks for stepping up!
How will this impact me?
The short answer is that it shouldn't. You should receive more regular updates, but the package itself will not be changing course.
If you have contributed in the past, thanks! We welcome more contributions.
How can I help?
Sanic aims to be a community run project. Therefore, we always are looking for contributors from the people that are using it.
But, we need thought contributors too, so responding to issues with positive commentary is also very welcome.
But, I have never helped on an open source project before...
So what. All skill levels of pythonistas are welcome. Whether you are able to help diagnose bugs, build new features, write documentation, or even just engage in conversations on GitHub, we'd love to have your support. Maybe you would like to help us build this site up, or maybe you would like to start writing content (blogs, videos, tutorials). It all counts and it all matters.
You can also check out our development mailing list.
We look forward to your thoughts and help!