SMTK issueshttps://gitlab.kitware.com/cmb/smtk/-/issues2016-10-11T13:22:39-04:00https://gitlab.kitware.com/cmb/smtk/-/issues/80Add 3DM and 2DM as an option to export mesh operator2016-10-11T13:22:39-04:00Robert M. O'BaraAdd 3DM and 2DM as an option to export mesh operatorCurrently you can export the mesh as VTK, etc.. but not these.Currently you can export the mesh as VTK, etc.. but not these.SMTK 1.1T.J. CoronaT.J. Coronahttps://gitlab.kitware.com/cmb/smtk/-/issues/72Add modified signals to qtItem and qtattribute2016-10-21T13:58:13-04:00Robert M. O'BaraAdd modified signals to qtItem and qtattributeNeed to be able to tell if an item or attribute has been modified via the GUI - needed to properly deal with the operator View GUINeed to be able to tell if an item or attribute has been modified via the GUI - needed to properly deal with the operator View GUISMTK 1.1Robert M. O'BaraRobert M. O'Barahttps://gitlab.kitware.com/cmb/smtk/-/issues/71Clean up Input Item Code2016-09-14T10:45:04-04:00Robert M. O'BaraClean up Input Item CodeRight now the code is inside of the UIManager instead of the Input Item classRight now the code is inside of the UIManager instead of the Input Item classSMTK 1.1Robert M. O'BaraRobert M. O'Barahttps://gitlab.kitware.com/cmb/smtk/-/issues/70Document Software Process for SMTK2016-09-02T14:04:19-04:00Robert M. O'BaraDocument Software Process for SMTKThis should include providing general information to developers and reporters that can be access on the project in GitLab.This should include providing general information to developers and reporters that can be access on the project in GitLab.SMTK 1.1Robert M. O'BaraRobert M. O'Barahttps://gitlab.kitware.com/cmb/smtk/-/issues/530ValueItemTemplate const_iterator typedef is incorrect?2024-03-26T17:02:24-04:00jwilson1881ValueItemTemplate const_iterator typedef is incorrect?```
template<typename DataT>
class SMTK_ALWAYS_EXPORT ValueItemTemplate : public ValueItem
{
//template<DataT> friend class ValueItemDefinitionTemplate;
public:
typedef DataT DataType;
typedef typename std::vector<DataT> value_type...```
template<typename DataT>
class SMTK_ALWAYS_EXPORT ValueItemTemplate : public ValueItem
{
//template<DataT> friend class ValueItemDefinitionTemplate;
public:
typedef DataT DataType;
typedef typename std::vector<DataT> value_type;
typedef value_type const_iterator;
typedef ValueItemDefinitionTemplate<DataType> DefType;
~ValueItemTemplate() override = default;
typename std::vector<DataT>::const_iterator begin() const { return m_values.begin(); }
typename std::vector<DataT>::const_iterator end() const { return m_values.end(); }
```
In the snippet above, should `typedef value_type const_iterator;` actually be written as `typedef typename value_type::const_iterator const_iterator;`?
If so, should the following `begin()` and `end()` functions be declared as:
```
const_iterator begin() const { return m_values.begin(); }
const_iterator end() const { return m_values.end(); }
```
???Robert M. O'BaraRobert M. O'Barahttps://gitlab.kitware.com/cmb/smtk/-/issues/526Signal operation "items" should include full paths2024-03-12T13:04:26-04:00David ThompsonSignal operation "items" should include full pathsItems inside extensible groups modified in a qtInstancedView do not report the group-index of the item within the group that was modified. This should happen. Two changes are required:
+ [`qtInstancedView.cxx:291`](https://gitlab.kitwar...Items inside extensible groups modified in a qtInstancedView do not report the group-index of the item within the group that was modified. This should happen. Two changes are required:
+ [`qtInstancedView.cxx:291`](https://gitlab.kitware.com/cmb/smtk/-/blob/2a35ddef2f9/smtk/extension/qt/qtInstancedView.cxx#L291) should report the item's path (via `Attribute::itemPath()`), not the item's name.
+ `Attribute::itemPath()` should find the indexes of items within groups and include them to match the syntax already parsed by `Attribute::itemAtPath()`.
The `data/attribute/attribute_collection/childrenItemsTest.sbt` test data can be used to verify that paths are properly reported.Robert M. O'BaraRobert M. O'Barahttps://gitlab.kitware.com/cmb/smtk/-/issues/525Create 24.01 Release2024-03-12T13:03:38-04:00Robert M. O'BaraCreate 24.01 Release<!--
This template is for tracking a release of smtk. Please replace the
following strings with the associated values:
- `VERSION`: e.g. yy.mm.n
- `MAJOR`: e.g. yy is the year
- `MINOR`: e.g. mm is the month
- `PATCH`: e.g. the ...<!--
This template is for tracking a release of smtk. Please replace the
following strings with the associated values:
- `VERSION`: e.g. yy.mm.n
- `MAJOR`: e.g. yy is the year
- `MINOR`: e.g. mm is the month
- `PATCH`: e.g. the release sequence number (start at 0)
- `BRANCHPOINT`: The commit where the release should be started - it is a point on master where the release process branch is started from. The release process branch will have multiple commits including the assembling of release notes and changing of the version.
Please remove this comment.
-->
# Preparatory steps
- Make sure you have run the `utility/SetupForDevelopment.sh` script.
- Update smtk guides
# Update smtk
- Update the local copy of the base branch.
- If `PATCH` is 0, update `master`
- Otherwise, update `release`
- [ ] `git fetch origin`
- [ ] `git checkout $branch`
- [ ] `git merge --ff-only origin/$branch`
- If this fails, there are local commits that need to be removed
- Ensure that changes intended for the release are in it.
- The [`backport-mrs.py`][backport-mrs] script can be used to find and
ensure that merge requests assigned to the associated milestone are
available on the `release` branch. See its documentation for usage.
- Integrate changes.
- Create branch for release commits
- [ ] `git checkout -b update-to-v24.01.0 BRANCHPOINT`
- Make a commit for each of these `release`-only changes:
- [x] Assemble release notes into `doc/release/smtk-24.01.rst`.
- [x] Top of release notes should have `.. _release-notes-24.01:` and a reference to the previous release's notes (See `doc/release/smtk-21.07.rst` or later for an example.)
- [x] Add reference to new release notes to `doc/release/index.rst`. (This publishes release notes on read-the-docs.)
- [x] Update the ReadMe file to refer to the new release notes
- [x] If `PATCH` is greater than 0, add items to the end of this file.
- [x] `git rm` all of the individual release note files *except* `00-example.rst`.
- [x] Do a git add for ReadMe, index.rst, and smtk-24.01.rst
- [x] `git commit -m 'Compile release notes for 24.01.0'`
- [x] Update `version.txt` and tag the commit (tag this commit below)
- [x] `echo 24.01.0 > version.txt`
- [x] Rebuild smtk to check for deprecation warnings
- [x] `git commit -m 'Update version number to 24.01.0' version.txt` (commit message must be verbatum)
- [x] Update `.gitlab/ci/cdash-groups.json` to track the `release` CDash
groups.
- [x] Change "master" => "release" everywhere in `.gitlab/ci/cdash-groups.json`,
and change "latest-master" => "latest-release".
- [x] `git commit -m 'Update cdash-groups.json to track the release group' .gitlab/ci/cdash-groups.json`
- Create a merge request targeting `release`
- [x] Obtain a GitLab API token for the `kwrobot.release.cmb` user (ask
@ben.boeckel if you do not have one)
- [x] Add the `kwrobot.release.cmb` user to your fork with at least
`Developer` privileges (so it can open MRs)
- [x] Use [the `release-mr`][release-mr] script to open the create the
Merge Request (see script for usage)
- Pull the script for each release; it may have been updated since it
was last used
- The script outputs the information it will be using to create the
merge request. Please verify that it is all correct before creating
the merge request. See usage at the top of the script to provide
information that is either missing or incorrect (e.g., if its data
extraction heuristics fail).
- [x] Get positive review
- [x] Get a repo maintainer (currently Ben) or owner (currently Bob) to`Do: merge`
- [x] Get a repo maintainer or ownder to push the tag to the main repository
- [x] `git tag -a -m 'SMTK 24.01.0' v24.01.0 commit-that-updated-version.txt`
- [x] `git push origin v24.01.0`
- Software process updates (these can all be done independently)
- [x] Update kwrobot with the new `release` branch rules (@ben.boeckel)
- [x] Run [this script][cdash-update-groups] to update the CDash groups
- This must be done after a nightly run to ensure all builds are in the
`release` group
- See the script itself for usage documentation
- [x] Add (or update if `PATCH` is greater than 0) version selection entry
in cmb-superbuild
[backport-mrs]: https://gitlab.kitware.com/utils/release-utils/-/blob/master/backport-mrs.py
[release-mr]: https://gitlab.kitware.com/utils/release-utils/-/blob/master/release-mr.py
[cdash-update-groups]: https://gitlab.kitware.com/utils/cdash-utils/-/blob/master/cdash-update-groups.py
# Post-release
- [x] Write and publish blog post with release notes.
- [x] Post an announcement in the Announcements category on
[discourse.smtk.org](https://discourse.kitware.com/c/smtk/).
- [x] Create a new commit on `master` that does the following:
- [x] Remove the deprecated methods on `master`. Note that it should be discussed before hand which deprecated methods should be removed in this release.
- [x] Set the version.txt on `master` to be yy.mm.100
/cc @ben.boeckel
/cc @bob.obara
/cc @dcthompRobert M. O'BaraRobert M. O'Barahttps://gitlab.kitware.com/cmb/smtk/-/issues/523Task selection buttons crash modelbuilder2024-01-19T14:44:29-05:00Jason LuckhardtTask selection buttons crash modelbuilderReproduction steps:
1. Launch Modelbuilder with the latest SMTK.
2. Navigate to the Task Editor.
3. Click Select, Connect, Select.
4. Modelbuilder crashes.
qtConnectMode.cxx probably just needs a nullptr check on m_previewArc.
![image](...Reproduction steps:
1. Launch Modelbuilder with the latest SMTK.
2. Navigate to the Task Editor.
3. Click Select, Connect, Select.
4. Modelbuilder crashes.
qtConnectMode.cxx probably just needs a nullptr check on m_previewArc.
![image](/uploads/b0a2312d48f225057d229122e8bbda59/image.png)
```
Loguru caught a signal: SIGSEGV
Stack trace:
3 0x7ff26f27c468 smtk::extension::qtTaskEditor::modeChangeRequested(QAction*) + 422
2 0x7ff26f25a628 smtk::extension::qtConnectMode::exitMode() + 142
1 0x7ff26f27414f smtk::extension::qtPreviewArc::setPredecessor(smtk::extension::qtBaseTaskNode*) + 51
0 0x7ff25170e420 /lib/x86_64-linux-gnu/libpthread.so.0(+0x14420) [0x7ff25170e420]
( 37.455s) [paraview ] :0 FATL| Signal: SIGSEGV
Segmentation fault (core dumped)
```
Thanks!https://gitlab.kitware.com/cmb/smtk/-/issues/520Modifying resources should modify project2023-11-29T18:28:53-05:00David ThompsonModifying resources should modify project`smtk::operation::extractResources()` should be modified to not just include resources owning modified components but also projects owning those resources. This way, when any resource of a project is marked dirty, the project is also mar...`smtk::operation::extractResources()` should be modified to not just include resources owning modified components but also projects owning those resources. This way, when any resource of a project is marked dirty, the project is also marked dirty.Robert M. O'BaraRobert M. O'Barahttps://gitlab.kitware.com/cmb/smtk/-/issues/518Missing definition for templated version of smtk::project::Manager::unregiste...2023-10-24T14:43:29-04:00jwilson1881Missing definition for templated version of smtk::project::Manager::unregisterProject()The definition for the templated smtk::project::Manager::unregisterProject() method is missing and results in linker issues.The definition for the templated smtk::project::Manager::unregisterProject() method is missing and results in linker issues.https://gitlab.kitware.com/cmb/smtk/-/issues/517Handle specific exception in implementation of from_json for smtk::task::Task2023-10-26T12:08:06-04:00jwilson1881Handle specific exception in implementation of from_json for smtk::task::TaskThe current implementation of task deserializer is the following:
```
void from_json(const nlohmann::json& jj, smtk::task::Task::Ptr& task)
{
try
{
auto& helper = json::Helper::instance();
auto managers = helper.managers();
...The current implementation of task deserializer is the following:
```
void from_json(const nlohmann::json& jj, smtk::task::Task::Ptr& task)
{
try
{
auto& helper = json::Helper::instance();
auto managers = helper.managers();
auto& taskManager = helper.taskManager();
auto taskType = jj.at("type").get<std::string>();
task = taskManager.taskInstances().createFromName(
taskType, const_cast<nlohmann::json&>(jj), managers);
if (jj.contains("active") && jj.at("active").get<bool>())
{
helper.setActiveSerializedTask(task.get());
}
}
catch (std::exception& e)
{
smtkErrorMacro(
smtk::io::Logger::instance(), "Could not deserialize task (" << e.what() << ").");
}
}
```
If my custom task implementation throws any exception, creation of the task will fail result in a nullptr for the task and then a crash. The catch block here should probably be more specific about the types of exceptions that will be handled here and all other serializer/deserializer implementation should do the same.David ThompsonDavid Thompsonhttps://gitlab.kitware.com/cmb/smtk/-/issues/514SMTK Multithread Logging Issue2023-06-30T15:45:37-04:00RohithSMTK Multithread Logging IssueWhen Attributes are read in parallel, one attribute's reader log is reset by another attribute's reader log. Flush the log before resetting.
@bob.obara @dcthompWhen Attributes are read in parallel, one attribute's reader log is reset by another attribute's reader log. Flush the log before resetting.
@bob.obara @dcthomphttps://gitlab.kitware.com/cmb/smtk/-/issues/513Missing export of smtk/operation/Hints header2023-06-20T13:09:48-04:00RohithMissing export of smtk/operation/Hints headersmtk/operation/Hints.h is not exported to install directory. Need to add it to the smtk/Operation/CMakeLists.txt
@dcthomp @bob.obarasmtk/operation/Hints.h is not exported to install directory. Need to add it to the smtk/Operation/CMakeLists.txt
@dcthomp @bob.obaraDavid ThompsonDavid Thompsonhttps://gitlab.kitware.com/cmb/smtk/-/issues/511ACE3P contract test fails2023-05-30T10:25:03-04:00John TourtellottACE3P contract test failsThe ACE3P contract test fails after !2865 is merged. The specific test in https://gitlab.kitware.com/cmb/plugins/ace3p-extensions is `test_to_jobrecordPy`.
The test code (`test_to_jobrecord.py`) was updated to set `smtk::operator::Manag...The ACE3P contract test fails after !2865 is merged. The specific test in https://gitlab.kitware.com/cmb/plugins/ace3p-extensions is `test_to_jobrecordPy`.
The test code (`test_to_jobrecord.py`) was updated to set `smtk::operator::Managers`:
```
managers = smtk.common.Managers.create()
managers.insert_or_assign(self.res_manager)
managers.insert_or_assign(self.op_manager)
managers.insert_or_assign(self.proj_manager)
self.op_manager.setManagers(managers)
```
* A known problem is that `managers` should be changed to `self.managers` so that it doesn't go out of scope.
* After fixing that, there is still an error
```
.../ace3p-extensions/smtk/simulation/ace3p/Stage.h:66 model resource missing ace3p property
```
Added code to "register" `smtk.session.vtk` with the resource and operation managers, but the error remains.John TourtellottJohn Tourtellotthttps://gitlab.kitware.com/cmb/smtk/-/issues/509New project shortcut must be changed2023-04-12T09:21:04-04:00David ThompsonNew project shortcut must be changedThe Ctrl+P shortcut that "New Project…" uses is also used by ParaView's widgets for point picking. Since there is currently no way to change the widget shortcut, we must change the "New Project…" QAction.
An alternative would be Shift+C...The Ctrl+P shortcut that "New Project…" uses is also used by ParaView's widgets for point picking. Since there is currently no way to change the widget shortcut, we must change the "New Project…" QAction.
An alternative would be Shift+Ctrl+P.David ThompsonDavid Thompsonhttps://gitlab.kitware.com/cmb/smtk/-/issues/508Release SMTK 23.04.02023-07-06T16:34:41-04:00Robert M. O'BaraRelease SMTK 23.04.0
# Preparatory steps
- Make sure you have run the `utility/SetupForDevelopment.sh` script.
- Update smtk guides
# Update smtk
- Update the local copy of the base branch.
- If `PATCH` is 0, update `master`
- Otherwise, u...
# Preparatory steps
- Make sure you have run the `utility/SetupForDevelopment.sh` script.
- Update smtk guides
# Update smtk
- Update the local copy of the base branch.
- If `PATCH` is 0, update `master`
- Otherwise, update `release`
- [x] `git fetch origin`
- [x] `git checkout $branch`
- [x] `git merge --ff-only origin/$branch`
- If this fails, there are local commits that need to be removed
- Ensure that changes intended for the release are in it.
- The [`backport-mrs.py`][backport-mrs] script can be used to find and
ensure that merge requests assigned to the associated milestone are
available on the `release` branch. See its documentation for usage.
- Integrate changes.
- Create branch for release commits
- [x] `git checkout -b update-to-v23.04.0 bcf281df3db8c9424761e7c3069233950ee77d95`
- Make a commit for each of these `release`-only changes:
- [x] Assemble release notes into `doc/release/smtk-23.04.rst`.
- [x] Top of release notes should have `.. _release-notes-23.04:` and a reference to the previous release's notes (See `doc/release/smtk-21.07.rst` or later for an example.)
- [x] Add reference to new release notes to `doc/release/index.rst`. (This publishes release notes on read-the-docs.)
- [x] Update the ReadMe file to refer to the new release notes
- [x] If `PATCH` is greater than 0, add items to the end of this file.
- [x] `git rm` all of the individual release note files *except* `00-example.rst`.
- [x] Do a git add for ReadMe, index.rst, and smtk-23.04.rst
- [x] `git commit -m 'Compile release notes for 23.04.0'`
- [ ] Update `version.txt` and tag the commit (tag this commit below)
- [x] `echo 23.04.0 > version.txt`
- [x] Rebuild smtk to check for deprecation warnings
- [ ] `git commit -m 'Update version number to 23.04.0' version.txt` (commit message must be verbatum)
- [ ] Update `.gitlab/ci/cdash-groups.json` to track the `release` CDash
groups.
- [x] Change "master" => "release" everywhere in `.gitlab/ci/cdash-groups.json`,
and change "latest-master" => "latest-release".
- [x] `git commit -m 'Update cdash-groups.json to track the release group' .gitlab/ci/cdash-groups.json`
- Create a merge request targeting `release`
- [x] Obtain a GitLab API token for the `kwrobot.release.cmb` user (ask
@ben.boeckel if you do not have one)
- [x] Add the `kwrobot.release.cmb` user to your fork with at least
`Developer` privileges (so it can open MRs)
- [x] Use [the `release-mr`][release-mr] script to open the create the
Merge Request (see script for usage)
- Pull the script for each release; it may have been updated since it
was last used
- The script outputs the information it will be using to create the
merge request. Please verify that it is all correct before creating
the merge request. See usage at the top of the script to provide
information that is either missing or incorrect (e.g., if its data
extraction heuristics fail).
- [x] Get positive review
- [x] Get a repo maintainer (currently Ben) or owner (currently Bob) to`Do: merge`
- [x] Get a repo maintainer or ownder to push the tag to the main repository
- [x] `git tag -a -m 'SMTK 23.04.0' v23.04.0 commit-that-updated-version.txt`
- [x] `git push origin v23.04.0`
- Software process updates (these can all be done independently)
- [x] Update kwrobot with the new `release` branch rules (@ben.boeckel)
- [x] Run [this script][cdash-update-groups] to update the CDash groups
- This must be done after a nightly run to ensure all builds are in the
`release` group
- See the script itself for usage documentation
- [ ] Add (or update if `PATCH` is greater than 0) version selection entry
in cmb-superbuild
[backport-mrs]: https://gitlab.kitware.com/utils/release-utils/-/blob/master/backport-mrs.py
[release-mr]: https://gitlab.kitware.com/utils/release-utils/-/blob/master/release-mr.py
[cdash-update-groups]: https://gitlab.kitware.com/utils/cdash-utils/-/blob/master/cdash-update-groups.py
# Post-release
- [ ] Write and publish blog post with release notes.
- [ ] Post an announcement in the Announcements category on
[discourse.smtk.org](https://discourse.kitware.com/c/smtk/).
- [ ] Create a new commit on `master` that does the following:
- [ ] Remove the deprecated methods on `master`. Note that it should be discussed before hand which deprecated methods should be removed in this release.
- [ ] Set the version.txt on `master` to be 23.04.100
/cc @ben.boeckel
/cc @bob.obara
/cc @dcthompRobert M. O'BaraRobert M. O'Barahttps://gitlab.kitware.com/cmb/smtk/-/issues/506Create SMTK 23.01 Release2023-02-24T14:51:13-05:00Robert M. O'BaraCreate SMTK 23.01 Release<!--
This template is for tracking a release of smtk. Please replace the
following strings with the associated values:
- `VERSION`: e.g. yy.mm.n
- `MAJOR`: e.g. yy is the year
- `MINOR`: e.g. mm is the month
- `PATCH`: e.g. the ...<!--
This template is for tracking a release of smtk. Please replace the
following strings with the associated values:
- `VERSION`: e.g. yy.mm.n
- `MAJOR`: e.g. yy is the year
- `MINOR`: e.g. mm is the month
- `PATCH`: e.g. the release sequence number (start at 0)
- `BRANCHPOINT`: The commit where the release should be started - it is a point on master where the release process branch is started from. The release process branch will have multiple commits including the assembling of release notes and changing of the version.
Please remove this comment.
-->
# Preparatory steps
- Make sure you have run the `utility/SetupForDevelopment.sh` script.
- Update smtk guides
# Update smtk
- Update the local copy of the base branch.
- If `PATCH` is 0, update `master`
- Otherwise, update `release`
- [x] `git fetch origin`
- [x] `git checkout $branch`
- [x] `git merge --ff-only origin/$branch`
- If this fails, there are local commits that need to be removed
- Ensure that changes intended for the release are in it.
- The [`backport-mrs.py`][backport-mrs] script can be used to find and
ensure that merge requests assigned to the associated milestone are
available on the `release` branch. See its documentation for usage.
- Integrate changes.
- Create branch for release commits
- [x] `git checkout -b update-to-v23.01.0 618a8290247a89a67ecfe2dfe4833d914c0aef13`
- Make a commit for each of these `release`-only changes:
- [ ] Assemble release notes into `doc/release/smtk-23.01.rst`.
- [x] Top of release notes should have `.. _release-notes-23.01:` and a reference to the previous release's notes (See `doc/release/smtk-21.07.rst` or later for an example.)
- [x] Add reference to new release notes to `doc/release/index.rst`. (This publishes release notes on read-the-docs.)
- [x] Update the ReadMe file to refer to the new release notes
- [ ] If `PATCH` is greater than 0, add items to the end of this file.
- [x] `git rm` all of the individual release note files *except* `00-example.rst`.
- [x] Do a git add for ReadMe, index.rst, and smtk-23.01.rst
- [x] `git commit -m 'Compile release notes for 23.01.0'`
- [ ] Update `version.txt` and tag the commit (tag this commit below)
- [x] `echo 23.01.0 > version.txt`
- [x] Rebuild smtk to check for deprecation warnings
- [x] `git commit -m 'Update version number to 23.01.0' version.txt` (commit message must be verbatum)
- [ ] Update `.gitlab/ci/cdash-groups.json` to track the `release` CDash
groups.
- [x] Change "master" => "release" everywhere in `.gitlab/ci/cdash-groups.json`,
and change "latest-master" => "latest-release".
- [x] `git commit -m 'Update cdash-groups.json to track the release group' .gitlab/ci/cdash-groups.json`
- Create a merge request targeting `release`
- [x] Obtain a GitLab API token for the `kwrobot.release.cmb` user (ask
@ben.boeckel if you do not have one)
- [x] Add the `kwrobot.release.cmb` user to your fork with at least
`Developer` privileges (so it can open MRs)
- [x] Use [the `release-mr`][release-mr] script to open the create the
Merge Request (see script for usage)
- Pull the script for each release; it may have been updated since it
was last used
- The script outputs the information it will be using to create the
merge request. Please verify that it is all correct before creating
the merge request. See usage at the top of the script to provide
information that is either missing or incorrect (e.g., if its data
extraction heuristics fail).
- [x] Get positive review
- [x] Get a repo maintainer (currently Ben) or owner (currently Bob) to`Do: merge`
- [ ] Get a repo maintainer or ownder to push the tag to the main repository
- [x] `git tag -a -m 'SMTK 23.01.0' v23.01.0 commit-that-updated-version.txt`
- [x] `git push origin v23.01.0`
- Software process updates (these can all be done independently)
- [x] Update kwrobot with the new `release` branch rules (@ben.boeckel)
- [x] Run [this script][cdash-update-groups] to update the CDash groups
- This must be done after a nightly run to ensure all builds are in the
`release` group
- See the script itself for usage documentation
- [ ] Add (or update if `PATCH` is greater than 0) version selection entry
in cmb-superbuild
[backport-mrs]: https://gitlab.kitware.com/utils/release-utils/-/blob/master/backport-mrs.py
[release-mr]: https://gitlab.kitware.com/utils/release-utils/-/blob/master/release-mr.py
[cdash-update-groups]: https://gitlab.kitware.com/utils/cdash-utils/-/blob/master/cdash-update-groups.py
# Post-release
- [x] Write and publish blog post with release notes.
- [x] Post an announcement in the Announcements category on
[discourse.smtk.org](https://discourse.kitware.com/c/smtk/).
- [x] Create a new commit on `master` that does the following:
- [x] Remove the deprecated methods on `master`. Note that it should be discussed before hand which deprecated methods should be removed in this release.
- [x] Set the version.txt on `master` to be 23.01.100
/cc @ben.boeckel
/cc @bob.obara
/cc @dcthompRobert M. O'BaraRobert M. O'Barahttps://gitlab.kitware.com/cmb/smtk/-/issues/504Need to address SCCACHE Issue2023-10-02T16:30:49-04:00Robert M. O'BaraNeed to address SCCACHE IssueI needed to switch off sccache cause it was finding the wrong header files - in this case Deprecation.hI needed to switch off sccache cause it was finding the wrong header files - in this case Deprecation.hBen BoeckelBen Boeckelhttps://gitlab.kitware.com/cmb/smtk/-/issues/503Create SMTK 22.11 Release2023-01-27T11:46:40-05:00Robert M. O'BaraCreate SMTK 22.11 Release<!--
This template is for tracking a release of smtk. Please replace the
following strings with the associated values:
- `VERSION`: e.g. yy.mm.n
- `MAJOR`: e.g. yy is the year
- `MINOR`: e.g. mm is the month
- `PATCH`: e.g. the ...<!--
This template is for tracking a release of smtk. Please replace the
following strings with the associated values:
- `VERSION`: e.g. yy.mm.n
- `MAJOR`: e.g. yy is the year
- `MINOR`: e.g. mm is the month
- `PATCH`: e.g. the release sequence number (start at 0)
- `BRANCHPOINT`: The commit where the release should be started - it is a point on master where the release process branch is started from. The release process branch will have multiple commits including the assembling of release notes and changing of the version.
Please remove this comment.
-->
# Preparatory steps
- Make sure you have run the `utility/SetupForDevelopment.sh` script.
- Update smtk guides
# Update smtk
- Update the local copy of the base branch.
- If `PATCH` is 0, update `master`
- Otherwise, update `release`
- [x] `git fetch origin`
- [x] `git checkout $branch`
- [x] `git merge --ff-only origin/$branch`
- If this fails, there are local commits that need to be removed
- Ensure that changes intended for the release are in it.
- The [`backport-mrs.py`][backport-mrs] script can be used to find and
ensure that merge requests assigned to the associated milestone are
available on the `release` branch. See its documentation for usage.
- Integrate changes.
- Create branch for release commits
- [x] `git checkout -b update-to-v22.11.0 752dcc77e2df12fc1306ce42049a4bcdf1e533ba`
- Make a commit for each of these `release`-only changes:
- [x] Assemble release notes into `doc/release/smtk-22.11.rst`.
- [x] Top of release notes should have `.. _release-notes-22.11:` and a reference to the previous release's notes (See `doc/release/smtk-21.07.rst` or later for an example.)
- [x] Add reference to new release notes to `doc/release/index.rst`. (This publishes release notes on read-the-docs.)
- [x] Update the ReadMe file to refer to the new release notes
- [x] If `PATCH` is greater than 0, add items to the end of this file.
- [x] `git rm` all of the individual release note files *except* `00-example.rst`.
- [x] Do a git add for ReadMe, index.rst, and smtk-22.11.rst
- [x] `git commit -m 'Compile release notes for 22.11.0'`
- [x] Update `version.txt` and tag the commit (tag this commit below)
- [x] `echo 22.11.0 > version.txt`
- [x] Rebuild smtk to check for deprecation warnings
- [x] `git commit -m 'Update version number to 22.11.0' version.txt` (commit message must be verbatum)
- [x] Update `.gitlab/ci/cdash-groups.json` to track the `release` CDash
groups.
- [x] Change "master" => "release" everywhere in `.gitlab/ci/cdash-groups.json`,
and change "latest-master" => "latest-release".
- [x] `git commit -m 'Update cdash-groups.json to track the release group' .gitlab/ci/cdash-groups.json`
- Create a merge request targeting `release`
- [x] Obtain a GitLab API token for the `kwrobot.release.cmb` user (ask
@ben.boeckel if you do not have one)
- [x] Add the `kwrobot.release.cmb` user to your fork with at least
`Developer` privileges (so it can open MRs)
- [x] Use [the `release-mr`][release-mr] script to open the create the
Merge Request (see script for usage)
- Pull the script for each release; it may have been updated since it
was last used
- The script outputs the information it will be using to create the
merge request. Please verify that it is all correct before creating
the merge request. See usage at the top of the script to provide
information that is either missing or incorrect (e.g., if its data
extraction heuristics fail).
- [x] Get positive review
- [x] Get a repo maintainer (currently Ben) or owner (currently Bob) to`Do: merge`
- [x] Get a repo maintainer or ownder to push the tag to the main repository
- [x] `git tag -a -m 'SMTK 22.11.0' v22.11.0 commit-that-updated-version.txt`
- [x] `git push origin v22.11.0`
- Software process updates (these can all be done independently)
- [x] Update kwrobot with the new `release` branch rules (@ben.boeckel)
- [x] Run [this script][cdash-update-groups] to update the CDash groups
- This must be done after a nightly run to ensure all builds are in the
`release` group
- See the script itself for usage documentation
- [ ] Add (or update if `PATCH` is greater than 0) version selection entry
in cmb-superbuild
[backport-mrs]: https://gitlab.kitware.com/utils/release-utils/-/blob/master/backport-mrs.py
[release-mr]: https://gitlab.kitware.com/utils/release-utils/-/blob/master/release-mr.py
[cdash-update-groups]: https://gitlab.kitware.com/utils/cdash-utils/-/blob/master/cdash-update-groups.py
# Post-release
- [ ] Write and publish blog post with release notes.
- [ ] Post an announcement in the Announcements category on
[discourse.smtk.org](https://discourse.kitware.com/c/smtk/).
- [x] Create a new commit on `master` that does the following:
- [x] Remove the deprecated methods on `master`. Note that it should be discussed before hand which deprecated methods should be removed in this release.
- [x] Set the version.txt on `master` to be yy.mm.100
/cc @ben.boeckel
/cc @bob.obara
/cc @dcthompRobert M. O'BaraRobert M. O'Barahttps://gitlab.kitware.com/cmb/smtk/-/issues/500qtReferenceItem and qtResourceBrowser has strange interaction with mouse clicks2022-09-15T11:44:57-04:00Robert M. O'BaraqtReferenceItem and qtResourceBrowser has strange interaction with mouse clicksIf you double click on the badges it will sometimes not trigger the badge action but instead can change the qt selection or edit item name (as in the case of the Resource Browser.If you double click on the badges it will sometimes not trigger the badge action but instead can change the qt selection or edit item name (as in the case of the Resource Browser.Robert M. O'BaraRobert M. O'Bara