Also, @les it probably makes sense for us to have a voip meeting and walk through the sync code and the indexeddb write-batching, in case you have any questions about design choices. it’s been a while, and some of it probably changed since i last worked on it, but who knows, maybe i can help answer some of the questions you undoubtedly ran into while digging into the code
Here’s a summary of what we talked about and decided on:
We are going to merge the noglobal branch into master and version it as 1.0-alpha.
The current master will become the stable branch.
We create new issues for the proposed API changes and all other changes needed for the 1.0 release.
These issues are going to be grouped in a 1.0 milestone.
The current changes in regards to sync still need to be documented.
We should look through all documentation in the doc directory and check if everything is still up-to-date.
We will have regular (bi-weekly) meetings via IRC in the future.
There was a PR once that removed the Promise.defer calls, but we didn’t merge it. Maybe we can still use the code to get rid of the remaining calls in the noglobal branch.
We will start a new forum topic to discuss possible event(s) we can do for http://wwwtf.berlin/
ops, probably a misunderstanding, with “sync documentation” I meant “we need to sync documentation between how things works and how they are documented”, in @galfert report points are:
We should look through all documentation in the doc directory and check if everything is still up-to-date.
The current changes in regards to sync still need to be documented.