The Solidus Blog

We left technical conversations off the table when we posted the Solidus community roadmap. Now in this post, we'd like to focus on them. We'll discuss specific technical accomplishments and plans for Solidus 2.4 and 2.5 from a very technical perspective.

Previously, Solidus didn't have an explicit maintenance policy for previous versions. We're very security conscious, so for each previous security release we've released a patch simultaneously for all previous minor versions. As we've released more versions, this has become more difficult. Our last set of security patches (December 2017) required 10 new releases, which is way too many. However we don't want to surprise users by announcing an issue with no easy patch available to them. To allow us to patch security issues promptly, and to make sure developers know how long their Solidus version will receive security updates, we're introducing the following End of Life policy: Solidus versions will receive security patches for 18 months following their initial release. Versions which would hit their EOL before May 5th, 2018 (4 months from the date of this announcement) will receive security patches until May 5th, 2018. This applies to Solidus 1.0 through 2.0. Under this policy, versions will be supported until the following dates:  

Since we forked Spree three years ago, we’ve been heads down, working through the project's technical direction. We’re very proud of our technical progress over the last three years and have a concrete plan for continued success.

Announcing Solidus 2.3.0! This is our first release to use Rails 5.1. This also includes over 30 pull requests from the SolidusConf 2017 Hack Days.

Since forking Spree we’ve been so busy putting together our 5329 artisanally-crafted solidus core commits, we often forget to stick our head out of our git logs and talk about where we are and where we’re going.

We've released a new version of solidus_gateway (1.2.0) to address a security vulnerability. We recommend all users of solidus_gateway or spree_gateway upgrade immediately or use our provided workaround.

SolidusConf speaker Martin Tomov: My name is Martin Tomov, I am a full stack developer working primarily on ecommerce projects for Boomer Digital. I am based in London, UK.

SolidusConf speaker Clarke Brunsdon: I'm one of the Solidus core team members and one of the founders of Stembolt. I've been a developer for the last 17 years, though nowadays I write more emails than code.

SolidusConf 2017 speaker denis sellu: My name is Denis Sellu, I live in Bristol and work for CookiesHQ.

My name is Brian Buchalter and I work at Tommy John, a menswear brand that specialises in underwear. I've been working remotely on Rails-based projects for 11 years and on Spree stores for 4 years. I live on a small island in the Caribbean with my family of four.

Announcing Solidus 2.2.0! This release includes better support for non-credit-card payment sources, better promotion creation, and many other great changes.

Solidusconf 2017 Speaker Alex Stoica: I’m Alex, a backend developer at Lost My Name. I’ve worked here for just under three years now, while studying towards my Computer Science degree from King’s College London.