New Release v2.0.0

[DronRathore]

As #18 is under dev and there are been so many fixes pushed since v1.0.2, I am wondering if after completing #18 we bump the version to v2.0.0 as in no way older versions would be compatible. Though I will keep the recent code in a new headless branch and will keep on pushing bug fixes to it.

Let me know your thoughts. 😄

[dkcheun]

#18 would be a pretty big change to the package overall so it would make sense to bump it up to v2.0.0.

[DronRathore]

Cool! But should we keep the latest 2.0.0 in the master or should we keep it in different branch? People using it without any version number will face so many problems with it as the whole code will break, or shall we deprecate the current version after sometime with depreciation warnings added to the existing code and keep 2.0.0 in another branch and release it from there?

[dkcheun]

Hmmm put it in another branch just in case people want to use the old one (for whatever reason). Good to keep an archive of things too, can never go wrong with that.