Adding an Upgrade Guide
About
Since starting using your package about a month ago, I have been following along as you've fix fux-ed your way to v3, and I'm starting to feel the hype!
I'm planning on trying out v3.0.0-beta1 later today, and I was wondering whether I should use this as an opportuinity to start writing an upgrade guide for migrating from v2 -> v3? In that way I could hopefully have it done for when v3 is ready. ☺️ ✌️
Also, if there's anything that I can do to help with getting v3 over the finish line, then please don't hesitate letting me know. 🕺
Thank you very much; the v3 version adds some new ideas on the basis of v2; and renames some classes; because I am not an English speaker, it is more difficult to organize the words for me; if you are willing to help add upgrade docs, please feel free to create pr.
Alrighty then, I'll get started on the upgrade guide. Once I've settled on the main structure, I'll publish a draft PR which that we can use as a base for discussion. Aiming to have the aforementioned PR ready by Wednesday.
Questions (@slince)
- Is there any bigger changes left in the pipeline for
v3? - Would you mind writing me a bullet-list of remaining bugs/features/enhancements that needs finishing for you to feel
v3is ✔️ Done.