Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Equinox fix for Luna SR1 now available as a feature patch in "4.4" repository.

----- Original Message -----
> From: "Thomas Hallgren" <thomas@xxxxxxx>
> To: "Cross project issues" <cross-project-issues-dev@xxxxxxxxxxx>
> Sent: Tuesday, November 4, 2014 9:36:32 AM
> Subject: Re: [cross-project-issues-dev] Equinox fix for Luna SR1 now available as a feature patch in "4.4"
> repository.
> Hi David,
> I think it's fairly evident that the testing that was made prior to SR1 was
> insufficient and I can understand why. Projects have limited resources
> nowadays and unfortunately rigorous testing is one of the first things that
> gets a cutback. With lowered quality as a natural consequence. The way I see
> it, that problem can be attacked in one of two ways:
> 1. See to that the service releases really get tested rigorously which means
> that organizations must put up the resources needed to do so. The release
> train must be subject to integration testing.

So, to jump in,
Who is going to do the testing? Is anybody signing for fixing/improving the test suites? We are at a level where ideas don't bring anything - "show me the code" is the only thing that matters now from my POV.

> 2. Let the Eclipse users take the hit (like we already do now) and make sure
> that any problems that are discovered are remedied more or less immediately
> (i.e. push a new build of the release train or platform without delay). In
> essence, this would remove the need for service releases.

Again, who would do the work? Speaking of platform builds only, there are so many things to improve in the build process and they are a prerequisite before being able to spin a new release and be sure that the build will finish first, is good, doesn't regress and last but not least hasn't costed too much time to the one doing the builds. Everybody is welcome to jump in, pick something from and fix it, with every fix the probability of faster and easier releases increases.

> What we have now is the worst case of all. Virtually no integration testing
> and when bugs are found, no immediate new release.

I totally agree with you that this is worst case. The only thing I would like to clarify is that this is not the problem, it's the result from very few people contributing to the lower/common/shared bits we all rely on. Until this changes the situation will stay the same as no matter what we think/discuss and etc. at the end of the day someone have to step in and do it, which sadly doesn't happen in many cases for stuff discussed.

Alexander Kurtakov
Red Hat Eclipse team

> I wasn't referring to feature patches with my remark about p2 (I'm not much
> fond of them either). I was referring to p2's ability to deliver updates in
> a safe and controlled manner.
> - thomas
> _______________________________________________
> 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

Back to the top