docs: Make devtools a pure release procedure page
This commit is contained in:
parent
e981caf5e9
commit
b2b7b87081
@ -136,7 +136,7 @@ Development
|
|||||||
|
|
||||||
contributing
|
contributing
|
||||||
devenv
|
devenv
|
||||||
devtools
|
releasing
|
||||||
codestyle
|
codestyle
|
||||||
extensiondev
|
extensiondev
|
||||||
|
|
||||||
|
|||||||
@ -1,8 +1,10 @@
|
|||||||
*****************
|
******************
|
||||||
Development tools
|
Release procedures
|
||||||
*****************
|
******************
|
||||||
|
|
||||||
Here you'll find description of the development tools we use.
|
Here we try to keep an up to date record of how Mopidy releases are made. This
|
||||||
|
documentation serves both as a checklist, to reduce the project's dependency on
|
||||||
|
key individuals, and as a stepping stone to more automation.
|
||||||
|
|
||||||
|
|
||||||
Creating releases
|
Creating releases
|
||||||
Loading…
Reference in New Issue
Block a user