Difference between revisions of "M2E-WTP DEV MEETINGS"

Revision as of 09:41, 20 July 2012

M2E-WTP Development Status Meeting

20/07/2012

General status

• https://bugs.eclipse.org/bugs/buglist.cgi?list_id=2372438;query_based_on=Open%20m2e-wtp%20bugs;query_format=advanced;target_milestone=Juno%20SR1%20RC1;product=M2E-WTP;known_name=Open%20m2e-wtp%20bugs

Integration/Milestone builds availability

• hosting?
• need for EMO blessing?
• jar signing?

API status

• move to internal packages?

22/06/2012

General status

m2e-wtp's incubation is moving forward!

• The web site has been set up at https://www.eclipse.org/m2e-wtp/
• m2e-wtp's initial contribution has been greenlit by the IP Team to be uploaded to Eclipse's Git repository, under the parallel IP process.
• m2e-wtp integration tests code is available at github
• The issue tracker has been set up in Eclipse Bugzilla. There will be no issue migration from Sonatype's JIRA. All previous issues will need to be reopened manually in BZ.
• A #m2e-wtp IRC chat room is opened at freenode
• A mailing list for discussions about m2e-wtp developement has been set up.
• TODO : Add some documentation for setting up the developement environment (i.e. how to build m2e-wtp)

Build infrastructure

• Due to the m2e-wtp test code not being part of m2e-wtp's initial contribution, m2e-wtp is not built using Eclipse.org's Build infrastructure (similar to m2e).
• Instead, Jenkins jobs have been set up under Red Hat's internal build farm.
• Currently, m2e-wtp compiles correctly against Helios, Indigo and Juno. Integration tests are run against Indigo.
• m2e-wtp is built continuously and CI builds are pushed to a public p2 repository hosted by jboss.org : http://download.jboss.org/jbosstools/updates/requirements/m2eclipse/m2e-wtp-indigo/
• TODO : Some tests fail randomly. We need to stabilize them and start from solid foundations before going forward
• TODO : Evaluate the possibility of advertising new dev build availablity on the m2e-wtp-dev mailing list

Backward compatibility

• IBM wishes to keep Helios backward compatibility. m2e-wtp currently compiles against Helios, but needs to be tested against it. However, its unlikely the existing tests will pass in Helios due to some slight changes in behaviour.
• IBM is willing to perform these backward compatibility tests on their infrastructure and eventually contribute patches back to m2e-wtp and m2e.
• not discussed : backward compatibility / coexistence with the current m2eclipse-wtp install base

Planning

• Our objective is to join the Juno SR1 release train on 28/09/2012.
• According to the Juno SR1 calendar, we should target RC1+3 and prepare readyness for wed. 22/08
• we'll work on a release plan (using m2e's release plan as an example),
• m2e-wtp 0.16.0 will focus on stabilization and its main new features will be around the Eclipse to Maven project conversion area (converts eclipse settings to their maven plugin counterpart)