Open roll opened 6 days ago
Agreed. In addition:
We should have a mechanism to separate minor corrections to the website (live immediately) from changes that are part of a new release. The easiest solution I can think of:
main
branch = website. PRs that make quick corrections (e.g. #978) should be merged with this branch.upcoming-version
branch = all changes for a next version. PRs that affect the standard (e.g. #961) should be merged with this branch.upcoming-version
can be brought in sync by merging in main
, but the reverse should only be done when we plan to release a new version. That could kick off a bunch of build scripts (preferably a python script triggered by a GitHub Action) that:
See this PR - https://github.com/frictionlessdata/datapackage/pull/975 - creating new profiles version required to change version numbers in many places manually. This process needs to be automated (e.g. using a version variable)