It may not be super easy for people (including me) to follow the flow of
known bugs. Today I struck Bug #2246: deleting an environment also deletes the provisioning templates - Foreman and a
quick mention on #theforeman immediately got a "known bug" from the ever so
responsive Greg… (thanks!)
What's your take on a Mailing list such as foreman-announce for releases
and errata for last N supported stable versions of Foreman (security or
recommended patches) and each stable release on theforeman.org to have link
to a page with current Errata / Known bugs. You probably already considered
some of this since you went through a few of the Rails CVEs recently.
Perhaps Redmine can be reused somehow, so it doesn't have to be a
separately managed list. But I won't bet on it.
I know this requires resources too, like everything else. Responding to
known bugs on mailing lists and IRC ought to consume some resources too. If
the increased and decreased resources can offset each other even slightly
it may be worth it.
···
--
Mikael
> It may not be super easy for people (including me) to follow the flow of
> known bugs. Today I struck Bug #2246: deleting an environment also deletes the provisioning templates - Foreman
> and a quick mention on #theforeman immediately got a "known bug" from
> the ever so responsive Greg… (thanks!)
>
> What's your take on a Mailing list such as foreman-announce for releases
> and errata for last N supported stable versions of Foreman (security or
> recommended patches) and each stable release on theforeman.org
> <http://theforeman.org> to have link to a page with current Errata /
> Known bugs. You probably already considered some of this since you went
> through a few of the Rails CVEs recently.
I'm definitely in favour of an announce list generally, where all new
releases are announced, major, RC and bug fix releases. We could use it
for severe known bugs, but I personally wouldn't have classed #2246 as
one worthy of e-mailing everybody over.
> Perhaps Redmine can be reused somehow, so it doesn't have to be a
> separately managed list. But I won't bet on it.
I'm not sure, though it would help if Redmine had an "Affected version"
field, similar to the Puppet one. We really need to upgrade Redmine and
it would give us this feature.
···
On 15/05/13 11:34, Mikael Fridh wrote:
–
Dominic Cleal
Red Hat Engineering
