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
FWIW (sharing with the group because I think that this is of general
interest)...
If you see a URL from the PMI that has something like "-0" tacked on the
end, that generally means that the URL has been taken already. For
release records, the URL is generated to include the version of the
rel
Bugzilla page rendering is broken and bug comments are lost.
I filed https://bugs.eclipse.org/bugs/show_bug.cgi?id=50
Markus
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve yo
On 12/08/2016 10:02 AM, Dennis Hübner wrote:
Mickael,
AFAIK, incubating project may not start with major 1.
Right. I'm just not certain LSP4E will still be incubating by June as
some adopters are already asking for APIs, so there are chances that the
June release would be a regular one.
--
Mi
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 :
>
> The LSP4E project would like to participate to the Oxygen simultane
Hello,
EMF Facet will participate in the Oxygen Simultaneous Release, with an offset
of +2.
https://projects.eclipse.org/projects/modeling.emft.emf-facet/releases/1.2.0-0/
Regards,
Grégoire
___
cross-project-issues-dev mailing list
cross-project-issue
