Using CalVer for Besu Releases - 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







	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

/
Using CalVer for Besu Releases












More actions







Using CalVer for Besu Releases

	Danno Ferrin



	Justin Florentine



	Tim Beiko



	Sally MacFarlane





Owned by Danno Ferrin


Last updated: Jun 10, 2024 by Justin Florentine










On 17 Sep 2020 the Hyperledger TSC voted to Allow projects to use CalVer or SemVer.  
General background on Calendar Versioning (CalVer) - https://calver.org/
CalVer taxonomy: YY.M.patch
	YY: Year (20, 21, 22, etc.)

	M: Month (1, 2, 3, ..., 11, 12). 
	Patch: Fortnightly releases, or whenever sub-month releases happen.
	YY.M.patch: The year and month are from the current month. 

Breaking Changes Policy
	No intentional backwards incompatible breaking changes should occur without 3 months of prior notice via the deprecation policy.	Java Plugin APIs
	CLI flags and configuration files
	On-disk storage compatibility
	JSON-RPC APIs


	Patches may introduce forwards compatible changes, such as (but not limited to) new features, new fork or chain support, and new JSON-RPC apis.
	A notice for an intentional breaking change should be in the CHANGELOG.md file for at least 3 months. 
	Examples of such changes:	Changing the required JDK.  (such as when we went form Java 17 to Java 21).
	Removing storage formats, or required migrations.
	Dropping obsolete CLI flags, such as the whitelist series flags (replaced by the allowlist series)


	This breaking change policy will not prohibit rapid release of security related updates.








, multiple selections available,





Related content
More info

Collapse
Allow projects to use CalVer or SemVer
Allow projects to use CalVer or SemVer

Technical Oversight Committee



More like this






2021-11-09 Besu Contributor Call
2021-11-09 Besu Contributor Call

Besu



More like this






2021 Q4 Hyperledger Besu
2021 Q4 Hyperledger Besu

Technical Oversight Committee



More like this






2021 Q3 Hyperledger Besu
2021 Q3 Hyperledger Besu

Technical Oversight Committee



More like this






2020 Q3 Hyperledger Besu
2020 Q3 Hyperledger Besu

Technical Oversight Committee



More like this






Release Rotations 2023
Release Rotations 2023

Besu



More like this

































































        

    


    {"serverDuration": 34, "requestCorrelationId": "dfc2e7c705ea439ca9b62dbd81b52536"}