DanielaSfregola · August 8, 2017 19:48
diff --git a/Feedback on cats 1.0-MF migration b/Feedback on cats 1.0-MF migration
 Overall, quite easy -- but I had to read ALL the release notes quite carefully before doing anything else.
 My approach is to usually bump the version and go through each compilation error and check the release 
 notes for instructions on how to fix them.

 Key points where I struggled:
 - I initially just bumped the version of found that it couldn't find the `cats` module anymore
 - I had to ask for help on gitter cause it wasn't able to make `mapN` (substitute of `|@|`) compile 
 because of SI-2712 fix missing
 - when reading the documentation, more of us thought that `mapN` actually meant `map2`, `map3`, 
 `map4`, etc...maybe an explicit before/after example could help?

 There are fundamental steps of the migration process that should be highlighted probably more -- 
 maybe in a well highlighted dedicated version? 
 (The cats module silly mistake was just me, but the missing SI-2712 was 3 of us!)
	Overall, quite easy -- but I had to read ALL the release notes quite carefully before doing anything else.
	My approach is to usually bump the version and go through each compilation error and check the release
	notes for instructions on how to fix them.

	Key points where I struggled:
	- I initially just bumped the version of found that it couldn't find the `cats` module anymore
	- I had to ask for help on gitter cause it wasn't able to make `mapN` (substitute of `\|@\|`) compile
	because of SI-2712 fix missing
	- when reading the documentation, more of us thought that `mapN` actually meant `map2`, `map3`,
	`map4`, etc...maybe an explicit before/after example could help?

	There are fundamental steps of the migration process that should be highlighted probably more --
	maybe in a well highlighted dedicated version?
	(The cats module silly mistake was just me, but the missing SI-2712 was 3 of us!)