Re: [lsp4e-dev] Project versions mismatch between code, releases, git, b

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

Re: [lsp4e-dev] Project versions mismatch between code, releases, git, bugzilla and project page

From: Mickael Istria <mistria@xxxxxxxxxx>
Date: Mon, 21 Jun 2021 21:51:01 +0200
Delivered-to: lsp4e-dev@xxxxxxxxxxx
List-archive: <https://www.eclipse.org/mailman/private/lsp4e-dev/>
List-help: <mailto:lsp4e-dev-request@eclipse.org?subject=help>
List-subscribe: <https://www.eclipse.org/mailman/listinfo/lsp4e-dev>, <mailto:lsp4e-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://www.eclipse.org/mailman/options/lsp4e-dev>, <mailto:lsp4e-dev-request@eclipse.org?subject=unsubscribe>

+1.

Basically project versions means nothing technically, they're more "marketing" to let consumers get an idea of the importance of the change. For bundles, we stick to semantic versioning so it depends only on API changes and so on; because this does scale well.

Follow-Ups:
- Re: [lsp4e-dev] Project versions mismatch between code, releases, git, bugzilla and project page
  - From: Martin D'Aloia

References:
- [lsp4e-dev] Project versions mismatch between code, releases, git, bugzilla and project page
  - From: Martin D'Aloia
- Re: [lsp4e-dev] Project versions mismatch between code, releases, git, bugzilla and project page
  - From: Jonah Graham

Prev by Date: Re: [lsp4e-dev] Project versions mismatch between code, releases, git, bugzilla and project page
Next by Date: Re: [lsp4e-dev] Project versions mismatch between code, releases, git, bugzilla and project page
Previous by thread: Re: [lsp4e-dev] Project versions mismatch between code, releases, git, bugzilla and project page
Next by thread: Re: [lsp4e-dev] Project versions mismatch between code, releases, git, bugzilla and project page
Index(es):
- Date
- Thread

Breadcrumbs