I may be over-optimizing. In the last two days I was going through all my email from 18 Dec onwards and I felt bad for our users who had broken stuff.
I don't think it would have changed what was in the release (i.e. no-respins) - but I think it would have changed the perception on turnaround time and the attention span of people. All those issues were detected within the first 48 hours of the release and fixed/resolved/workedaround within 1 or 2 working days. But because so many people (me included) were in downtime for the holidays it took 3 calendar weeks to resolve everything.
I don't think any of those issues will be caught before release - and I don't think similar issues will be caught next time before release because there is insufficient testing capacity to detect them.
BTW - there is a whole separate conversation about how to handle "hotfixes" for simrel post release which I would love to resolve globally, but for now I have a solution for the CDT part when users are using the CPP EPP.
Thanks,
Jonah
Hi Jonah,
I understand your reasoning, but are you sure that a December release
happening a week earlier would have significantly changed the outcome?
The missing announcement could have easily been fixed, but what about
the other two issues? Both issues were found after SimRel was out of the
door. Both would probably not have justified a respin.
I'd recommend that we try to improve the testing scenarios ahead of the
release (e.g. "check file associations", "basic dark theme test") to
catch such issues. This should by all means not mean more testing/work
for you, though!
Regards,
Fred
On 06.01.21 03:26, Jonah Graham wrote:
> Hi folks,
>
> I was wondering if we could consider changing the December release date
> to a little earlier? Perhaps something for discussion at our call tomorrow?
>
> My main reason is that this release happens in the days just before
> Christmas, and what I have found is that it is hard to get anything to
> move fast when there are problems in the release because of the
> Christmas break.
>
> I have dealt with three issues since the release that are all getting
> resolved quickly this week, but were all identified within a day or two
> of the release.
>
> These are the issues I am referring to above for context:
> 1- Eclipse IDE release being announced on the eclipse.org
> <http://eclipse.org> home page
> (https://www.eclipse.org/lists/cross-project-issues-dev/msg18123.html)
> 2- Dark mode very broken for users with Tracecompass installed
> (https://www.eclipse.org/lists/cross-project-issues-dev/msg18128.html)
> 3- Broken CDT setup for some users
> (https://bugs.eclipse.org/bugs/show_bug.cgi?id=569796)
>
> Thanks.
> Jonah
>
>
> ~~~
> Jonah Graham
> Kichwa Coders
> www.kichwacoders.com <http://www.kichwacoders.com>
>
> _______________________________________________
> eclipse.org-planning-council mailing list
> eclipse.org-planning-council@xxxxxxxxxxx
> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/eclipse.org-planning-council
>
--
Frederic Gurr
Release Engineer | Eclipse Foundation Europe GmbH
Berliner Allee 47, D-64295 Darmstadt
Handelsregister: Darmstadt HRB 92821
Managing Directors: Gaël Blondelle, Mike Milinkovich
_______________________________________________
eclipse.org-planning-council mailing list
eclipse.org-planning-council@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/eclipse.org-planning-council
