Yep,

Pierre-Charles will send a mail as soon as the project plan is filled.


Le 10/09/2013 16:33, Pascal Rapicault a écrit :

Will Sirius be art of Luna?

*From:*[email protected] [mailto:[email protected]] *On Behalf Of *Cédric Brun
*Sent:* September-10-13 10:29 AM
*To:* [email protected]
*Subject:* Re: [cross-project-issues-dev] Please announce your participation in Luna

Hi,

EcoreTools will participate in Luna with a 2.0 release, offset is +3

The 2.0 release is a complete rewrite leveraging the Eclipse Sirius project.
End Users might expect :
- redesigned user experience
- complementary editors besides the main diagram editor
- improved stability and consistency
- power user specific features

https://projects.eclipse.org/projects/modeling.emft.ecoretools/releases/2.0.0

Le 09/09/2013 17:09, Wayne Beaton a écrit :

    Greetings folks.

    I've changed the way things work with regard to keeping track of
    who is participating in the simultaneous release. Previously, you
    just had to flip a bit in the project metadata; now, you have to
    announce your participation on the cross-project-issues-dev
    mailing list.

    This has several advantages:

    First, a project needs to have at least on representative as a
    member of the list to announce. This seems pretty obvious, but
    there have been multiple examples in the past of projects that
    were unaware of important messages and discussion because they
    didn't have this representation.

    Second, announcing on the list provides better transparency and
    openness. The community will have a much better chance of
    understanding what each participating project is doing and have a
    much more obvious opportunity to ask questions and otherwise
    participate.

    Third, it'll be harder for projects to "sneak in" after the fact.
    Believe it or not, there are multiple examples of projects who
    have "flipped the bit" on participation with older (past) releases.

    So... If you intend to participate in Luna, please do the following:

    * If you have not already done so, create a release record [1] for
    the release that you're contributing to Luna. Note that the Luna
    release date is June 25/2013.
    * Enter at least plan information for the release, minimally
    including a description and milestones. The release's description
    should minimally describe the main focus of the release. Please
    also consider adding a theme or two. This sort of information is
    really easy to add and update using the PMI. Note that you do not
    necessarily need to use the PMI for your plan, but please at least
    include a description of the release in the PMI record.
    * If you have not already done so, sign up for the
    cross-project-issues-dev mailing list
    * Send a note to cross-project-issues-dev with the name of your
    project, number of the release to include with Luna, and the
    offset (+0, +1, +2, ...).

    If you have any questions, please coordinate with your Planning
    Council representative [2], PMC, or me (via [email protected]
    <mailto:[email protected]>).

    Thanks!

    Wayne

    [1]
    
http://wiki.eclipse.org/Project_Management_Infrastructure/Project_Metadata#Releases
    [2]
    https://projects.eclipse.org/content/planning-council-representative

-- Wayne Beaton
    Director of Open Source Projects, The Eclipse Foundation
    <http://www.eclipse.org>
    Learn about Eclipse Projects <http://www.eclipse.org/projects>
    EclipseCon Europe 2013 <http://www.eclipsecon.org/europe2013>




    _______________________________________________

    cross-project-issues-dev mailing list

    [email protected]  
<mailto:[email protected]>

    https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev



_______________________________________________
cross-project-issues-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

_______________________________________________
cross-project-issues-dev mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Reply via email to