Release process

[1buran]

What is the release process of project? I don't see a new release but it seems that project is not abandoned. GitHub shows that since the last release master branch of repo has a lot of new commits:

https://github.com/zyedidia/micro/releases/tag/v2.0.13
· 181 commits to master since this release

Should I use the latest changes from master branch and compile micro by own or wait for a new release?

[dmaluka]

Micro is recently being developed more actively than it used to be, since @JoeKar and me now have rights to push commits.

But when it comes to releases, still only @zyedidia can make them, so ultimately it is up to @zyedidia when to make the next release. We can only recommend to him when.

There indeed has been a lot of changes since v2.0.13. On the other hand, there are still some known important issues that we'd like to fix before the next release.

TL;DR we don't know (have not decided/agreed) when will the next release happen.

Should I use the latest changes from master branch and compile micro by own or wait for a new release?

If you want those newer changes, yes, you need to compile micro on your own.

There are also nightly builds: https://github.com/zyedidia/micro/releases/tag/nightly but apparently they are broken: for some reason it builds v2.0.13, instead of the newest master, every night. @zyedidia any chance to fix that?

[dmaluka]

Nightly build fixed: #3284.

[texastoland]

Excited for a stable release 🔥

[dev-nicolaos]

With v2.0.14 released and the explanation provided above, this discussion can probably be marked as answered or closed.

[dmaluka]

Closing then. BTW now @JoeKar and I do have permissions to make releases.

[zyedidia]

Thank you for all your hard work making this release possible @dmaluka and @JoeKar!