Re: [mdt-papyrus.dev] Papyrus and Helios Release Train

[Kenn Hussey <kenn.hussey@xxxxxxxxx>]

Thibault,

I support this initiative and am here to help in any way I can... Note that I'll be asking all MDT components to start making similar plans in the coming weeks.

It would be ideal if the team could adopt an agile approach to the release, e.g. based on Scrum. That way we could do some forecasting and track progress by holding a demo every two weeks to ensure that everybody is on the same page. I've led several development teams using this approach and found it to be quite useful... Just a thought.

Cheers,

Kenn

2009/8/14 Thibault LANDRE <thibault.landre@xxxxxxxxxxxxxx>

Hi all,

The first official version of MDT Papyrus will be available with Helios.

It would be great if we could join the Helios Simultaneous release.
To achieve it, some tasks must be done before specific Helios milestone.

The official date for Helios Milestone :
M1 : August 21th (M1+0: August 7th)
M2 : October 2nd (M2+0: September 18th)
M3 : November 13th (M3+0: October 30th)
M4 : December 18th (M4+0: December 11th)
M5 : February 5th 2010 (M5+0: January 29th)
M6 : March 19th 2010 (M6+0: March 12th)
M7 : May 7th 2010 (M7+0: April 30th)


Our first deadline is M4+0, December 11th. Before this milestone, we have to make :

1- https://bugs.eclipse.org/bugs/show_bug.cgi?id=251715
"Projects must have stated and demonstrated their intent to join Helios by the M4+0 date. Projects do so by adding themselves to bug 251715 and asking to have their project-specific bugs created as clones of each of those referenced in this table. "
--> Action SG and RF ?

2 - https://bugs.eclipse.org/bugs/show_bug.cgi?id=252790
"Projects must have an project plan in XML format."
--> Action TL

3 - https://bugs.eclipse.org/bugs/show_bug.cgi?id=252789
" At least one person from each project must subscribe to cross-project bug inbox, i.e. edit Bugzilla prefs to watch "cross-project.inbox@xxxxxxxxxxx". Build team members (or their designated alternates) from each project will provide communication channels: phone, mail, IM, IRC and will be available during the milestone integration periods. "
--> Action RS and EP ?

4  - https://bugs.eclipse.org/bugs/show_bug.cgi?id=252791
"Project representatives must attend the planning meetings and conference calls - you have to be involved to be involved. "
--> Action SG and RF ?

5 - https://bugs.eclipse.org/bugs/show_bug.cgi?id=252795
" Projects must use Eclipse message bundles unless there are technical reasons not to. (see Message Bundle Conversion Tool and [1]) "
--> Action TL, CD and YT ?

6 - https://bugs.eclipse.org/bugs/show_bug.cgi?id=252799
"Projects must use signed plugins using the Eclipse certificate. Exceptions must be authorized by the planning council for technical reasons. "
--> Action RS and EP ?

7 - https://bugs.eclipse.org/bugs/show_bug.cgi?id=252800
" Projects must use jar'ed plug-ins (with unpack=false) unless authorized by the planning council for technical reasons. Nested jars should be avoided if possible since it creates problems for projects that has dependencies to such plug-ins. The OSGi runtime is fine with it but the compiler is not able to handle classpaths that contain nested jars. In case only one nested jar exists, it is often better to expand the contents of that jar into the root folder (i.e. unnest the jar). If a plug-in contains large files that are frequently used (opened and closed), a jar'ed plug-in might degrade performance significantly since the file must be decompressed each time it is opened. "
--> Action TL and PT ?

8 - https://bugs.eclipse.org/bugs/show_bug.cgi?id=252801
"        Projects must have build process maturity: scripted, repeatable, and executable by others. "
--> Action RS and EP ?

9 - https://bugs.eclipse.org/bugs/show_bug.cgi?id=252803
"Any new third-party plug-ins that are common between projects must be consumed via Orbit; the final Helios release will not have duplicate third-party libraries (note that this only applies to identical versions of the libraries; thus if project A requires foo.jar 1.6 and project B uses foo.jar 1.7, that's ok). "
--> Action to check if we need to do this one : YT ?

10 - https://bugs.eclipse.org/bugs/show_bug.cgi?id=252804
"        Projects must optimize their own update site using pack200 to reduce bandwidth utilization and provide a better update experience for users. With the introduction of p2, project update sites must generate metadata (artifact and content repository info). "
--> Action RS and EP ?

11 - https://bugs.eclipse.org/bugs/show_bug.cgi?id=252811
"Should design and test for accessibility. "
--> Action YT ?



As there is a lot of tasks to be completed before M4+0, I suggest we try to complete most of them before M3 release in order to state if we are able to make it or not.

The prior task is to enable the build of Papyrus with Eclipse's mechanism. We should also start to follow the Eclipse release train (a release every 6 weeks).


Everything is described here and I suggest you to read it :
http://wiki.eclipse.org/Helios#Project_Plan



What do you think ?


Regards,

Thibault

_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev