[cross-project-issues-dev] EcoreTools participation in 2018-09
Hi all, EcoreTools will participate in the 2018-09 SimRel, with offset +3. The version contributed will be the 3.3.0 (same as Photon). https://projects.eclipse.org/projects/modeling.ecoretools/releases/3.3.0 Regards, Cédric ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
[cross-project-issues-dev] Amalgamation Participating in Photon
The Modeling Amalgamation project will be participating in the Photon release with an offset of +3 The record is here : https://projects.eclipse.org/projects/modeling.amalgam/releases/2.0.0 Cheers, Cédric ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
[cross-project-issues-dev] EcoreTools participating in Photon release
Hi, EcoreTools will be participating in the Photon simultaneous release, with offset +3. The code inherited from the "legacy" property views" will no longer be shipped (hence the 4.0) as notified in the 3.3.0 "end of life" section of the previous release [1] The release record is here: https://projects.eclipse.org/projects/modeling.ecoretools/releases/4.0.0/plan [1] https://projects.eclipse.org/projects/modeling.ecoretools/releases/3.3.0/review Regards, Cédric ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
[cross-project-issues-dev] Amalgamation Participating in Oxygen
The Modeling Amalgamation project will be participating in the Oxygen release with an offset of +3 The record is here : https://projects.eclipse.org/projects/modeling.amalgam/releases/1.8.0 Cheers, Cédric ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
[cross-project-issues-dev] EcoreTools participating in Neon release
Hi, EcoreTools will be participating in the Neon simultaneous release, with offset +3. The release record is here: https://projects.eclipse.org/projects/modeling.ecoretools/releases/3.1.0/plan Regards, Cédric ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
[cross-project-issues-dev] Amalgam participating in Neon release
Hi, Amalgam will be participating in the Neon simultaneous release, with offset +3. The release record is here: https://projects.eclipse.org/projects/modeling.amalgam/releases/1.7.0/plan Regards, Cédric ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Discussing the idea of setting up a "Mattermost" server for projects
I am interested :) We've been using and experimenting with it for quite a few weeks at Obeo and the feedback is very positive so far. We have been able to integrate gerrit, bugzilla, the eclipse forums, jira and jenkins/hudson with it using a couple of python scripts. Jens would you track a bugzilla to move the discussion there ? Cheers, Cédric Le 08/12/2015 17:46, Jens Reimann a écrit : Hi, I just wanted to check if there would be interest in running a "Mattermost" [1] server at Eclipse. If you don't know "Mattermost" is it "Slack", "HipChat" alternative, but open source. If you don't know Slack or HipChat, you could see it as a web based IRC alternative, which allows integrating other web based solutions using an web API. On other words, you can type text and other can read it. A chat. I do know there are Forums and IRC server and NNTP groups and mailing lists. And I don't want to start a discussion about pro's and con's about these different solutions. But I would like to check if there is interest in something like "Mattermost", so I would like to volunteer and try to see if something like this could be established. Jens [1] http://www.mattermost.com/ ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
[cross-project-issues-dev] Signing service seems down
At least for the Sirius HIPP. I tracked it in https://bugs.eclipse.org/bugs/show_bug.cgi?id=461937 Feel free to chime in to confirm (or not) that your HIPP is having issue too. Cédric ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
[cross-project-issues-dev] Amalgamation Participating in Mars
The Modeling Amalgamation project will be participating in the Mars release with an offset of +3 The record is here : https://projects.eclipse.org/projects/modeling.amalgam/releases/1.6.0 Cheers, Cédric ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
[cross-project-issues-dev] Mylyn Intent project will not participate in the Mars release train
The Mylyn Intent project will not participate in the Mars release train. We are at a point where we want to take the pencils back and rework the services Intent can provide in a way which is less intrusive to the development process. This will require more experiments, API breakages, and as a consequence we can't commit to the schedule or even to the resources needed to maintain the alignment with the other projects. AFAIK the project is not consummed by any other component in the release train, If you do, please contact us and we'll figure out something. Cédric ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Papyrus: CSS Support for GMF
Hi and thanks for the heads-up. You're right this would impact every GMF modeler out there (EcoreTools being one of them) and lead to issues quite difficult to identify and fix. Which lead me to this question : why don't you, in the papyrus code, directly refers to the Factory you want to use (here the one having the CSS support) - or even define your own extension point to retrieve the right one in the context of papyrus ? What is the rationale to override the GMF one for all the Eclipse Installation ? Even if this does not introduce any specific bug or issue, just that fact that it might lookup the ResourceSet for the CSS support could lead to performance penalty for all the modelers - not something we could afford for no gain on the other hand. Furthermore your code might assume things which are just not true for other modelers, like the fact that the model is in a ResourceSet or even in a Resource. Cédric Le 17/12/2013 18:13, LETAVERNIER Camille a écrit : Hi all, In Papyrus, we've implemented a component to support CSS Stylesheets for GMF-based diagrams. This component has been introduced in Papyrus/Juno, and we now consider it stable. It has never been included in the Simultaneous Release because of one specific issue: this component overrides the GMF Notation metamodel implementation (Though the org.eclipse.emf.ecore.factory_override extension point). Because the EMF Factory is a singleton, there is a risk of introducing conflicts, if more than one component uses this extension point for the same metamodel. The CSSNotation elements have been designed to delegate to the standard Notation implementation when the CSS support is not installed on the resource set, which means that this component, in theory, doesn't introduce any change in the behavior of non-Papyrus diagrams. Now, we'd like to distribute this component as part of the Papyrus project for Luna, directly in the Release Train, whereas it was only proposed as an optional, extra component in Juno and Kepler. My idea is that we might introduce this feature in M4, and remove it before M6 if major issues (incompatibilities) are introduced. Is there any objection, or suggestion? (Especially for GMF-based projects) Regards, Camille __ Camille Letavernier CEA LIST Papyrus : http://www.eclipse.org/papyrus ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
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 e...@eclipse.org). 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 Learn about Eclipse Projects ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Please announce your participation in Luna
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:*cross-project-issues-dev-boun...@eclipse.org [mailto:cross-project-issues-dev-boun...@eclipse.org] *On Behalf Of *Cédric Brun *Sent:* September-10-13 10:29 AM *To:* cross-project-issues-dev@eclipse.org *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 e...@eclipse.org mailto:e...@eclipse.org). 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 cross-project-issues-dev@eclipse.org mailto:cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Re: [cross-project-issues-dev] Kepler offsets
Hi Wayne, Actually no, Amalgamation should be +3, EMF Compare should be +2 I can't remember where I should update this information, I can't find it in the portal metadata. Any hint ? Cédric Le 16/08/2012 23:30, Wayne Beaton a écrit : Are Amalgamation and EMF Compare really +0 projects? http://eclipse.org/projects/releases/releases.php Wayne -- Wayne Beaton The Eclipse Foundation Twitter: @waynebeaton Explore Eclipse Projects http://www.eclipse.org/projects ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev ___ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
