wbeaton@build:~> find downloads/releases/neon/ -name *eclipse.nebula* | grep -v nattable
downloads/releases/neon/201512181000/plugins/org.eclipse.nebula.widgets.tablecombo_1.0.0.201511041902.jar
downloads/releases/neon/201605061000/plugins/org.eclipse.nebula.widgets.tablecombo_1.0.0.201604151927.jar
downloads/releases/neon/201605061000/plugins/org.eclipse.nebula.widgets.richtext_1.0.0.201604151927.jar
downloads/releases/neon/201603301000/plugins/org.eclipse.nebula.widgets.tablecombo_1.0.0.201602191853.jar
downloads/releases/neon/201602051000/plugins/org.eclipse.nebula.widgets.tablecombo_1.0.0.201602011643.jar

HTH,

Wayne

On 12/05/16 04:44 PM, Wim Jongman wrote:
We should be able to investigate what is being consumed by the release train. If this also includes one or more of the "unsupported widgets" then we need to decide if we add those as well or let these consumers know that they are in violation.

David could you produce a list with references to org.eclipse.nebula projects?



On Thu, May 12, 2016 at 10:16 PM, Dirk Fauth <[email protected] <mailto:[email protected]>> wrote:

    As far as I understood Wim, the idea is to first clean up the list
    of committers, specify the widgets/projects that should be in the
    release and possibly update the widget versions to 1.0.0 to match
    the version rules regarding maturity.

    From my point of view the set of widgets for the release is set.
    At least that would be what the community expects. What is
    currently communicated as released should be released. I think
    that would be the easiest way to proceed. Not sure if Wim planned
    to also move some of the incubation widgets to the release aswell.

    Regarding the IP log, do we need to wait for the cleanup or should
    we send it in immediately via
    https://projects.eclipse.org/projects/technology.nebula/iplog/preview ?



    On Thu, May 12, 2016 at 9:49 PM, Wayne Beaton <[email protected]
    <mailto:[email protected]>> wrote:

        A bunch of projects are already using Nebula widgets. This is
        a bit problematic from an EDP POV because Nebula has never
        done (AFAICT) a formal release and is still incubating.

        It's long past time to do a proper release and graduate the
        project.

        Can we do this soon?

        AFAICT, the project downloads are IP clean, so getting the IP
        Log approved should only take a couple of seconds of effort.

        The project is hosting downloads [1] (though, I'd prefer that
        you not use the term "Projects" like you are; that term is
        already confusing enough).

        There is still lots of activity on the project, but it does
        seem that many/most of the widgets are stable.

        What's stopping us from doing this?

        Wayne

        [1] https://www.eclipse.org/nebula/downloads.php

-- Wayne Beaton
        @waynebeaton
        The Eclipse Foundation
        EclipseCon France 2016 <http://www.eclipsecon.org/france2016>

        _______________________________________________
        nebula-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/nebula-dev



    _______________________________________________
    nebula-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/nebula-dev



--
Wayne Beaton
@waynebeaton
The Eclipse Foundation
EclipseCon France 2016 <http://www.eclipsecon.org/france2016>
_______________________________________________
nebula-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/nebula-dev

Reply via email to