Re: [cross-project-issues-dev] Use Milestones/RCs To Test and Run

[Ed Willink <ed@xxxxxxxxxxxxx>]

HI Lars

You seem to have missed the distinction.

The original bug was the philosophy change, initially endorsed, 
subsequently rejected as a bad regression.

The follow on bug was an ergonomic issue that violated even the changed 
philosophy. After reporting I back-pedalled on reproducibility. I 
suspect that the actual problem might well be idiot user; disabling 
auto-build or just not waiting long enough for all the time wasting 
background activities such as Bug 544272 to complete before the editor 
can refresh its markers usefully.

    Regards

        Ed Willink

On 17/12/2019 17:07, Lars Vogel wrote:
>  From Ed Willink,
>
> > Sadly some like https://bugs.eclipse.org/bugs/show_bug.cgi?id=545211 have to wait 9 months until the platform team 'duplicates'.
> Ed, if you open twice the same bug as you did with
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=544977 and
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=545211 it would be great
> if you can mark one of them yourself as dup instead of complaining
> about the time the platform team needs to find this.
>
> On Fri, Dec 13, 2019 at 2:12 PM Ed Willink <ed@xxxxxxxxxxxxx> wrote:
> > Hi
> >
> > Yes. It would be great and in the past I did that re-installing for many 6/8 weekly milestones. But with three weekly milestones, not all of which have a coherent set of contributions and four releases a year I just do not have time. In the past four RCs provided an opportunity for test. Now the platform is pretty much done before RC1 is declared complete. It's unacceptably fast and now you see the consequences. I just have to keep my fingers crossed interactively. API-wise, all my projects have a forced weekly rebuild that catches out quite a few regressions. Sadly some like https://bugs.eclipse.org/bugs/show_bug.cgi?id=545211 have to wait 9 months until the platform team 'duplicates'.
> >
> >      Regards
> >
> >          Ed Willink
> >
> > On 13/12/2019 10:23, Daniel Megert wrote:
> >
> > It would be great if everyone could at least test or even better, run on the latest milestone/RC. Platform got a stop ship bug for 4.13 and one for 4.14 reported after RC2. The 4.13 bug was introduced in M3 and the 4.14 bug in M1. So, there would have been enough room to find the bugs earlier.
> >
> > Of course the Platform team does exactly that but everyone has its own patterns how to work and hence, unfortunately did not detect those bugs.
> >
> > Thanks to everyone who helps with testing!
> > Dani
> >
> > _______________________________________________
> > 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://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
> >
> > _______________________________________________
> > 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://www.eclipse.org/mailman/listinfo/cross-project-issues-dev