Re: [lsp4e-dev] Can we release soon?

[Jonah Graham <jonah@xxxxxxxxxxxxxxxx>]

OK. Lets release "tomorrow" then :-) You can promote the https://download.eclipse.org/lsp4e/0.14.0-snapshots/S202003032032/ to be https://download.eclipse.org/lsp4e/releases/0.14.0/ when you are ready as AFAICT LSP4E is working with LSP4J properly. 

(PS I am grateful to Martin L for doing an integration test as part of the review of https://git.eclipse.org/r/#/c/158568/ - that helps the confidence level of LSP4E release!)

I do recommend that any dependencies on LSP4E are version locked to org.eclipse.lsp4e;bundle-version="[0.13.1,0.14.0)" or org.eclipse.lsp4e.debug;bundle-version="[0.12.0,0.13.0)"

I will raise the issue of graduating and semver of LSP4J on their communications channels. Keep your eye on lsp4j-dev for an email.

Note that there is no requirement for incubating projects to use < 1.0 release numbers. It is totally ok for incubating projects to start using semver as soon as possible.

Jonah

 

~~~
Jonah Graham
Kichwa Coders
www.kichwacoders.com

On Wed, 4 Mar 2020 at 11:44, Mickael Istria <mistria@xxxxxxxxxx> wrote:

On Wed, Mar 4, 2020 at 5:37 PM Jonah Graham <jonah@xxxxxxxxxxxxxxxx> wrote:

I wrote a long email and as I finished writing it I think that there is an underlying difference in approaches between how you and I see the purpose of the LSP4E release. Please correct me if I am wrong. I see the LSP4E release as the end of the integration process and you see the LSP4E release as the start of that integration process. If that is the case I am fine to change to your way of seeing things and have LSP4E be the start of the process.

Yes, it looks like you found the root of our divergences here. Thanks for that, as I wouldn't have been able to find or explain that better.

_______________________________________________
lsp4e-dev mailing list
lsp4e-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/lsp4e-dev