Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Checklist for PouchDB 7.0.0 #6356
We released 6.0.0 in September 2016, and 5.0.0 in December 2015. I agree with Tom Dale that SemVer shouldn't mean more breaking changes, so to keep us around ~1 major release per year, I'd propose a 7.0.0 release later this year.
I think the ideal strategy is to cram as many breaking changes as possible into a few infrequent releases. You don't want users to have to wonder: "Hmmm, in v7 they removed this, and in v8 they removed that, and in v9 they removed another thing, so if I'm on v5 and want to upgrade to v10...". Keep it simple.
Following up on discussion in #6019, this is a living list of breaking changes for PouchDB 7.0.0. Please comment here if anything concerns you, or if there are other changes you'd like to add.
Nice-to-haves, may not make it
In terms of strategy, I think we should create a separate branch called
My hunch is that 7.0.0 will be the last major release before
We should probably also use dist-tags to start shipping alpha versions of 7.0.0 to npm before it's officially released. Babel, Webpack, and many other projects have had success with this strategy.
Yup, I agree. No reason to call it "beta" anymore. The actual indexing is 100% solid because it's based on pouchdb-abstract-mapreduce. The only thing that's still incomplete is the query language, but that's less of a big deal because it can always be fixed later, without requiring data migration.
In fact since we publish all packages at the same version, looks like pouchdb-find will jump from 0.10.5 to 5.x which definitely communicates "not in beta anymore."
referenced this issue
Mar 26, 2017
About polyfill, I think it could be great to remove them from core for 2 reasons :
By the way, guys you do a great job, thanks to you.
I'm not sure this is actually the case. I don't have data, but my hunch is that since Webpack/Browserify are new technologies, most webdevs are still using old-fashioned
I think it's important to strike a balance between "works out of the box" for beginners and "I can customize to my liking" for experts. Take a look at #6377 where I'm trying to make this a bit more explicit without needing to yank out features for absolutely everybody.
I aggree on the fact that beginners will use <script> tag. But for professional, it's mandatory use use bundler (like rollup => strong compression and one output file), minimifier, tests, automation (ex: gulp), etc... All peoples dont live in european or north american countries. India or China represent a big market (billions of people) and still have a slow connection... Same for mobile devices...
For a "works out of the box" you could provide some king of "pouchdb-web-full.js" which could import pouchdb-core, pouchdb-mapreduce, shims, etc...
@lifaon74 Does the proposed