Two years ago today, we announced our Pinax distribution plan. Since Pinax is no one app or project but an ecosystem of applications that work together to make building new web applications fast and fun, having a distribution allows us to provide a known working set of compatible versions.
A lot has been happening these past two months in pinax-stripe. I wanted to take a moment between all the Pull Requests and provide an update of what’s on master pending a new release.
For years we have supported the same import ordering rules in our CONTRIBUTING.md files as part of the Pinax coding style. One feature of this was separate sections for both django and django.contrib. Time has come for that to change.
As it turns out managing templates in an external app for dozens of different apps across 11 different projects is quite a tedious process. We need something simpler. After all, necessity is the mother of invention.
With so many different projects in the Pinax ecosystem, we’ve long wanted to give each project a bit of their own identity. With this in mind, we’ve launched our first batch of Pinax Patches.
Since 2011, we’ve been packaging templates for Pinax apps inside pinax-theme-bootstrap. Over the
years we’ve moved more and more app templates that used to be bundled with the app into the theme.
Unfortunately, we are too coupled to specific Bootstrap versions.
Our third iteration in reducing the tooling overhead to support a decoupled static build process in our Django project templates is proving itself well.
Today we are excited to announce django-user-accounts
v2.0.0, with bug fixes, enhancements, and support for Django 1.10! Since this is a major version
release you can expect a few backward incompatibilities as well as exciting enhancements such as
automatic login after confirming email address and (optional) automatic password expiration.
This is the first story of our “My First Pull Request” series where we share stories of open source contributors and their first pull requests. Read more about it here.