Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] [epp-dev] m2e ponders participation in luna 
Although I think everyone agrees that Sisu and Aether are mature
technologies from technical point of view, as things currently stand I
have no choice but to add "includes incubating components" disclaimer to
affected m2e bundles and features.

Based on [1] I do not expect m2e will be able to remove this label for
Luna, so all EPP packages that include m2e will need either add similar
label or remove m2e.

Of course, I would like m2e to stay in, but I understand why having
"incubating" label is not desirable and can't even give you any data to
help estimate how many users will be affected if m2e is removed.

@Wayne please update your records that m2e will participate in luna,
offset is +3, but does not really matter
[1] http://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg10136.html 

--
Regards,
Igor

On 12/16/2013, 13:47, Markus Knauer wrote:

I don't have *the* solution at hand, but Wayne's and others idea of
graduating these projects seems to be the best way to move forward -
given that a graduation is possible. Both projects are included in
another project (m2e) and this is one sign of maturity.
The IP deadline needs to be discussed with Janet and team, but from my
experience they will try to help as good as they can.

Thanks,
Markus


On Mon, Dec 16, 2013 at 7:20 PM, Igor Fedorenko <igor@xxxxxxxxxxxxxx
<mailto:igor@xxxxxxxxxxxxxx>> wrote:

    What is your suggestion?

    BTW, I didn't even realize m2e was part of RCP/RAP package :-)

    --
    Regards,
    Igor


    On 12/16/2013, 13:16, Markus Knauer wrote:

        I cannot speak for them but m2e is included in my RCP/RAP
        package, too.
        I don't like the idea of having to use an "Incubation" label on my
        package, and I am sure that the Java and Java EE package maintainers
        have a similar opinion.

        Thanks,
        Markus



        On Mon, Dec 16, 2013 at 7:13 PM, Igor Fedorenko
        <igor@xxxxxxxxxxxxxx <mailto:igor@xxxxxxxxxxxxxx>
        <mailto:igor@xxxxxxxxxxxxxx <mailto:igor@xxxxxxxxxxxxxx>>> wrote:



             On 12/16/2013, 12:45, Wayne Beaton wrote:

                 The submission deadline is the deadline for all CQs.
        The May
                 deadline
                 was for IP log submission.

                 I agree that if Sisu and Aether have both been adopted
        by a release
                 version of Maven, that this is a pretty clear
        indication that
                 they are
                 mature technology.

                 Have the Sisu and Aether projects been contacted regarding
                 graduation?
                 I'd love to hear their opinion regarding their readiness.

                 If, theoretically, we could get Sisu and Aether to graduate
                 early in the
                 new year, is it possible to create a new release of
        Maven based
                 on the
                 1.0 code in time for the simultaneous release?

                 FWIW, if m2e depends on the specific version of Maven that
                 includes Sisu
                 and Aether, including that version of Maven in the
        project downloads
                 means that the downloads must be marked as "incubating". By
                 extension,
                 any Eclipse package that includes m2e would have to be
                 similarly-marked.
                 Note that this does not mean that m2e itself needs to
        be moved
                 back into
                 an Incubation phase.


             What do "java" and "java ee" epp package maintainers think
        about
             "incubating" label?

             --
             Regards,
             Igor

             ___________________________________________________
             cross-project-issues-dev mailing list
             cross-project-issues-dev@__ecl__ipse.org <http://eclipse.org>
             <mailto:cross-project-issues-__dev@xxxxxxxxxxx
        <mailto:cross-project-issues-dev@xxxxxxxxxxx>>
        https://dev.eclipse.org/____mailman/listinfo/cross-____project-issues-dev
        <https://dev.eclipse.org/__mailman/listinfo/cross-__project-issues-dev>
        <https://dev.eclipse.org/__mailman/listinfo/cross-__project-issues-dev
        <https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev>>





        _________________________________________________
        epp-dev mailing list
        epp-dev@xxxxxxxxxxx <mailto:epp-dev@xxxxxxxxxxx>
        https://dev.eclipse.org/__mailman/listinfo/epp-dev
        <https://dev.eclipse.org/mailman/listinfo/epp-dev>

    _________________________________________________
    epp-dev mailing list
    epp-dev@xxxxxxxxxxx <mailto:epp-dev@xxxxxxxxxxx>
    https://dev.eclipse.org/__mailman/listinfo/epp-dev
    <https://dev.eclipse.org/mailman/listinfo/epp-dev>





_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Back to the top