Skip to content

Commit

Permalink
version updated for development
Browse files Browse the repository at this point in the history
  • Loading branch information
scap3yvt authored Sep 24, 2024
1 parent 4d614fe commit 86c8fab
Show file tree
Hide file tree
Showing 17 changed files with 24 additions and 24 deletions.
2 changes: 1 addition & 1 deletion GANDLF/version.py
Original file line number Diff line number Diff line change
Expand Up @@ -2,4 +2,4 @@
# -*- coding: UTF-8 -*-

# check GaNDLF wiki for versioning and release guidelines: https://github.com/mlcommons/GaNDLF/wiki
__version__ = "0.1.0"
__version__ = "0.1.1-dev"
4 changes: 2 additions & 2 deletions docs/migration_guide.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,8 +15,8 @@ The [0.0.20 release](https://github.com/mlcommons/GaNDLF/releases/tag/0.0.20) wa
- The main change is the use of the [Version package](https://github.com/keleshev/version) for systematic semantic versioning [[ref](https://github.com/mlcommons/GaNDLF/pull/841)].
- No change is needed if you are using a [stable version](https://docs.mlcommons.org/GaNDLF/setup/#install-from-package-managers).
- If you have installed GaNDLF [from source](https://docs.mlcommons.org/GaNDLF/setup/#install-from-sources) or using a [nightly build](https://docs.mlcommons.org/GaNDLF/setup/#install-from-package-managers), you will need to ensure that the `maximum` key under `version` in the configuration file contains the correct version number:
- Either **including** the `-dev` identifier of the current version (e.g., if the current version is `0.1.0-dev`, then the `maximum` key should be `0.1.0-dev`).
- Or **excluding** the `-dev` identifier of the current version, but increasing the version number by one on any level (e.g., if the current version is `0.1.0-dev`, then the `maximum` key should be `0.1.1`).
- Either **including** the `-dev` identifier of the current version (e.g., if the current version is `0.X.Y-dev`, then the `maximum` key should be `0.X.Y-dev`).
- Or **excluding** the `-dev` identifier of the current version, but increasing the version number by one on any level (e.g., if the current version is `0.X.Y-dev`, then the `maximum` key should be `0.X.Y`).

### Use in HPC Environments

Expand Down
4 changes: 2 additions & 2 deletions samples/config_all_options.yaml
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
# affix version
version:
{
minimum: 0.1.0,
maximum: 0.1.0 # this should NOT be made a variable, but should be tested after every tag is created
minimum: 0.1.1-dev,
maximum: 0.1.1-dev # this should NOT be made a variable, but should be tested after every tag is created
}
## Choose the model parameters here
model:
Expand Down
4 changes: 2 additions & 2 deletions samples/config_classification.yaml
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
# affix version
version:
{
minimum: 0.1.0,
maximum: 0.1.0 # this should NOT be made a variable, but should be tested after every tag is created
minimum: 0.1.1-dev,
maximum: 0.1.1-dev # this should NOT be made a variable, but should be tested after every tag is created
}
# Choose the model parameters here
model:
Expand Down
2 changes: 1 addition & 1 deletion samples/config_getting_started_classification_histo2d.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -94,6 +94,6 @@ scheduler:
track_memory_usage: false
verbose: false
version:
maximum: 0.1.0
maximum: 0.1.1-dev
minimum: 0.0.14
weighted_loss: true
2 changes: 1 addition & 1 deletion samples/config_getting_started_classification_rad3d.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -99,6 +99,6 @@ scheduler:
track_memory_usage: false
verbose: false
version:
maximum: 0.1.0
maximum: 0.1.1-dev
minimum: 0.0.14
weighted_loss: true
2 changes: 1 addition & 1 deletion samples/config_getting_started_regression_histo2d.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -59,6 +59,6 @@ scheduler:
track_memory_usage: false
verbose: false
version:
maximum: 0.1.0
maximum: 0.1.1-dev
minimum: 0.0.14
weighted_loss: true
2 changes: 1 addition & 1 deletion samples/config_getting_started_regression_rad3d.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -62,6 +62,6 @@ scheduler:
track_memory_usage: false
verbose: false
version:
maximum: 0.1.0
maximum: 0.1.1-dev
minimum: 0.0.14
weighted_loss: false
2 changes: 1 addition & 1 deletion samples/config_getting_started_segmentation_histo2d.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -66,6 +66,6 @@ scheduler:
track_memory_usage: false
verbose: true
version:
maximum: 0.1.0
maximum: 0.1.1-dev
minimum: 0.0.14
weighted_loss: true
4 changes: 2 additions & 2 deletions samples/config_getting_started_segmentation_rad3d.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -89,6 +89,6 @@ scheduler:
track_memory_usage: false
verbose: true
version:
maximum: 0.1.0
minimum: 0.1.0
maximum: 0.1.1-dev
minimum: 0.1.1-dev
weighted_loss: true
4 changes: 2 additions & 2 deletions samples/config_regression.yaml
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
# affix version
version:
{
minimum: 0.1.0,
maximum: 0.1.0 # this should NOT be made a variable, but should be tested after every tag is created
minimum: 0.1.1-dev,
maximum: 0.1.1-dev # this should NOT be made a variable, but should be tested after every tag is created
}
# Choose the model parameters here
model:
Expand Down
4 changes: 2 additions & 2 deletions samples/config_segmentation_brats.yaml
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
# affix version
version:
{
minimum: 0.1.0,
maximum: 0.1.0 # this should NOT be made a variable, but should be tested after every tag is created
minimum: 0.1.1-dev,
maximum: 0.1.1-dev # this should NOT be made a variable, but should be tested after every tag is created
}
# Choose the model parameters here
model:
Expand Down
4 changes: 2 additions & 2 deletions samples/config_segmentation_histology.yaml
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
# affix version
version:
{
minimum: 0.1.0,
maximum: 0.1.0 # this should NOT be made a variable, but should be tested after every tag is created
minimum: 0.1.1-dev,
maximum: 0.1.1-dev # this should NOT be made a variable, but should be tested after every tag is created
}
# Choose the model parameters here
model:
Expand Down
2 changes: 1 addition & 1 deletion testing/config_classification.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -55,7 +55,7 @@ save_output: false
scaling_factor: 1
scheduler: triangle
version:
maximum: 0.1.0
maximum: 0.1.1-dev
minimum: 0.0.14
weighted_loss: True

2 changes: 1 addition & 1 deletion testing/config_regression.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,7 @@ save_output: false
scaling_factor: 1
scheduler: triangle
version:
maximum: 0.1.0
maximum: 0.1.1-dev
minimum: 0.0.14
weighted_loss: false

2 changes: 1 addition & 1 deletion testing/config_segmentation.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@
version:
{
minimum: 0.0.14,
maximum: 0.1.0
maximum: 0.1.1-dev
}
model:
{
Expand Down
2 changes: 1 addition & 1 deletion tutorials/classification_medmnist_notebook/config.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
version:
{
minimum: 0.0.14,
maximum: 0.1.0 # this should NOT be made a variable, but should be tested after every tag is created
maximum: 0.1.1-dev # this should NOT be made a variable, but should be tested after every tag is created
}
# Choose the model parameters here
model:
Expand Down

0 comments on commit 86c8fab

Please sign in to comment.