Matt Johnson-Pint

@jabjab - That seems like a reasonable workaround.

@realyze - That might fail on the first/last day of the month.

Well, even [the source data](http://www.iana.org/time-zones) changes regularly. Time zones are a political decision, and are subject to change at the whim of the world's governments. So in order to keep...

Marking this as "enhancement" to remind us to create a "current data" pointer. Another approach you could take in the meantime is to point at a CDN cached version of...

Agreed. They're both bugs. Cloning a moment shouldn't change anything about it. Any mode, offset, or zone details should carry forward. With regard to `startOf('day')`, I would expect that whenever...

Consider that without moment-timezone, setting my time zone for Brazil: ``` javascript moment("2014-10-19T12:00:00+08:00").startOf('day').format() // "2014-10-19T01:00:00-02:00" moment.parseZone("2014-10-19T12:00:00+08:00").startOf('day').format() // "2014-10-19T00:00:00+08:00" ``` So without moment-timezone appears to have the behavior I described above....

Indeed, I just found this in the docs: http://momentjs.com/docs/#/manipulating/utc-offset/ > ... Note that once you set an offset, its fixed and won't change on its own (i.e there are no...

Hi @dashie. Sorry I was tuned out for a while. You basically hit the same problem I just stumbled upon, in #743 after updating things for the latest IANA version....

... Or rather, can you separate the code changes out so I can do a full build after merging? Thanks.

Thanks for the bug report. I can confirm this, and will dig in further as soon as I can.