CodeTanzania / CodeTanzania/open311-android-library

should use semantic versioning on releases

Open
#26 0 comments 0 reactions 4 assignees Claimed by @DYJParker View on GitHub
enhancement
Dominant language
Java
Stars
1
Forks
0
PR merge metrics
No merged PRs in 30d

Description

I hope [Semantic Versioning](https://semver.org/) is the de facto on versionin. Steps

1. On preparing releases if we don't break API's we increase `MINOR` version both in `build.gradle` and tag a repo using `vMAJOR.MINOR.PATCH` for `jitpack` to propagate new release
2. For android it may be trick cause `versionName is string` and `versionCode is long`. A simple library(or app) may use convection `MAJOR*1000+MINOR*100+PATCH*10` i.e `v0.5.1` versionCode become `510` and `v1.5.1` become `1510`
3. For bigger apps they can even mix `min SDK version` on deriving `versionCode`

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.