Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] [URGENT] Indigo bug causes framework to keep bundle file handles open for lifetime of framework instance.

I didn't ask the other package maintainers so far, but I am sure they will agree that this bug is severe enough to justify a respin. Yes, there is a potential workaround out there but many users will install additional bundles during the next months and in that case it is very likely that their update to SR1 will fail, the update which is will be the first chance for a fix.

Let's try a respin then... (I have to admit that there is another reason why I like the idea of a respin: There was a rebuild of the common repository after the last EPP build. While we checked that there were no new contributions that could have influenced the packages, it leaves always a bad taste...)

Regards,
Markus




On 14 June 2011 08:25, David M Williams <david_williams@xxxxxxxxxx> wrote:
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





Back to the top