Re: [cross-project-issues-dev] [URGENT] Indigo bug causes framework to k

[Thomas Watson <tjwatson@xxxxxxxxxx>]

To reduce the risk of breaking the respin build we must limit the new contributions for addressing stop ship issues only. I would not touch your contribution for minor issues.

Tom



Mark Russell ---06/14/2011 09:09:42 AM---Newbie question: I have a general/theoretical question for respins like we are talking about. If a full respin is being done, d

From:	Mark Russell <mrrussell@xxxxxxxxxx>
To:	Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Date:	06/14/2011 09:09 AM
Subject:	Re: [cross-project-issues-dev] [URGENT] Indigo bug causes framework to keep bundle file handles open for lifetime of framework instance.

---

Newbie question:
I have a general/theoretical question for respins like we are talking about. If a full respin is being done, does it make sense to pick up small fixes to other bundles? We are happy with the state of our bundles, but we did have a very minor issue reported (Bug 349028 - missing name and provider) which we have fixed. If that is not a good idea, we are happy to wait until SR1 to pick up the fix.

On Tue, Jun 14, 2011 at 8:53 AM, Thomas Watson <tjwatson@xxxxxxxxxx> wrote:

Our build has completed. Are we ready to accept the re-contribution from Eclipse/Equinox? Or are we waiting for some others to respond and react before proceeding?

Tom



David M Williams---06/14/2011 01:26:59 AM---I've opened bug 349267 [1] to discuss and document the mechanics and investigation about _if_ we can cleanly respin the common

From:	David M Williams/Raleigh/IBM@IBMUS
To:	Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Date:	06/14/2011 01:26 AM
Subject:	Re: [cross-project-issues-dev] [URGENT] Indigo bug causes framework to keep bundle file handles open for lifetime of framework instance.

---




I've opened bug 349267 [1] to discuss and document the mechanics and investigation about _if_ we can cleanly respin the common repository and EPP packages.

The dry-run of the common repository aggregation went well, with only one project, PTP, showing changed features from our run last week. So, they also will need to comment in the bug to document how they would like to proceed/react.

I think next step is for the Eclipse Platform to re-contribute (when their build is done), and we'll see who else breaks, if anyone. RAP Runtime is the likely one (from experience) but there might be others.

Thanks

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=349267
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev



_______________________________________________
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