The Solidus Blog

Announcing Solidus 2.8.0! Thanks to all contributors, testers, and users who made this release possible.

Canadian digital agency Stembolt was acquired late July by Juul Labs. Stembolt formally announced the acquisition earlier this year prior to Southeast Solidus. This has created a gap in leadership of Solidus. **We’re proud to announce that from December onward, Solidus is joining the growing list of open and sustainable communities partnering with [OpenCollective](https://opencollective.com/solidus).** We understand that many in the community may have been feeling unsure regarding the future of Solidus. Solidus and its community have always been strong. Through the strength of the community, a group of concerned individuals was formed. This group is inclusive of many retailers, agencies and long-term members of the community. Everyone in this group is deeply invested in the success of Solidus. Over many weeks we determined what we feel was the best path for the future of Solidus and have unanimously decided that Solidus should become an OpenCollective project. Since the beginning Solidus has enjoyed a vibrant and engaging community, we are happy to guarantee that this will continue, in addition, this paves the way for: - Continued maintenance - Adding new features - Security patches when required - Framework improvements - Future conferences - Securing the future of Solidus as a leading open source e-commerce framework. ##How You Can Help **While we are excited about this development, we are still looking for help from the community.** In an effort to facilitate this new direction, we are seeking: - A full-time contributor - Contributions to the platform and the #support channel - [Financial support](https://opencollective.com/solidus) - Case studies from Solidus retailers Thank you for your continued support, Solidus Stakeholders

You may have noticed that we rolled out a brand new look and feel to Solidus.io last month. We wanted a new site that better communicates Solidus' strengths as a platform. We hope that you agree that the new branding is more meaningful than what the old site offered.

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.