Start versioning beyond version zero #1869
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1869 +/- ##
=======================================
Coverage 93.17% 93.17%
=======================================
Files 287 287
Lines 3237 3237
Branches 490 490
=======================================
Hits 3016 3016
Misses 221 221 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
sounds reasonable -- just a note that the versions apply to our OpenAPI specification document (which is what we mean by API version) as well as our published SDKs To your point: we'll rapidly increase major versions since at this point / probably for a while are breaking changes, but I don't think we need to be afraid of reaching EDIT: didn't see this was a PR sorry, thought it was an issue for discussion! The above wasn't intended as an approve just yet. v1 release is a huge deal! |
|
@slifty It is a succinct and actionable discussion-starter, it's a PR : ) |
Until recently, the PDC back-end software has largely been in an experimental or prototype state. At least two parties (besides the team developing the PDC back-end) call it. We also anticipate real data to be sent to the PDC soon. Even if the software remains experimental for a while, the API has matured over the past three-plus years since its first commit. It is time to call it version one.
|
Created a ticket for us to be able to talk about what policies (if any) we'll want to adopt alongside a change like this: #1895 |
Until recently, the PDC back-end software has largely been in an experimental or prototype state. At least two parties (besides the team developing the PDC back-end) call it. We also anticipate real data to be sent to the PDC soon. Even if the software remains experimental for a while, the API has matured over the past three-plus years since its first commit. It is time to call it version one.