Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Announcement issue for user-facing changes #228

Open
maxfischer2781 opened this issue Feb 3, 2022 · 1 comment
Open

Announcement issue for user-facing changes #228

maxfischer2781 opened this issue Feb 3, 2022 · 1 comment

Comments

@maxfischer2781
Copy link
Member

maxfischer2781 commented Feb 3, 2022

This is an announcement issue for changes relevant to users of TARDIS. If you run a TARDIS instance or maintain a plugin, please subscribe to notifications for this issue.

In case of questions, head to the Matterminers chat.


Overview of current changes and deprecations:


Instructions for TARDIS maintainers:

  • Keep the top-level listing up to date by editing it as appropriate.

    • Link to the announcement comments of upcomming and recent changes.
  • Announce upcoming changes by adding a comment to this issue.

    • Provide a short description targeted at users of TARDIS.
    • Include the expected version of change/deprecation/removal.
  • Announce releases with notable changes by adding a comment to this issue.

    • Link to the announcement comments of the changes affected by the release.
@maxfischer2781 maxfischer2781 pinned this issue Feb 3, 2022
@maxfischer2781
Copy link
Member Author

The internal HTCondor resource identifier format is changed from ClusterId to ClusterId.ProcId.

  • v0.7.0: New resources automatically use the new format. Existing resources with an old resource identifier are automatically mapped to the new format. No active changes are required.
  • v0.8.0: The automatic mapping is disabled. Resources created with the old format cannot be managed anymore.

In effect, this means that when using the HTCondor site adapter on a pre-v0.7.0 TARDIS, one should:

  • take no special measures when updating to v0.7.X.
  • wait for all resources to complete when updating to v0.8.X without updating to v0.7.X first.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant