This effectively means we can't really update to any new PouchDB releases because we can't be sure they will work on JXcore. The only sane approach at this point is to commit resources to PouchDB so that they will continue to run the 0.10 tests but we will promise to look at the bugs and fix them.
Alternatively we can set up our own ingestion pipeline that before we take a PouchDB new released we test it on JXcore. This sounds reasonable until you realize that PouchDB is still under active development, we aren't likely to check release often and so who sets of issues can accrete (including using features that just aren't in node 0.10) that we then have to try to get PouchDB to undo. Good luck with that.
That's why it's so important to keep PouchDB running 0.10 tests so that issues show up immediately and can be addressed immediately.
The text was updated successfully, but these errors were encountered:
pouchdb/pouchdb#5070 (comment)
This effectively means we can't really update to any new PouchDB releases because we can't be sure they will work on JXcore. The only sane approach at this point is to commit resources to PouchDB so that they will continue to run the 0.10 tests but we will promise to look at the bugs and fix them.
Alternatively we can set up our own ingestion pipeline that before we take a PouchDB new released we test it on JXcore. This sounds reasonable until you realize that PouchDB is still under active development, we aren't likely to check release often and so who sets of issues can accrete (including using features that just aren't in node 0.10) that we then have to try to get PouchDB to undo. Good luck with that.
That's why it's so important to keep PouchDB running 0.10 tests so that issues show up immediately and can be addressed immediately.
The text was updated successfully, but these errors were encountered: