[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [cross-project-issues-dev] Status and outlook for Indigo M7
|
> I'm new to this release train and was wondering what I had to do to
> be part of the Java EPP package? Can you point me to some
> documentation or describe the process?
You might find some interesting links by starting at EPP's home page [1] (though, I suspect some info there might be out of date? ... just guessing)
But the short answer is to start the discussion by opening a bugzilla entry in EPP [2]. To see some examples, you might search that bugzilla component with "add" or "create" in title, but from quick peek I found three that might be useful (and, I do mean maybe ... others may know better examples?) [3, 4, 5] Also, the epp-dev list [6] might be a good place to ask specific questions about EPP package development and additions.
Glad I asked ... :) ... Good luck,
[1] http://eclipse.org/epp/
[2] https://bugs.eclipse.org/bugs/enter_bug.cgi?product=EPP;component=java-package
[3] https://bugs.eclipse.org/bugs/show_bug.cgi?id=233592
[4] https://bugs.eclipse.org/bugs/show_bug.cgi?id=272947
[5] https://bugs.eclipse.org/bugs/show_bug.cgi?id=303198
[6] http://dev.eclipse.org/mhonarc/lists/epp-dev/
Mark Russell ---04/22/2011 06:56:06 AM---HI David: I'm the build person for the WindowBuilder component. In your email you
From: Mark Russell <mrrussell@xxxxxxxxxx>
To: Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Cc: Eric Clayberg <clayberg@xxxxxxxxxx>
Date: 04/22/2011 06:56 AM
Subject: Re: [cross-project-issues-dev] Status and outlook for Indigo M7
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx
HI David:
I'm the build person for the WindowBuilder component. In your email you said:
In fact, what is the status of WindowBuilder? I've heard rumors they would like to be part of the Java EPP package, but don't recall seeing a bugzilla open there to discuss, and initiate the work required to make that happen, so ... did I miss it?
I'm new to this release train and was wondering what I had to do to be part of the Jave EPP package? Can you point me to some documentation or describe the process?
On Thu, Apr 21, 2011 at 3:21 PM, David M Williams <david_williams@xxxxxxxxxx> wrote:
What ... M7 status already?!
Yeah, it is a little early, but there are a few timely reminders and early issues.
First, I have promoted a warmup staging repo with everything that's been updated since M6.
http://download.eclipse.org/releases/staging/
One of the big ones updated is WindowBuilder ... try it out. I haven't yet, so hope the WindowBuilder team is really ready? I just saw the contribution file change and the aggregation build still worked.
In fact, what is the status of WindowBuilder? I've heard rumors they would like to be part of the Java EPP package, but don't recall seeing a bugzilla open there to discuss, and initiate the work required to make that happen, so ... did I miss it?
[I'm partially asking openly, here on cross-project, to emphasize that one thing that's really important for the Simultaneous Release is lots of communication, so everyone knows what's going on ... even if key players already know, or it "seems obvious" to some, it's often not so obvious to others. And, who know, maybe they were only rumors and not really, or no longer, true?]
The second "early issue": there's several features or repositories that (still) have enabled="false". I don't recall any history about a few of them, so will ask here in case I've missed something. But, if I don't hear anything soon, I'll assume they should be removed from aggregation. Apologies if this was all explained to me before and I've forgotten.
dsdp-sequoyah.b3aggrcon (2 features disabled: org.eclipse.sequoyah.device.examples.feature and org.eclipse.sequoyah.vnc.protocol.examples.feature)
emft-eef.b3aggrcon (here, whole repo/contribution is disabled)
gmp-gmf-tooling.b3aggrcon (I do recall this one ... Anthony's said before it should be removed, so I will).
Third, I suggest the Platform contribute a "warm up" repository early next week, before their final contribution on +0 day on Friday (4/29). While that will likely "break the build" (for a few, dependent projects) it is an easy way to get an early indication of problems, that projects might need to react to, so there is more time to react, and not such a ripple effect the following week (5/2 to 5/4) when everyone is contributing everything final for M7. It does help others contribute "warm-up" deliveries, so they can sanity check things before their final contribution.
Thanks everyone ... everything has been going well this release, and I'm sure it'll be an easy few weeks leading up to a solid M7!
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
--
Mark R Russell
(724) 473-3140
Release Engineer
Google Pittsburgh
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev