Spree 1.1.1 has been released. This release is just a minor patch release to fix a few issues with the previous release. There are no security fixes in this release so there is no rush to upgrade if things are working fine for you.
The primary reason to upgrade is if you are experiencing issues with the new 2.1.x version of Devise which may get used by bundler in new Spree deployments. Please see the Github compare for a complete list of changes in this release.
At the beginning of the year we held our first ever SpreeConf in NYC. The conference was a huge success and we announced our plans to hold our first SpreeConf Europe on August 22-23 in Dublin, Ireland.
Today we’re pleased to announce the details of the conference including a full schedule of awesome speakers. In keeping with our tradition of holding the conference in unique venues, this conference will be held in the very awesome Guinness Storehouse. The official conference hotel is conveniently located in the city center with easy access to restaurants and tourists attractions. There is also free transportation between the hotel and conference thanks to our friends at Klarna.
Ticket prices are only €100 and include two full days of conference activities including the following:
We’re also working on scheduling an after party in the world famous Gravity Bar.
We also have a special deal for people who like to book early. Conference registration is only €50 for the first fifty registrants. That’s a 50% discount off an already reasonable price! Our last conference sold out quickly so act now and secure your spot at this amazing conference!
We’d also like to welcome Contegix as our primary sponsor for the conference. Contegix is a strategic cloud computing and managed hosting company and they are the preferred hosting company for several large-scale e-commerce deployments.
Spree 1.1.0 has been released. We’ve been hard at work the past two months getting this release ready. This is also the first Spree release to support Rails 3.2.×. All it took was 790 commits by 34 different authors (including many first-time committers.)
Here’s a list of highlights of what is contained in the new release:
Please see the Github compare for a complete list of changes in this release. Please see the Spree 1.1.0 release notes for more details.
Spree 1.0.4 has been released. This is just a minor patch release that contains several minor fixes made since the prior release. There are no security fixes contained in the release so there’s no need to upgrade unless you’re experiencing one of the problems fixed in this release.
Please see the Github compare for a complete list of changes in this release. If your store is not yet running on a 1.0.x version of Spree you are encouraged to upgrade at your earliest convenience. Once Spree 1.1.0 is released we will no longer be maintaining versions of Spree prior to 1.0.x except in the case of a critical security fix.
We have just released Spree 1.1.rc2! In this version, you’ll find bug fixes for bugs detected within the first release candidate, as well as some refactoring. Pending any other issues brought up on the Spree issues, this will be the final release candidate before the actual release.
Probably the most substantial change from this release candidate is the clean up of the Creditcard class. We don’t anticipate any problems with these changes, but if you do find some, please bring them up on the Spree issues page.
If you want to see all the changes that have gone into this second release candidate since the first, be sure to check out the comparison view on GitHub.
One final note, both the Railsdog and Spree teams are at Railsconf this week! Come find us and talk to us about how you’re using Spree.
Spree 1.1.0 is now available as a release candidate (rc1.) This means that the official release is imminent and we request your assistance in testing the code before we do so. As part of this process we have created a new 1-1-stable branch in Github. As the branch name implies, the code in this branch should stay fairly stable over time as we move towards and beyond the 1.1 release.
What’s in the Upcoming Release?
Please see the edge version of the release notes for more details
Using the RC in your project
Since the spree_cmd gem defaults to the latest official releases for Spree (and the associated payment gateway gems), it is recommended that you use the following approach to install the RC in a new project:
spree install mystore --git=git://github.com/spree/spree.git --branch=1-1-stable
For existing stores you can follow the standard process of updating your Gemfile
gem 'spree', '1.1.0.rc1'
and then install and run the migrations
bundle exec rake spree:install:migrations bundle exec rake db:migrate
A couple of weeks ago I went down to the Rackspace office and sat down for a quick interview with Robert Scoble.
We also had a good discussion about Spree and took an in-depth look at the new Deployment Service. For me the highlight was showing off the new live editor functionality. The editor stuff is not yet publicly available but you can sign up for beta access now if you’re interested.
This year is shaping up to be another year of tremendous growth in the Spree community with an ever growing number of awesome contributors helping out with the effort. We also held our first ever SpreeConf where I presented a talk on the Spree Road Map. It has been a month since that talk so I thought I would update everyone on how things are progressing and what we have planned for later this year.
The Spree 1.1 release is right around the corner. We’re scheduled to announce the first release candidate later this week. This release should be a relatively painless upgraade if you’re already running Spree 1.0.×. Spree 1.1 will include support for Rails 3.2.x as well as some minor improvements that were not urgent enough to include in the Spree 1.0.x patch releases. Expect the final release to occur during the first week of April.
The Spree 1.2 release will focus on the much anticipated admin redesign. We will be reorganizing some of the admin screens to improve usability as well as putting a fresh coat of paint on things and making the admin functionality easier to customize. We already have a ton of mockups for how the admin might look but the design is not final. Work on the admin will begin later this month and commits will start showing up in the master branch within a couple of weeks.
The first improvement to our website will be the addition of a new forum system. Its based heavily on the forem project created by our very own community manager (Ryan Bigg.) It will have the ability to upvote answers and for people to mark their questions as answered. This will help us keep better track of the unanswered questions out there. Go ahead and create your Spree account now so you’re ready to participate!
During our first SpreeConf we also announced our plans for a SpreeConf Europe later this summer. The conference will be on August 22-23 in Dublin, Ireland. We’re going to announce the details shortly and there will be a large discount for early registration. Hope to see everyone there!
Spree 1.0.3 has been released. The primary purpose of this release is to address a recently discovered security vulnerability which under certain circumstances allows any authenticated user to read the contents of another user’s order.
Please see the Github compare for a complete list of changes in this release. Due to this issue and other previously announced vulnerabilities you should upgrade to this version of Spree if you are running a prior version of Spree 1.0.×.
NOTE: Earlier this week we released Spree 1.0.2 which contained this fix. Before we could write up the release announcement we discovered a newly introduce bug that required a quick follow up release which is now Spree 1.0.3. It is recommened that you update to version 1.0.3 if you are running version 1.0.2 because of this bug but it is not required for security purposes.
Spree 0.70.5 has been released. The primary purpose of this release is to address a recently discovered security vulnerability which under certain circumstances allows any authenticated user to read the contents of another user’s order.
Please see the Github compare for a complete list of changes in this release. Due to this issue and other previously announced vulnerabilities you should upgrade to this version of Spree if you are running a previous 0.70.x version of Spree.
This project is maintained by a core team of developers and is freely available for commercial use under the terms of the New BSD License.
Spree, Spree Commerce and the Spree logo are all trademarks of Spree Commerce, Inc.
Subscribe via RSS