Matt Johnson-Pint

Ok, so now that moment/moment#3098 has been merged, let's address this, and also that formatting is now using `Z` instead of `+00:00`. (BTW - the MS issue above will be...

Yes, it's a bug. You can work around it like so: ```js moment.tz("America/Los_Angeles").hour(12).toString() ```

Confirmed. Not sure the cause. Will investigate. Thanks!

Currently, the expected behavior is that `local()` should always set back to the local time zone, not necessarily to the "default" time zone. See #247. There is a bug here...

I believe this will be addressed if moment/moment-rfcs#1 is adopted.

The `isUtc()` function still returns the correct result. The general guidance is to not use the underscore-prefixed properties externally, as many of the moment functions combine multiple properties to achieve...

@ashleydw - `utcOffset()` returns a number in terms of minutes East of UTC. 60 minutes in an hour, so 600 / 60 = 10 hours East of UTC, which we...

@wyefei - in the example you gave, the offset is your *local* offset, not the one passed in. You'd have to use `moment.parseZone(...)` to retain the offset passed in.

To be clear, the bug being tracked in this issue is related to calling `utcOffset` with the `true` second parameter (to keep the local time) [as shown here](https://github.com/moment/moment-timezone/issues/187#issuecomment-82379973), should clear...

@ichernev @Poyeyo - you are both listed at https://packagist.org/packages/moment/moment so it won't let me add this. Can you please either add me (mj1856) to that package, or also add moment-timezone?...