Spree 1.0.7 release?

45 views
Skip to first unread message

Anthony Batchelor

unread,
Aug 9, 2012, 9:54:00 AM8/9/12
to spree...@googlegroups.com
Hi,
  Does anyone know  when Spree 1.0.7 is planned for release?  We can't use < 1.0.5 due to insecurity, but 1.0.5 and 1.0.6 have a new bug to do with the date picker that are blocking us from release.  There are fixes in 1-0-stable that resolve this and other bugs.  Unfortunately, we can't just use the stable branch, as some development still seems to be going on in there and we need to fully test our site before putting the changes live.  Creating our own fork and maintaining that is less than ideal, we would like to avoid doing that if possible.

Also, is there anything we can do to help with the 1.0.7 release?

Kind Regards,
  Anthony Batchelor

Trung LE

unread,
Aug 9, 2012, 11:00:43 AM8/9/12
to spree...@googlegroups.com
Is there any problem of using 1-0-stable? As long as the branch 1-0-stable pass the Travis CI, you are safe to use it.

Trung LE
Sent with Sparrow

--
You received this message because you are subscribed to the Google Groups "Spree" group.
To view this discussion on the web visit https://groups.google.com/d/msg/spree-user/-/FbCPIALJ1oMJ.
To post to this group, send email to spree...@googlegroups.com.
To unsubscribe from this group, send email to spree-user+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/spree-user?hl=en.

Anthony Batchelor

unread,
Aug 10, 2012, 4:42:49 AM8/10/12
to spree...@googlegroups.com
The problem is that 1-0-stable is a moving target and not all bugs break on Travis CI. As an example, the date picker issue was not picked up by Travis CI.  

If we were releasing straight from stable we could get into a situation where we test against a version and sign-off on it (then someone commits something breaking to stable), then we deploy to live (with unknowingly broken code).

AB

Ryan Bigg

unread,
Aug 10, 2012, 6:21:43 AM8/10/12
to spree...@googlegroups.com
As long as you don't run bundle update on spree itself, the Gemfile will remain locked at a specific commit.
To view this discussion on the web visit https://groups.google.com/d/msg/spree-user/-/D2lN7tqVt4AJ.

Andrew Hooker

unread,
Aug 10, 2012, 8:09:47 AM8/10/12
to spree...@googlegroups.com
As a note, you can actually guarantee this behavior with the :ref designation in your Gemfile
gem 'spree', :git => 'git://github.com/spree/spree.git', :ref => '6d3f84c43'

Anthony Batchelor

unread,
Aug 10, 2012, 11:33:11 AM8/10/12
to spree...@googlegroups.com
This seems the next best option to having a 1.0.7 release
Reply all
Reply to author
Forward
0 new messages