The top priority in writing code for Crabgrass is to make something that someone else will be able to understand, maintain, and debug long after you are gone.
Autumn 2014 – Finalizing Core Rework¶
We’ve had a number of small pushes throughout the last years to finish the core rework we started in 2011 (omg). However – while it always felt like we were almost done we never managed to finish it.
Now we’re pushing forward again with azul working on crabgrass for 6 month.
Here’s a list of the major changes and a development roadmap for the upcoming months
September – upgrade¶
We’re still way behind the main rails development. That leads to lack of security fixes and improving code that will have to be rewritten for newer versions of rails.
result: we now depend on rails 3.2 which will see security updates until rails 5 is released next summer.
October & November – security and bugfixes¶
Besides the version upgrades there’s a number of things we can do to improve the overall security. In particular I will look into locking down the routes to the minimum required and using strong_parameters.
At the beginning of December we will release 0.6.0.beta.
December – test, customize and prepare¶
There’s quite a bit of customization on we.riseup.net and there’s a new server ready to be used for it. So in December I will focus on customizing a deploy for that server and test all the functionality thoroughly fixing bugs as they are found.
Help with testing by a small team will be very much appreciated at that point. At the end of December we will release 0.6.0
January – deploy to we.riseup.net¶
After the deploy development cycles will be much shorter to fix bugs quickly once they are reported. I’m planning weekly releases of 0.6.1 to 0.6.4.
Since rails 3.2 will not be supported anymore I’ll also work on an 0.7.0 release based on rails 4.
Recent Pages • More »
Recent Activity from Your Groups in Crabgrass Dev Network