Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[geogig-dev] release schedule and version planning

I gotta a confusion about our upcoming roadmap ... minor difference on numbering.

Java versioning:
- QGIS 1.0 initial release (using BDB as default local repo)
- QGIS 2.0 second release (using sqlite as default backend), locationtech approved dependencies

And dot release versioning:
- QGIS 1.0 initial release (no default local repo, command line example of using BDB, sqlite)
- QGIS 1.1 second release (BDB optional install, make sqlite the default) locationtech approved dependencies

Why worry: .. the whole product point of having an initial 1.0 release is to be STABLE so people trust us enough to embed geogig into EVERYTHING. If we follow it a few weeks-months later with a QGIS 2.0 we are sending a CRAZY signal to those wanting to use geogig - namely that we will never be stable enough to embed.

Talking with Tyler:  It is a bit rude having DBD as as default, and then having it be an optional install later. Update to 2.0 when the storage on disk changes and is incompatible, rather than based on any code changes.
-- 

Jody Garnett
Community Lead | Boundless


Back to the top