Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [stp-dev] Galileo RC heartbeat

Here you go:
http://dev.eclipse.org/svnroot/stp/org.eclipse.stp.bpmn-modeler/org.eclipse.stp.bpmn/tags/3.5GA/

On Mon, May 25, 2009 at 16:29, Oisin Hurley <oisin.hurley@xxxxxxxxx> wrote:
[..] 

Ok, some other Galileo items that are on the list. Here are
three items picked from the http://wiki.eclipse.org/Galileo
page:

1. "Each major project (as determined by participating PMCs) should
have an About dialog icon with descriptive text (e.g. provider name
= "Eclipse Modeling Project" and not simply Eclipse.org) and contribute
to the welcome page."

This is a 'should have' - but I'm interested to hear what you
guys think about having this icon in place, and contributing
to the welcome page.
Won't fix. 


2. "Projects must have an project plan in XML format."

Can you let me know, please, if you have this in place, and
send links.
I tried, I spent half a day to a day on it, I don't have cycles for it:


3. "Must have new & noteworthy for each milestone. Must be something
readable and usable not just a static list of all the bugs, e.g. platform.
Corollary: individual new & noteworthy should be linked in to the collective
New & Noteworthy."

Ok, so I'm going to unilaterally tone this one down and say,
please can we have a round-up of what's new and noteworthy
for your project for the release review and the GA.
Will do as part of the slide deck. 


4. "Projects should leverage only published APIs of dependencies. As a
Release Review requirement, all deviations must be documented.
Additionally, rectification for the issues should be listed as part of a
migration plan, with bugs listed where APIs need to be provided by
dependent projects"

So - it looks like we have to document our deviations :)  I see where
the PC is coming from with this one, and my approach here would be
to do something along the lines of finding all of the imports of
internal packages in your code and just writing them down. The
migration plan piece is a 'should do'. There may be some kind of
magical PDE tooling that can do this, but I'm not aware of it at
the moment.
Sorry, but we won't have cycles to address this. 


Finally, a reminder about Release Review. Here are the dates:

* Release review documentation due May 29
* IP Logs  due June 3
* Galileo review date is June 10.

Release review documentation is due END OF THIS WEEK!
5pm Irish time :) ? 


 --oh
_______________________________________________
stp-dev mailing list
stp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/stp-dev


Back to the top