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
Bitwarden releases are currently tagged for each client and the history for each release can be browsed there. However, the difficulty comes when wanting to track what has been implemented (and not) in each release. All releases are divergent from the main branch however there is no way to track where the tag diverged from without comparing the tag history to the main branch history. This is inefficient and the local branches that are certainly maintained for Browser/Web/Desktop/CLI should be made public for more easy tracking.
For example, if I want to track what the current tagged release for the Browser release is I first have to go to the tag and main and see where the tag's history diverges from the main history. For the current tag, https://github.com/bitwarden/clients/tree/desktop-v2024.9.0, that is 456b156, a commit from 2 week ago
Issue Tracking Info
I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
The text was updated successfully, but these errors were encountered:
Issue
Bitwarden releases are currently tagged for each client and the history for each release can be browsed there. However, the difficulty comes when wanting to track what has been implemented (and not) in each release. All releases are divergent from the
main
branch however there is no way to track where the tag diverged from without comparing the tag history to themain
branch history. This is inefficient and the local branches that are certainly maintained for Browser/Web/Desktop/CLI should be made public for more easy tracking.For example, if I want to track what the current tagged release for the Browser release is I first have to go to the tag and main and see where the tag's history diverges from the main history. For the current tag, https://github.com/bitwarden/clients/tree/desktop-v2024.9.0, that is 456b156, a commit from 2 week ago
Issue Tracking Info
The text was updated successfully, but these errors were encountered: