List view
2.0.0 will mark a change in course for NimbusKit, with *each component being separated into individual Github repositories*. The reasons for this: - Easier version tracking. - Cleaner modifications to features. - Easier to deprecate features and add new ones. - Easier to add individual features (no longer need to check out all of Nimbus just to use the attributed label, for example). The primary downside will be that people now have to manage multiple git repositories, though with the Catalog github repo including all features as submodules, Cocoapods for targeted inclusion, and good ol' git for direct feature cloning, there will be plenty of methods to include NimbusKit components into projects. The Plan ======= Step 1: Stabilize Nimbus ------------------------------------ Before cutting 2.0.0, every bug must be closed on the latest version of Nimbus. Step 2: Cut a Final 1.* Release ----------------------- Once all bugs have been closed, a final version 1 release will be cut. This will be the base from which version 2 is based. Step 3: Create a Template Github Repo ----------------- This will be used to define the foundation for each existing feature and any new ones as well. Step 4: Create a Catalog Repo ------------- This repo will have every NimbusKit feature as a submodule and will include the Catalog application, detailing every feature of Nimbus. Step 5: Port Each Feature to a New Github Repo ----------- These will all be found at the NimbusKit org. Step 6: Move jverkoey/nimbus into the NimbusKit org ------------ This one will be tricky. It's possible that we'll want to move the repo and wipe it clean, turning it into the catalog repo. This needs to be thought through some more. Step 7: Cut the 2.0.0 Release ---------- Once everything has moved over we can cut the 2.0.0 release!
No due date•2/2 issues closed