search

opengeospatial / geoparquet

Specification for storing geospatial vector data (point, line, polygon) in Parquet
https://geoparquet.org
Apache License 2.0
780 stars 54 forks source link

Branching strategy for spec development #34

Closed TomAugspurger closed 2 years ago

TomAugspurger commented 2 years ago

Now that we have a release we should figure out a branching strategy going forward. I think the primary thing to consider is what version of the spec should a person visiting https://github.com/opengeospatial/geoparquet? The "currently released version, or the in-development version?

My thoughts: we keep things as is for now (just a single main branch that we develop against), at least until we hit 1.0. I think there's a bit more value in people seeing what's coming soon.

After 1.0, I could see making a dev branch. But IMO it's not worth branching until we have a change that's going to require a 1.x (or 2.0), otherwise we'll have to backport / cherry pick typo fixes and clarifications.

jorisvandenbossche commented 2 years ago

My thoughts: we keep things as is for now (just a single main branch that we develop against), at least until we hit 1.0. I think there's a bit more value in people seeing what's coming soon.

+1