> (Moved discussion from bug to Equinox mailing list) Why? I prefer to keep discussions in bug reports.
And, it would not be an Equinox specific question/issue. Dani From: Gunnar Wagenknecht <gun...@wagenknecht.org> To: equinox-dev@eclipse.org Date: 30.07.2018 18:00 Subject: Re: [equinox-dev] [Bug 531680] [code mining] Avoid cancellation by exception Sent by: equinox-dev-boun...@eclipse.org (Moved discussion from bug to Equinox mailing list) >> As for the other comments, is introducing this as a new default method on >> IProgressMonitor and coordinating a release with fixes upstream possible? Or >> will that never allowed? > > Following the rules as they are now that would require a major version > increase. Not something I think is justified to fix this issue. What are the general plans here? I'd like to see the specific issue fixed in a good way. Having the new default method on IProgressMonitor seems like a clean approach. However, I tend to agree that this is a big change (in terms of impact). Are there any plans to have another major version? What are the main concerns in that area? -Gunnar _______________________________________________ equinox-dev mailing list equinox-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________ equinox-dev mailing list equinox-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/equinox-dev
