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
Release 5.0 has been in progress for years. It is a big improvement compared to 4.2 and it has been difficult for us to use the latest stable version in our documentation when the latest version is much better but we can't reference it consistently because of broken links that often happen (or will happen in the future) and no way to use wstg ids in the format of wstg-version-category-id.
can we get a release soon or at least an eta for 5.0? multiple releases exist guys for a reason lol, let's get the 5.0 and have 5.1 later one when needed, at least we get something more up to date compared to 4.2
The text was updated successfully, but these errors were encountered:
Release 5.0 has been in progress for years. It is a big improvement compared to 4.2
Is it? I'm not sure everyone would agree.
and it has been difficult for us to use the latest stable version in our documentation when the latest version is much better but we can't reference it consistently because of broken links that often happen (or will happen in the future) and no way to use wstg ids in the format of wstg-version-category-id.
Important
You can refer to and use the documented linking guidance:
Release 5.0 has been in progress for years. It is a big improvement compared to 4.2 and it has been difficult for us to use the latest stable version in our documentation when the latest version is much better but we can't reference it consistently because of broken links that often happen (or will happen in the future) and no way to use wstg ids in the format of wstg-version-category-id.
can we get a release soon or at least an eta for 5.0? multiple releases exist guys for a reason lol, let's get the 5.0 and have 5.1 later one when needed, at least we get something more up to date compared to 4.2
The text was updated successfully, but these errors were encountered: