You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If possible, I would suggest to adapt the integration of Swate.
It's confusing that the look and feel changes inside ARCitect without having updated.
Would it be sensible to have two instances of Swate running (stable / production and dev / latest), so that only with an update of ARCitect one would change to a new version?
Plus the updates from one Swate release to another could be included in the release log of ARCitect to more transparently communicate the changes with users (and data stewards).
Would it be sensible to have two instances of Swate running (stable / production and dev / latest)
This is indeed planned and will soon be done! Then users can change swate target inside of ARCitect.
... so that only with an update of ARCitect one would change to a new version?
This is not the result of having a production and a dev version of swate running.
We would need a version of swate running for every swate release we do and every arcitect version specifies the target swate version. Which is simply not feasible.
If possible, I would suggest to adapt the integration of Swate.
It's confusing that the look and feel changes inside ARCitect without having updated.
Would it be sensible to have two instances of Swate running (stable / production and dev / latest), so that only with an update of ARCitect one would change to a new version?
Plus the updates from one Swate release to another could be included in the release log of ARCitect to more transparently communicate the changes with users (and data stewards).
@Freymaurer
@SabrinaZander
The text was updated successfully, but these errors were encountered: