Using pre-1.0 release numbers for incubating projects is a convention,
not a rule.
The rule regarding release numbers boils down to: don't confuse your
community.
Wayne
On 08/12/16 04:02 AM, Dennis Hübner wrote:
Mickael,
AFAIK, incubating project may not start with major 1.
We (LSP4J) plan to start with 0.1.0 and hopefully provide 0.3.0 for
the Oxygen release.
Kind regards,
Dennis.
Am 06.12.2016 um 19:14 schrieb Mickael Istria <[email protected]
<mailto:[email protected]>>:
The LSP4E project would like to participate to the Oxygen
simultaneous release.
The goal of the project is to make the Eclipse IDE possible to
consume Language Servers conforming to the Language Server Protocol.
Although it's more to be perceived as a framework to very easily
create support for new languages in the Eclipse IDE, with most of the
language logic separated and reused/reusable as a language server, it
also provides a way for end-users to dynamically define a language
server and take advantage of it in the IDE without installing new
plugins.
(we'll probably reuse this blurb in the description)
As the project is new and currently incubating, it's not yet know
which version will be suitable for Oxygen. Depending on the adoption
by some other projects, it may be 0.2.0, 0.N.0 or even 1.0.0, 1.0.1
or 1.1.0... This also depends on the releases of the LSP4J project
(LSP4E will most likely create a new milestone release whenever LSP4J
releases).
How should we handle this? Should we start by defining a 0.1.0 and a
0.2.0 milestone releases and announce 0.2.0 as candidate for Oxygen,
with the high priority of a version change?
Thanks in advance
--
Mickael Istria
Eclipse developer for Red Hat Developers <http://developers.redhat.com/>
My blog <http://mickaelistria.wordpress.com/> - My Tweets
<http://twitter.com/mickaelistria>
_______________________________________________
cross-project-issues-dev mailing list
[email protected]
<mailto:[email protected]>
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Viele Grüße,
Dennis Hübner
_______________________________________________
cross-project-issues-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
--
Wayne Beaton
@waynebeaton
The Eclipse Foundation
Eclipse Converge <https://www.eclipseconverge.org/na2017/>
_______________________________________________
cross-project-issues-dev mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
