Re: Thoughts welcome: interface between automated test gating and the "critical path"

2022-08-30 Thread Ben Cotton
From my perspective, anything that blocks the release is on the critical path. So any time there's a violation of the release criteria and the package is not on the critical path definition, that's a bug in the definition. I recognize that this is a somewhat naïve view. For one, it may broaden the

Thoughts welcome: interface between automated test gating and the "critical path"

2022-08-30 Thread pmkel...@frontier.com
On 8/29/22 6:50 PM, Adam Williamson wrote: Hi folks! I have one of those definitional quandaries and I figured I'd throw it at the lists for some input. I spent some years as a project manager and I have lots of experience with schedules. The term Crital Path was formalized in the business

Re: Thoughts welcome: interface between automated test gating and the "critical path"

2022-08-30 Thread Adam Williamson
On Tue, 2022-08-30 at 09:39 +0300, Alexander Bokovoy wrote: > On ma, 29 elo 2022, Adam Williamson wrote: > > On Tue, 2022-08-30 at 00:32 -0400, DJ Delorie wrote: > > > It sounds to me like the problem is "how do we best use the available > > > automated test resources?" so I'll answer accordingly.

Re: Thoughts welcome: interface between automated test gating and the "critical path"

2022-08-30 Thread Adam Williamson
On Tue, 2022-08-30 at 09:14 -0400, Ben Cotton wrote: > From my perspective, anything that blocks the release is on the > critical path. So any time there's a violation of the release criteria > and the package is not on the critical path definition, that's a bug > in the definition. > > I recogniz