-
Notifications
You must be signed in to change notification settings - Fork 12
Merge in @OlegKi's JavaScript changes. #36
Comments
What's this about ? :) |
Just making sure the issue we have discussed the most as being urgent is actually tracked. |
Yes, having a ticket for this makes it a lot easier to handle (compared to random mails). The JS changes are currently synched up to (but not including) this one: Next steps:
After, I would propose we wait for @OlegKi's documentation of his changes, because we need to keep our documentation in sync |
This one : was a change i did, it was committed by me here : and here : So the Oleg's mentionned commit merge must be avoided. Considering this one : There is no real conflict as autodetection doesn't care about it. |
I'm starting this now, and it's heavy going, practically every commit conflicts, @OlegKi please can you stop making changes to your old branch and start making them from a new fork of this project? It isn't going to be possible for us to merge any more of your changes otherwise. |
OK I've done the first ten or so commits and created pull #50. But it took ages to do even that small a number. |
I have done another ten now, next one will be free-jqgrid/jqGrid@1fabe17 |
P.S.: We still need to update the documentation for changed defaults & such |
See the release notes file I created yesterday, it has the language file changes. |
Yes, I saw. So we need to update the release notes and the options.md page |
moving to : #50 |
No description provided.
The text was updated successfully, but these errors were encountered: