Release Timezone version 0.2.0.
- Dominant language
- JavaScript
- Stars
- 256
- Forks
- 26
- PR merge metrics
- No merged PRs in 30d
Description
I've created this issue for may many early adopters to be appraised of API changes to Timezone while it is on the 0.0.x version branch. Currently, I'm updating another issue to keep my many early adopters (and by many early adopters, I mean the very helpful @sberryman) appraised of such changes.
On the `0.0.x` branch, API changes may break applications. Please use an absolute version number in your `package.json` to hold onto a version Timezone that works for you. When `0.0.x` development is done, I'll create an `0.2.0` branch for application use and a `0.1.0` for any further development. The `0.2.0` branch will be an API freeze.
Timezone is stable at this point. There is only one API change to the Node.js API remaining; I'm going to move the zone database somewhere, so you're `require` will have to change. Otherwise, the invocation of the `tz` function is highly unlikely to change.
There will be further development to Timezone to make it work well in the browser, but that is unlikely to affect Node.js users.
Thank you very much for using Timezone.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.