Re: [cross-project-issues-dev] Equinox fix for Luna SR1 now available as

[Thomas Hallgren <thomas@xxxxxxx>]

+1

I would really like to see p2 leveraged (the way it was designed to) to make it really easy to push fixes like this out 
to the community in a controlled but swift manner.

- thomas

On 2014-11-02 11:07, Max Rydahl Andersen wrote:
> On 31 Oct 2014, at 19:56, David M Williams wrote:
>
> > I am not sure if this bug was discussed directly on this list, or, just
> > some of its predecessors, but, we have an "official fix" available for
> > anyone impacted by
>
> Really appreciate the work for fixing this nasty subtle bug.
>
> But can we have a chat about why the Eclipse release train does not seem to have a *good* way to release updates for 
> this ?
>
> By "Good" I mean one that just gets available via Check For Updates rather that one that does not require users to 
> aware of having to install a specific feature patch ?
>
> I think Eclipse survived this far because we haven't really had any big "all impacting stop ship bugs", but lately 
> they are starting to crop up - this issue with System properties being the worst one (that I know of).
>
> Can someone remind me why we can't in these cases do an update that fixes this bug ? Is it technical because the 
> release train is to hardly coupled and we have feature's using exact versions and that p2 won't let you update the 
> plugins on their own ?
>
> ...or is there also some political agenda on how we provide these updates ?
>
> In any case - I think it would be worth finding a way to update these technical and political limitations to make it 
> easier to do timely stop-ship bug updates?
>
> wdyt ?
>
> /max
> http://about.me/maxandersen
> _______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev