CityofSantaMonica / mds-provider

Python tools for working with MDS Provider data

https://github.com/openmobilityfoundation/mobility-data-specification

MIT License

18 stars 20 forks source link

contribute to dev or master? #59

Closed yoimnik closed 5 years ago

yoimnik commented 5 years ago

are we supposed to make contributions to dev or master?

the mds-provider-services uses the master branch for pip installing the libraries. should we PR dev into master, and make master the default branch for this repo?

yoimnik commented 5 years ago

example of what i mean above: https://github.com/CityofSantaMonica/mds-provider-services/blob/db/ingest/requirements.txt#L1

thekaveman commented 5 years ago

Right, master is the stable reference for e.g. pip installing.

55 is an example of an open PR for `dev` -> `master`, representing the next release `0.2.0`. PRs should generally target `dev`, unless it is an urgent break-fix.

dev will stay as the default to help ensure correct PR targeting the first time.

thekaveman commented 5 years ago

I think this was answered above. Let me know if not...

thekaveman commented 5 years ago

Causing more confusion than it was worth, so I got rid of dev after the latest release. master is now the default branch for PRs etc.

CityofSantaMonica / mds-provider

contribute to dev or master? #59

55 is an example of an open PR for dev -> master, representing the next release 0.2.0. PRs should generally target dev, unless it is an urgent break-fix.

55 is an example of an open PR for `dev` -> `master`, representing the next release `0.2.0`. PRs should generally target `dev`, unless it is an urgent break-fix.