From 3906a1077172052d696ad20d3d30b43cbf2287a4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jean-Fran=C3=A7ois=20Boismenu?= Date: Mon, 23 Sep 2019 12:56:00 -0400 Subject: [PATCH 1/4] packaging for 3.2.0 --- HISTORY.rst | 4 ++++ README.md | 1 - setup.py | 2 +- shotgun_api3/shotgun.py | 2 +- 4 files changed, 6 insertions(+), 3 deletions(-) diff --git a/HISTORY.rst b/HISTORY.rst index 80ac2dea..a5a9a82c 100644 --- a/HISTORY.rst +++ b/HISTORY.rst @@ -4,6 +4,10 @@ Shotgun Python API Changelog Here you can see the full list of changes between each Python API release. +v3.2.0 (2019 Sept 23) +===================== +- It is now possible to modify field visibility via ``schema_field_update``. + v3.1.2 (2019 Sept 17) ===================== - Adds an optional `localized` property on the Shotgun object which allows to retrieve localized display names on diff --git a/README.md b/README.md index 57a22f83..51cd48ca 100644 --- a/README.md +++ b/README.md @@ -116,7 +116,6 @@ Integration and unit tests are provided. - Make sure the date of the release matches today. We try and keep this TBD until we're ready to do a release so it's easy to catch that it needs to be updated. - Make sure the version number is filled out and correct. We follow semantic versioning. Or more correctly, we should be following it. 2) Ensure any changes or additions to public methods are documented - - Update the Github wiki, and usually you'll need to update the Method Reference page with concise and exact documentation of the changes that are in this release. - Ensure that doc strings are updated in the code itself to work with Sphinx and are correctly formatted. - Examples are always good especially if this a new feature or method. - Think about a new user to the API trying to figure out how to use the features you're documenting. diff --git a/setup.py b/setup.py index 8837466c..49533ae6 100644 --- a/setup.py +++ b/setup.py @@ -27,7 +27,7 @@ setup( name='shotgun_api3', - version='3.1.2', + version='3.2.0', description='Shotgun Python API ', long_description=readme, author='Shotgun Software', diff --git a/shotgun_api3/shotgun.py b/shotgun_api3/shotgun.py index 06519241..5bbc3e32 100755 --- a/shotgun_api3/shotgun.py +++ b/shotgun_api3/shotgun.py @@ -117,7 +117,7 @@ def _is_mimetypes_broken(): # ---------------------------------------------------------------------------- # Version -__version__ = "3.1.2" +__version__ = "3.2.0" # ---------------------------------------------------------------------------- # Errors From 2b1ae2ca4a5f447de10fb7d96412cd07d118dd1c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jean-Fran=C3=A7ois=20Boismenu?= Date: Mon, 23 Sep 2019 13:00:40 -0400 Subject: [PATCH 2/4] updated release process --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 51cd48ca..3aba407d 100644 --- a/README.md +++ b/README.md @@ -129,7 +129,7 @@ Integration and unit tests are provided. - Add more detailed information regarding the changes in this release. This is a great place to add examples, and reasons for the change! ### Letting the world know -We usually send an email to the `shotgun-dev` list with an announcement of the release and highlight the changes. +Post a message in the the [Pipeline Community channel](https://community.shotgunsoftware.com/c/pipeline) and send an email to [shotgun-dev](https://groups.google.com/a/shotgunsoftware.com/forum/#!forum/shotgun-dev) with a link to the community post. ### Prepare for the Next Dev Cycle 1) Update the `__version__` value in `shotgun_api3/shotgun.py` to the next version number with `.dev` appended to it. For example, `v3.0.24.dev` From 28a128ca7fdda5e85fb76fc73b86e58d1bfa2dc5 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jean-Fran=C3=A7ois=20Boismenu?= Date: Mon, 23 Sep 2019 13:09:36 -0400 Subject: [PATCH 3/4] Update HISTORY.rst --- HISTORY.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/HISTORY.rst b/HISTORY.rst index a5a9a82c..ba3d10b9 100644 --- a/HISTORY.rst +++ b/HISTORY.rst @@ -6,7 +6,7 @@ Here you can see the full list of changes between each Python API release. v3.2.0 (2019 Sept 23) ===================== -- It is now possible to modify field visibility via ``schema_field_update``. +- Adds a new ``project`` parameter to ``schema_field_update`` that allows to modify field visibility for a given project. v3.1.2 (2019 Sept 17) ===================== From d79ad8dd2cd9a57287050420c518c15f55e06d65 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jean-Fran=C3=A7ois=20Boismenu?= Date: Mon, 23 Sep 2019 13:10:08 -0400 Subject: [PATCH 4/4] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 3aba407d..a3d72d49 100644 --- a/README.md +++ b/README.md @@ -129,7 +129,7 @@ Integration and unit tests are provided. - Add more detailed information regarding the changes in this release. This is a great place to add examples, and reasons for the change! ### Letting the world know -Post a message in the the [Pipeline Community channel](https://community.shotgunsoftware.com/c/pipeline) and send an email to [shotgun-dev](https://groups.google.com/a/shotgunsoftware.com/forum/#!forum/shotgun-dev) with a link to the community post. +Post a message in the [Pipeline Community channel](https://community.shotgunsoftware.com/c/pipeline) and send an email to [shotgun-dev](https://groups.google.com/a/shotgunsoftware.com/forum/#!forum/shotgun-dev) with a link to the community post. ### Prepare for the Next Dev Cycle 1) Update the `__version__` value in `shotgun_api3/shotgun.py` to the next version number with `.dev` appended to it. For example, `v3.0.24.dev`