ozpos
commented
10 years ago Why not lock it down now to the version of rails you know is OK. If someone wishes to use it with a more recent version then they can fork/branch and give back any changes ?
Closed iox closed 9 years ago
ozpos
commented
10 years ago Why not lock it down now to the version of rails you know is OK. If someone wishes to use it with a more recent version then they can fork/branch and give back any changes ?
ozpos
commented
10 years ago Just came accross travis-ci. Looks like the testing can be automated with real-time feedback.
It allows you to script the tests using ruby, shell scripts or executables and setup the environment (ruby version, build tools etc). It would be easy to montecarlow several ruby versions against several rails versions.
iox
commented
10 years ago Yes, travis-ci, codeship or a similar tool would be very very interesting for us, so we could ensure that the tests are running fine all the time.
About the Rails version, the main issue is the Rails security updates. Developers usually want to update their applications very fast when a new Rails bug is discovered. That's why we would need to keep Hobo in sync very quickly.
ozpos
commented
10 years ago That's just what the 'Boxed'/'Pessimistic' version operator is for. gem rails, '~> 3.2.10' will match 3.2.10 to 3.2.xxx
On 08/10/14 07:24, Ignacio Huerta wrote:
Yes, travis-ci, codeship or a similar tool would be very very interesting for us, so we could ensure that the tests are running fine all the time.
About the Rails version, the main issue is the Rails security updates. Developers usually want to update their applications very fast when a new Rails bug is discovered. That's why we would need to keep Hobo in sync very quickly.
— Reply to this email directly or view it on GitHub https://github.com/Hobo/hobo/issues/124#issuecomment-58315632.
iox
commented
10 years ago Hmm, that sounds like the perfect solution, thanks :).
ozpos
commented
10 years ago What version should be set for master ? On 08/10/14 12:22, Ignacio Huerta wrote:
Hmm, that sounds like the perfect solution, thanks :).
— Reply to this email directly or view it on GitHub https://github.com/Hobo/hobo/issues/124#issuecomment-58343440.
iox
commented
10 years ago Latest 4.0.x
iox
commented
9 years ago Note: now master branch supports Rails 4.2
iox
commented
9 years ago I think this was solved by #97
This is an idea for the future:
It would be great if we could specify a specific Rails version to use with Hobo. That would mean having someone responsible of testing new Rails releases and releasing a Hobo update, but would also save us a lot of trouble when a Rails change breaks Hobo.