Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [] When should a project leave incubation? Is the 0.x version related?

My understanding is that for most of the projects we should graduate them as the "Mature" phase as they demonstrate the good qualities of a proper open source project. Do all the projects listed have an active and growing community? I know from personal experience that LSP4E does. The other aspect of incubating should be to let adopters know that APIs are not stable yet -- however I don't really know how stable it should be, and is having part (core part?) stable enough? The parallel IP seems just a small consideration to remove a pain point for people bringing new projects to Eclipse and not a core quality of an incubating project.

The Incubating branding can have negative connotations, so I understand the desire to get out of incubation at the earliest opportunity.

I hope that helps advance the discussion.

Jonah Graham
Kichwa Coders Ltd.

On Thu, 21 Jun 2018 at 11:25, Mickael Istria <mistria@xxxxxxxxxx> wrote:
Hi all,

I'd like the AC to discuss the following case:
For LSP4E, TM4E, Corrosion, aCute and others, we're still in a 0.x version because we want to highlight that the project is in relatively early-stage for integrators to adopt them with too much trust on stability of code and APIs.
However, none of those projects require the parallel-IP process and all are fine with the regular release and IP process for mature projects.

In this case, is it worth keeping the project as incubating?
Is a 0.x version reserved to the official "incubating" project state or can it be used for non-incubating projects?

Thanks in advance for the answer or discussion.
Mickael Istria
Eclipse IDE developer, for Red Hat Developers
_______________________________________________ mailing list

IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation.  To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.

Back to the top