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
{{ message }}
This repository has been archived by the owner on Jan 31, 2025. It is now read-only.
The releaser sees the list of Boxo and Kubo commits that are in master/main that aren't being included in the current release.
The release issue is also updated with this information.
Why Important
Especially now that fixes are often made in Boxo but need to be bubbled up to Kubo, it's easier to have a Kubo release not include all the desired functionality. We had this in happen in 0.20 (see here). This either frustrates users and/or creates extra work for the maintainers having to do extra followup releases.
Notes
I hypothesize that seeing this list and having it get added to the release issue (which others are subscribed to) will help trigger if we're missing something important.
The text was updated successfully, but these errors were encountered:
@galargh : if possible, I'd like to improve this before 0.21. Also, if you have better ideas on how to do this rather than printing to console and posting to the release issue, feel free to share.
I want to make sure that someone not executing the release will still have visibility into this set of commits that aren't included. If I understand correctly, the set of commits will make it into the release PR description. The release PR also references the release issue (which causes a backlink from the release issue to the release PR). As a result, it should be self-service for someone to discover and see this easily enough. Correct me if I have this wrong.
Done Criteria
The releaser sees the list of Boxo and Kubo commits that are in master/main that aren't being included in the current release.
The release issue is also updated with this information.
Why Important
Especially now that fixes are often made in Boxo but need to be bubbled up to Kubo, it's easier to have a Kubo release not include all the desired functionality. We had this in happen in 0.20 (see here). This either frustrates users and/or creates extra work for the maintainers having to do extra followup releases.
Notes
I hypothesize that seeing this list and having it get added to the release issue (which others are subscribed to) will help trigger if we're missing something important.
The text was updated successfully, but these errors were encountered: