Re: [mdt.dev] Fwd: [cross-project-issues-dev] Galileo review preparation

[James Bruck <jbruck@xxxxxxxxxx>]

Thanks for the catch Michael.  
Can you tell that I've based my slides
on the previous year's slides ;)

Cheers,
- James.

Kenn Hussey <kenn.hussey@xxxxxxxxx>
Sent by: mdt.dev-bounces@xxxxxxxxxxx

28/05/2009 08:57 AM

Please respond to
MDT developers <mdt.dev@xxxxxxxxxxx>

To	MDT developers <mdt.dev@xxxxxxxxxxx>
cc
Subject	Re: [mdt.dev] Fwd: [cross-project-issues-dev] Galileo review         preparation

Good catch, Michael. Yes, it should say "Eclipse
Modeling Project". Other than that, +1 from me.
 
Now that UML2 has submitted there draft docuware, we're
just waiting for OCL, UML2 Tools, and XSD... Don't forget that these are
due to be submitted to the Foundation by tomorrow. Note also that they
need to be "approved" by the PMC before you submit them, but
that's more of a formality (since I am your representative on the PMC).
 
Cheers,
 
Kenn

On Wed, May 27, 2009 at 9:05 PM, Michael Golubev <Michael.Golubev@xxxxxxxxxxx>
wrote:
Hello,
Just in case, at Slide 15 an item #6 states:

>the "provider" field of each plug-in is set to "Eclipse.org“.

Should not it be "Eclipse Modeling project" instead?

Regards,
Michael


________________________________________
From: mdt.dev-bounces@xxxxxxxxxxx
[mdt.dev-bounces@xxxxxxxxxxx]
On Behalf Of James Bruck [jbruck@xxxxxxxxxx]
Sent: Wednesday, May 27, 2009 11:50 PM
To: MDT developers
Cc: Paul Elder; kenn.hussey@xxxxxxxxxxxxxxx
Subject: Re: [mdt.dev] Fwd: [cross-project-issues-dev] Galileo review  
preparation

Hi All,

I was going to submit the following.   Please let me know if you see
any issues.


Cheers,
- James.



Kenn Hussey <kenn.hussey@xxxxxxxxx>
Sent by: mdt.dev-bounces@xxxxxxxxxxx

26/05/2009 08:10 PM
Please respond to
MDT developers <mdt.dev@xxxxxxxxxxx>




To
       MDT developers <mdt.dev@xxxxxxxxxxx>
cc

Subject
       [mdt.dev] Fwd: [cross-project-issues-dev] Galileo
review preparation







Team,

Please don't forget to prepare and submit your docuware by this Friday
- see below for a reminder from the Foundation. As I've mentioned in emails
recently, it would be ideal if you could distribute them among the team
before review before submitting them.

Also, note that the deadline for submitting your IP log is coming soon
(next week). Anne also mentions this in her email below...

Cheers,

Kenn

---------- Forwarded message ----------
From: Anne Jacko <emo@xxxxxxxxxxx<mailto:emo@xxxxxxxxxxx>>
Date: Tue, May 26, 2009 at 4:41 PM
Subject: [cross-project-issues-dev] Galileo review preparation
To: "eclipse.org-planning-council" <eclipse.org-planning-council@xxxxxxxxxxx<mailto:eclipse.org-planning-council@xxxxxxxxxxx>>,
cross-project-issues-dev@xxxxxxxxxxx<mailto:cross-project-issues-dev@xxxxxxxxxxx>


Hello Galileo participants,

Thanks for your continuing work and attention in getting ready for this
release! We are approaching our June 10 review date, and this note is to
remind you of some deadlines that are fast approaching.

As always, you don't need to wait until the final deadline to submit! Earlier
is better, and this especially applies to projects using the IP Log Tool
(see below for more on this).

Review Slides

 *   Deadline for submitting to EMO is Friday,
May 29 (submit via email to emo@xxxxxxxxxxx<mailto:emo@xxxxxxxxxxx>)
 *   Please submit two pdfs for your review
docuware
   *   the "full deck" of slides
for your project, making sure to include the information listed here: [1]
<http://wiki.eclipse.org/Development_Resources/HOWTO/Review_Information_for_Project_Leads#Docuware_Contents>
   *   a "mini deck" -- two to four slides summarizing
your Galileo release; here's an example of one from Ganymede:  [2]<http://www.eclipse.org/project-slides/MDT_UML2Tools_minideck.pdf>

IP Log
   *   Deadline for submitting to the IP Team (emo-ip-team@xxxxxxxxxxx<mailto:emo-ip-team@xxxxxxxxxxx>)
is Wednesday, June 3
   *   Projects are encouraged to use the IP Log Tool [3]<http://wiki.eclipse.org/Development_Resources/Automatic_IP_Log>.
If you are not familiar with the tool, we suggest that you try it out,
look at the output, and use the documentation to correct any issues before
submitting the final log. If you ask EMO for help with the tool before
Friday, May 29, we will do our best to assist you.

Thanks again, and please let us know is you have questions or need help
(via email to emo@xxxxxxxxxxx<mailto:emo@xxxxxxxxxxx>).

Anne Jacko
emo@xxxxxxxxxxx<mailto:emo@xxxxxxxxxxx>

[1] http://wiki.eclipse.org/Development_Resources/HOWTO/Review_Information_for_Project_Leads#Docuware_Contents
[2] http://www.eclipse.org/project-slides/MDT_UML2Tools_minideck.pdf
[3] http://wiki.eclipse.org/Development_Resources/Automatic_IP_Log


Below is Wayne's original post about the Galileo review, for your reference:

*************************************************************************************

Hey folks. Here are the dates for Galileo:

*May 29*: Deadline for IP team to review all Galileo CQs

 * The IP Team has committed to completing the reviews of all CQs
for
  Galileo by May 29th.
 * Please respond as quickly as possible to questions from the IP
  Team concerning your CQs to ensure timely processing.

*May 29*: Deadline for submitting review docuware

 * We understand that the results from the IP reviews may change the
  contents of your docuware. If you need an extension, please let
  emo@xxxxxxxxxxx<mailto:emo@xxxxxxxxxxx>
know.
 * If you can complete and submit your docuware ahead
of the
  deadline, please do so. This will give the EMO time to review it.
 * If you need help assembling your review docuware, please contact
  your PMC or emo@xxxxxxxxxxx<mailto:emo@xxxxxxxxxxx>.
 * Projects are encouraged to make sure that their
project metadata
  is up-to-date in the portal [1].

*June 3*: Deadline for submitting IP Log

 * In order to provide projects with time required to put the
  finishing touches on their IP logs, we've set the deadline for the
  IP Logs to be three business days after the CQ deadline, and one
  week before the release review date.
 * Again, we ask that those project that are able to submit their
IP
  Logs in advance of the deadline to please do so.
 * Please ensure that your project's IP Log is properly recorded in
  the portal [1].
 * Any projects that wish to use the Automated IP Log Tool [2] are
  encouraged to do so. If you want/need assistance with the tool,
  please contact emo@xxxxxxxxxxx<mailto:emo@xxxxxxxxxxx>.

*June 10*: Review date

 * Standard practice is to hold a review call only when requested.
  Regardless of this, we're going to hold the review call anyway.
  Please plan to attend. Anne will send out the details.
 * The review call will be for Q&A only. Everybody please review
the
  slides in advance of the call and come prepared with your questions.

*Docuware*

Every project/component needs to send in a separate slide deck (if you
have a separate ".build" file in the /org.eclipse.galileo.build/
project [3], then your project is considered to be a separate project/component).
We also ask that you provide an additional "mini-deck" of three
to four slides with an overview of your project. We will combine the mini-decks
into an overview section of the Ganymede Release slide deck. We will archive
the "normal" slide deck you send as your project-specific Ganymede
release docuware, as well as include it in the Ganymede Release slide deck
that is used for the review call.

The due date for the slide decks is Friday, May 29. You are welcome and
encouraged to send them in earlier! Please include both the source file
(such as PPT, or ODP) and a PDF version of the slides.

Thanks,

Wayne

[1] http://portal.eclipse.org<http://portal.eclipse.org/>
[2] http://wiki.eclipse.org/Development_Resources/Automatic_IP_Log
[3] http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.galileo.build/?root=Callisto


Anne Jacko
emo@xxxxxxxxxxx<mailto:emo@xxxxxxxxxxx>


_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx<mailto:cross-project-issues-dev@xxxxxxxxxxx>
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

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


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