Release Remediation - Besu - LF Decentralized Trust


    
        
            
                
                                

        


        
            

            






Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
PreferencesOnly necessaryAccept all









LF Decentralized Trust

LF Decentralized Trust

Spaces

Apps
Templates

Create
























Besu




	All content



Shortcuts



	Meetings

Meetings


 This trigger is hidden

	How-to articles

How-to articles


 This trigger is hidden






Content







Results will update as you type.

	Code of Conduct





	Contributing





	Developing and Conventions




	Besu CLI Style Guide





	Coding Conventions





	Changelog





	Testing





	Debugging Besu in IntelliJ





	Releasing




	Release Rotations 2024





	Using CalVer for Besu Releases





	How to do a Besu Release





	Off-cycle release process





	Release Process





	Obsolete Proposals and Policies





	Archive




	Critical Issue for Privacy Users





	Mainnet Consensus Bug Identified and Resolved in Hyperledger Besu





	Release 22.1.0





	Release Process Improvement





	Release Remediation





	Release Rotations 2021





	Release Rotations 2022





	Release Rotations 2023









	Bug Triage Process





	Policies





	Plugin Services





	Tools we use





	Advanced





	Repositories and other projects





	Archive (Dev)





	Changelog Improvement Proposal





	Logging





	Building from source







	Documentation





	Community





	Governance





	Programs & Grants





	Meetings





	Design Documents





	Security





	Audits





	Start Here





	Performance & Stability





	How-to articles





	Incident Reports





	Besu Roadmap & Planning





	How to Contribute



















You‘re viewing this with anonymous access, so some content might be blocked.
Close













Besu

/
Release Remediation












More actions







Release Remediation

	Christopher Hare



	Madeline Murray (Deactivated)





Owned by Christopher Hare


Last updated: Apr 19, 2020










What to do when a defect has been discovered in a release version of Besu?
GitHub
Nothing. 
The history is GitHub (release tags and commits) are never rewritten when a defect or bug is discovered. It serves as a record of history, documented what has happened over the course of Besu's lifetime.
Binary Artefact
When a defect is found that causes data corruption in common cases or significant security breach, then that artefact may be removed from the Binary Artefact store.
Changelog and Communication 
For significant defects including where a release is not usable in common cases, the Changelog is updated and a post is made to the besu and besu-contributors channels on RocketChat. 







, multiple selections available,release


artefact


remediation






























































        

    


    {"serverDuration": 12, "requestCorrelationId": "223300938f914d29bb73fbf3b57b203c"}