forked from toolshed/abra
		
	Compare commits
	
		
			4 Commits
		
	
	
		
			0.1.0-alph
			...
			0.1.1-alph
		
	
	| Author | SHA1 | Date | |
|---|---|---|---|
| 48bc03db51 | |||
| f0e966afc3 | |||
| a1d1166308 | |||
| 1438fdf3c2 | 
@ -22,6 +22,7 @@ archives:
 | 
			
		||||
      linux: Linux
 | 
			
		||||
      386: i386
 | 
			
		||||
      amd64: x86_64
 | 
			
		||||
    format: binary
 | 
			
		||||
checksum:
 | 
			
		||||
  name_template: "checksums.txt"
 | 
			
		||||
snapshot:
 | 
			
		||||
 | 
			
		||||
@ -54,11 +54,9 @@ Please use the [conventional commit format](https://www.conventionalcommits.org/
 | 
			
		||||
 | 
			
		||||
## Versioning
 | 
			
		||||
 | 
			
		||||
We use [goreleaser](https://goreleaser.com) to help us automate releases. We
 | 
			
		||||
use [semver](https://semver.org) for versioning all releases of the tool. While
 | 
			
		||||
we are still in the public alpha release phase, we will maintain a
 | 
			
		||||
`0.y.z-alpha` format. Change logs are generated from our commit logs. We are
 | 
			
		||||
still working this out and aim to refine our release praxis as we go.
 | 
			
		||||
We use [goreleaser](https://goreleaser.com) to help us automate releases. We use [semver](https://semver.org) for versioning all releases of the tool. While we are still in the public alpha release phase, we will maintain a `0.y.z-alpha` format. Change logs are generated from our commit logs. We are still working this out and aim to refine our release praxis as we go.
 | 
			
		||||
 | 
			
		||||
For developers, while using this `-alpha` format, the `y` part is the "major" version part. So, if you make breaking changes, you increment that and _not_ the `x` part. So, if you're on `0.1.0-alpha`, then you'd go to `0.1.1-alpha` for a backwards compatible change and `0.2.0-alpha` for a backwards incompatible change.
 | 
			
		||||
 | 
			
		||||
## Fork maintenance
 | 
			
		||||
 | 
			
		||||
 | 
			
		||||
		Reference in New Issue
	
	Block a user