Skip to content

Commit

Permalink
2.3.16->2.4.0
Browse files Browse the repository at this point in the history
  • Loading branch information
devernay committed Apr 9, 2021
1 parent ad1403d commit dbc455e
Show file tree
Hide file tree
Showing 3 changed files with 4 additions and 7 deletions.
3 changes: 0 additions & 3 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,9 +7,6 @@

## Version 2.4.0


## Version 2.3.16

### Known issues

- Rendering sometimes silently stalls after X frames #248
Expand Down
2 changes: 1 addition & 1 deletion Documentation/templates/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ cp ../html/_groupChannel.html groupitem-foot.txt
cp ../html/_group.html group-head.txt
cp ../html/_group.html group-foot.txt
sed -e "s/Natron 2.3.15 documentation/NATRON_DOCUMENTATION/g" -e "s/Dot/%1/g" -e "s/Channel/%1/g" -i .bak *txt
sed -e "s/Natron 2.4.0 documentation/NATRON_DOCUMENTATION/g" -e "s/Dot/%1/g" -e "s/Channel/%1/g" -i .bak *txt
sed -e 's/<link rel="next".*//g' -e 's/<link rel="prev".*//g' -i .bak plugin*txt
```
Expand Down
6 changes: 3 additions & 3 deletions tools/docker/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -49,12 +49,12 @@ docker run -it --rm --mount src="$(pwd)/builds",target=/home/builds_archive,type

### Launching a release build

To launch a release, the Natron and plugins repositories must have the appropriate tags. for example, for release 2.3.15, the Natron repository must have tag `v2.3.15`, and the plugin repositories (openfx-misc, openfx-io, openfx-arena, openfx-gmic) must all have the tag `Natron-2.3.15`.
To launch a release, the Natron and plugins repositories must have the appropriate tags. for example, for release 2.4.0, the Natron repository must have tag `v2.4.0`, and the plugin repositories (openfx-misc, openfx-io, openfx-arena, openfx-gmic) must all have the tag `Natron-2.4.0`.

When launching the build, `RELEASE_TAG` must be set to the version number (eg "2.3.15") and `NATRON_BUILD_NUMBER` must be set to an integer value (typically 1 for the first build, and increment for each new build after fixing issues). See [launchBuildMain.sh](https://github.com/NatronGitHub/Natron/blob/master/tools/jenkins/launchBuildMain.sh#L340) for more details.
When launching the build, `RELEASE_TAG` must be set to the version number (eg "2.4.0") and `NATRON_BUILD_NUMBER` must be set to an integer value (typically 1 for the first build, and increment for each new build after fixing issues). See [launchBuildMain.sh](https://github.com/NatronGitHub/Natron/blob/master/tools/jenkins/launchBuildMain.sh#L340) for more details.

```
docker run -it --rm --env RELEASE_TAG=2.3.15 --env NATRON_BUILD_NUMBER=1 --env NATRON_DEV_STATUS=STABLE --mount src="$(pwd)/builds",target=/home/builds_archive,type=bind natrongithub/natron-sdk:latest
docker run -it --rm --env RELEASE_TAG=2.4.0 --env NATRON_BUILD_NUMBER=1 --env NATRON_DEV_STATUS=STABLE --mount src="$(pwd)/builds",target=/home/builds_archive,type=bind natrongithub/natron-sdk:latest
```


Expand Down

0 comments on commit dbc455e

Please sign in to comment.