Skip to content

Commit 312d071

Browse files
committed
Updates dev documentation
1 parent 794e7f4 commit 312d071

File tree

1 file changed

+17
-3
lines changed

1 file changed

+17
-3
lines changed

Diff for: doc/meta.md

+17-3
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,6 @@ I use the gem-release gem
55
For more info see: https://github.com/svenfuchs/gem-release#usage
66

77

8-
98
## Steps for an update
109

1110
1. Update code and commit it.
@@ -22,11 +21,26 @@ For more info see: https://github.com/svenfuchs/gem-release#usage
2221
`gem tag`
2322

2423

25-
2624
## How to run specs
2725

28-
`bundle exec rake`
26+
`bundle exec rake` in the filterrific repo
27+
28+
29+
## How to support a new major Rails version
30+
31+
Follow these steps when starting support for a new Rails major version:
32+
33+
* In `filterrific`
34+
* Archive the current major rails version into a new branch off of master, e.g., when starting to support Rails 6, create a new branch for `5.x` from current master. This will be the branch used for ongoing 5.x support, and all new development for Rails 6 will happen in the `master` branch.
35+
* Make all changes required to support a new version of Rails.
36+
* Release the first `filterrific` version for Rails 6: `6.0.0`.
2937

38+
* In `filterrific_demo`
39+
* Following the same example for Rails 6:
40+
* Make sure that the `5.x` branch is up-to-date with master, and with current filterrific.
41+
* Create a new `6.x` branch. In that branch create a brand new rails app using a current version of Rails 6.
42+
* Make sure that the app works with the relevant version of `filterrific`.
43+
* Deploy demo app to heroku.
3044

3145

3246
## Travis CI

0 commit comments

Comments
 (0)