Merge branch 're-enable-lexica-after-buid-fix' into 'master'
Re-enable v0.9.2 of Lexica after fixing build and retagging. Apologies for pointing the v0.9.2 metadata to a broken build. Don't think I used `-f` during my test `fdroid build`. I'm not sure how semantic versioning usually deals with fixing broken builds, but I left it at v0.9.2, fixed the linter problem during the build, and moved the v0.9.2 tag to the new (hopefully working) commit. Do you guys have a suggestion about what the usual way for dealing with this is? Do others tend to bump the version number again to, e.g. `v0.9.3`, or perhaps do a `v0.9.2-1`? See merge request !1151
This commit is contained in:
commit
6ca3189006
|
@ -27,7 +27,6 @@ Build:0.9.1,901
|
||||||
gradle=yes
|
gradle=yes
|
||||||
|
|
||||||
Build:0.9.2,902
|
Build:0.9.2,902
|
||||||
disable=lint runs and errors
|
|
||||||
commit=v0.9.2
|
commit=v0.9.2
|
||||||
subdir=app
|
subdir=app
|
||||||
gradle=yes
|
gradle=yes
|
||||||
|
|
Loading…
Reference in a new issue