Skip to content
This repository has been archived by the owner on Aug 13, 2024. It is now read-only.

Common: consider switching to git flow #8

Open
chuwy opened this issue Oct 1, 2019 · 4 comments
Open

Common: consider switching to git flow #8

chuwy opened this issue Oct 1, 2019 · 4 comments

Comments

@chuwy
Copy link
Contributor

chuwy commented Oct 1, 2019

No description provided.

@chuwy
Copy link
Contributor Author

chuwy commented Nov 28, 2019

Should we start all our new releases in 2020 with git flow? Should we pick a set of early adopters?

@peel
Copy link
Contributor

peel commented Nov 29, 2019

I'd say split the snowplow/snowplow, migrate to gitflow everywhere. Just make sure we're able to release RCs #12. All the other things will come along.

@chuwy
Copy link
Contributor Author

chuwy commented Nov 29, 2019

We unfortunately cannot just assume that it will happen all at once. We need to figure what repos will be the first ones, some of them will be experimental where we decide what subset of git flow we'll embrace. Also this will have to be announced - our partners, customers and OSS contributors rely on current convention to keep track what's happening.

Just make sure we're able to release RCs #12.

Not sure how #12 is related to being able to release RCs. We are able to release them now.

@peel
Copy link
Contributor

peel commented Nov 29, 2019

Not sure how #12 is related to being able to release RCs. We are able to release them now.

Linked for sake of completeness.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants