Conversation
|
We should also add This would be a good workaround before adding per instance lang configurations. |
|
FYI, I updated the list. The new parser ended up taking much less time than I thought it would. It passes all the previous tests, plus the new 'YYYMMDD' tests. I think it's pretty stable, so it should be good to release. I added lang as a getter, and moved the S/SS/SSS parsing issue up to the 'have been written' section. I also added moment.fn.isValid and two letter month names to the 'not this release' section. |
|
I added these to the 'already written' section, and moved durations there as well.
|
|
I think this is ready to go, @rockymeza, is there anything I'm forgetting? |
|
Looks like a good solid release to me. What about that Korean bug? We On Tue, Apr 24, 2012 at 6:19 PM, Tim Wood <
|
|
Cool, all that is left is adding docs for durations and ender compatibility. I've created placeholders, so hopefully I can get it all written tonight. I'll ping you so you can double check them before I make the release. |
|
@rockymeza, I added docs for durations, please check it out over on https://github.com/timrwood/momentjs.com. Everything is just in the master branch there for now. (After 1.6.0 release, I think I'll switch that to git flow as well). I also made you a collaborator on that site, so you should be able to push changes there as well. After you look over the docs, I'll release 1.6.0. |
|
This is released! |
Note: this pull request is not ready to be merged in.
I am opening up the version 1.6.0 release for discussion. In this pull request, I think we should talk about the features that need to be added or removed before we can cut a new version of moment. Here are some changes that I think should be in version 1.6.
Languages
To be removed
New Features that have already been written
_isUTCpropertyNew features that have not been written
Things that should not go into this release