Re: [eclipse.org-planning-council] Exception for Sequoyah for M4 Require

[David M Williams <david_williams@xxxxxxxxxx>]

You can't vote twice Tom! :)  


I double checked with Eric, and he said
he can't contact his engineering team right now (due to travel and timezones),
but thought they were mostly ready to go, but by no means smoothly assured
they could enter without issues. So I'd like to encourage them to try,
but agree at the first (or second) sign of trouble, allow them to back
out, and re-enter right after M5. I think that's low risk since no one
else in Helios depends on them (other than Pulsar EPP leaf). 

As for other exceptions we have approved
to enter late, after M4, I fully expect them to be in M5, and if they are
not, then they would have to re-apply for another exception. I don't mean
to "get in the way of progress" but seems a simple mechanism
to establish order and keep everyone informed. We have a meeting next week
and can discuss then if that hasn't been clear to us all. 

Thanks,

From:	Thomas Watson/Austin/IBM@IBMUS
To:	"eclipse.org-planning-council" <eclipse.org-planning-council@xxxxxxxxxxx>
Date:	01/28/2010 03:29 PM
Subject:	Re: [eclipse.org-planning-council] Exception for Sequoyah for M4        Requirement
Sent by:	eclipse.org-planning-council-bounces@xxxxxxxxxxx

---

+1 for participation.

But I wonder if they will be ready for M5. How will it impact our ability
to get M5 out the door on time? Is this something they can get integrated
in right after M5?

Tom

David
M Williams---01/28/2010 12:12:23 PM---

From:	David M Williams/Raleigh/IBM@IBMUS
To:	"eclipse.org-planning-council" <eclipse.org-planning-council@xxxxxxxxxxx>
Date:	01/28/2010 12:12 PM
Subject:	[eclipse.org-planning-council] Exception for Sequoyah for M4 Requirement

---

I am sending this note on behalf of the DSDP-PMC, since they are still
in the process of picking a successor for Doug Gaff to represent them on
the Planning Council. 

Sequoyah [1] is a re-packaging and expansion [2] of the Project previously
known as TmL [3]. 

TmL was in Galileo, but with all the transition and transformation into
Sequoyah their builds were not ready for M4. 

Eric Cloninger kept me informed of their status and outlook since December
of last year, so this isn't as "last minute" as it might appear.
Its been known for a while, plans in place, etc. and if anything, their
lack of a representative these past few months is the reason for no earlier
communication to the council (not, anything to do with the Project itself).

>From a business perspective, there are several justifications for allowing
this exception: 

1) The charter change was to allow a unified place for mobile application
development to occur, which is one of the growth areas for Eclipse

2) The project now contains the code behind Eclipse Pulsar (Eclipse Mobile
Industry Working Group) that has an EPP Package. 

As I have stated before, I would like to abstain from these Exception Votes,
to make sure you, the Planning Council, are fully on board, take responsibility
for the content of the Simultaneous Release, and avoid your tendency just
to do as I say (ha ha). So, I'll be looking for 3 +1 votes to consider
this "approved". Please indicate your approval, or not, by a
response to this planning council list. Since a full one week delay would
interfere with getting M5 done, I've told Eric he can take steps to get
in the build, as long as he is willing to revert, if it turns out there
are objections 
or a lack of support. 

Thank you, 

[1] http://www.eclipse.org/sequoyah/
[2] http://www.eclipse.org/sequoyah/reviews/MoveReview_DSDP-TmL-MTJ_2009-09-16.pdf
[3] http://www.eclipse.org/sequoyah/reviews/ReleaseReview_DSDP-TmL_0_4.pdf_______________________________________________
eclipse.org-planning-council mailing list
eclipse.org-planning-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-council

IMPORTANT: Membership in this list is generated by processes internal to
the Eclipse Foundation.  To be permanently removed from this list,
you must contact emo@xxxxxxxxxxx to request removal.
_______________________________________________
eclipse.org-planning-council mailing list
eclipse.org-planning-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-council

IMPORTANT: Membership in this list is generated by processes internal to
the Eclipse Foundation.  To be permanently removed from this list,
you must contact emo@xxxxxxxxxxx to request removal.