Skip to content
This repository has been archived by the owner on Sep 7, 2018. It is now read-only.

determine how to version breaking changes #18

Open
ambrosejcarr opened this issue Aug 23, 2018 · 4 comments
Open

determine how to version breaking changes #18

ambrosejcarr opened this issue Aug 23, 2018 · 4 comments

Comments

@ambrosejcarr
Copy link
Member

need a plan that states how we will increment versioning.

@ttung
Copy link

ttung commented Aug 23, 2018

File version?

@ambrosejcarr
Copy link
Member Author

ambrosejcarr commented Aug 23, 2018

File version?

Yea, that might be a good idea. If the package is installable, how do we deal with breaking vs non-breaking changes? Semantic versioning seems like it'd be a bit gross, we'd be at version 112.0.0 very soon, I think. ;)

@ttung
Copy link

ttung commented Aug 23, 2018

File version was a question about what sort of versioning we need. Is it file version or app version?

@ambrosejcarr
Copy link
Member Author

I have no idea. The HCA-metadata people seem to go with file versions for their schema.

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