Prepare release: Bump ralphc to 3.12.2

[simerplaha]

Prepare stable release.

Release 0.2.15 from master so that a stable version is available with the latest ralphc.

Question for next PR: Should RC releases with soft-parser enabled remain on 0.2.14-rc[x]?

[tdroxler]

Release 0.2.15 from master so that a stable version is available with the latest ralphc.

Question for next PR: Should RC releases with soft-parser enabled remain on 0.2.14-rc[x]?

This release should be 0.2.14 no? as we are currently on 0.2.13

We can then continue with the soft parser on 0.2.15-rcx

Or if we want to make a clear separation. We could say that the soft parser will be 0.3.0

so we have 0.3.0-rcx until it's fully ready

and we can continue to increment 0.2.x as much as we want without the soft parser enabled, that would maybe be less confusing and it also show the importance of this soft parser switch

[simerplaha]

This release should be 0.2.14 no? as we are currently on 0.2.13
We can then continue with the soft parser on 0.2.15-rcx

I don't think this is standard practice. Releasing 0.2.14 after 0.2.14-rc0 normally means that the changes in 0.2.14-rc0 have been finalised and now stable.

Or if we want to make a clear separation. We could say that the soft parser will be 0.3.0

This wouldn't follow standard versioning convention. Bumping the major 0.3.0 implies breaking changes. For example, the release 0.2.0 had a breaking change because of the move of ralph.json to the directory .ralph-lsp.

[tdroxler]

I'm fine with any solution, your call.