Commit 5639825eace4f18839a5b3279f4223060def471a
1 parent
c6c8ffbd
Exists in
master
and in
1 other branch
add upgrade beyond v0.4.0 notes
Showing
1 changed file
with
10 additions
and
0 deletions
Show diff stats
README.md
| @@ -202,6 +202,16 @@ This will ensure that your application stays up to date with any schema changes. | @@ -202,6 +202,16 @@ This will ensure that your application stays up to date with any schema changes. | ||
| 202 | * You must have already run migrations at least up to v0.3.0. Check to | 202 | * You must have already run migrations at least up to v0.3.0. Check to |
| 203 | make sure you're schema version is at least 20131011155638 by running rake | 203 | make sure you're schema version is at least 20131011155638 by running rake |
| 204 | db:version before you upgrade beyond v0.4.0 | 204 | db:version before you upgrade beyond v0.4.0 |
| 205 | +* Notice fingerprinting has changed and is now easy to configure. But this | ||
| 206 | + means you'll have to regenerate fingerprints on old notices in order to for | ||
| 207 | + them to be properly grouped with new notices. To do this run: `rake | ||
| 208 | + errbit:notice_refingerprint`. If you were using a custom fingerprinter class | ||
| 209 | + in a previous version, be aware that it will no longer have any effect. | ||
| 210 | + Fingerprinting is now configurable within the Errbit UI. | ||
| 211 | +* Prior to v0.4.0, users were only able to see apps they were watching. All | ||
| 212 | + users can now see all apps and they can watch or unwatch any app. If you were | ||
| 213 | + using the watch feature to hide secret apps, you should not upgrade beyond | ||
| 214 | + v0.4.0. | ||
| 205 | 215 | ||
| 206 | ### Upgrading errbit from v0.3.0 to v0.4.0 | 216 | ### Upgrading errbit from v0.3.0 to v0.4.0 |
| 207 | 217 |