You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes bugs in the tooling require a re-compilation of all dictionaries and
also require a new release, even though the source didn't change. Since we use
semantic versioning, we could re-release all non-source releases by appending a
build number, as for instance a.valid.version-1.
The workflow should be as follows:
make deploy-src
deploys the source to fd.org
git tag, if version-controlled (optional)
make deploy
obtain the source version mentioned in the edition tag of the
dictionary
query last build number and increase by one
deploy the auto-generated binary distributions
Ideally there would be a make deploy BUILD_NO= command to accomplish this.
Deploying a new build version should make sure that the source release remains
untouched.
The text was updated successfully, but these errors were encountered:
humenda
changed the title
extend tools to re-deploy dictionaries with a build number
Extend tools to re-deploy dictionaries with a build number
Jan 19, 2020
Sometimes bugs in the tooling require a re-compilation of all dictionaries and
also require a new release, even though the source didn't change. Since we use
semantic versioning, we could re-release all non-source releases by appending a
build number, as for instance
a.valid.version-1
.The workflow should be as follows:
dictionary
Ideally there would be a
make deploy BUILD_NO=
command to accomplish this.Deploying a new build version should make sure that the source release remains
untouched.
The text was updated successfully, but these errors were encountered: