On 09/08/2016 01:05 PM, Peter Robinson wrote:
Sounds like this scope would warrant a Change?
The components should be already prepared for DNF-2 and the changes
are not huge. There's the FESCO ticket [5]. If it is not accepted then
we will submit a Change.
Actually, the preferred approach would be for this to come to FESCo *as*
a
Change. Mostly because the Change Process requires you to explain the
situation
fully and establish a contingency plan.
Completely agree, we (rel-eng and I'm sure others) don't want to find
out one day everything is broken due to this change and the compose is
up the spout. Core components such as dnf need to follow the process
properly and communicate far and wide so people are aware of the
changes in flight that could affect everything from builds to users
updating.
FESCo requested that a System Wide Change should be submitted for this.
Regards,
Dominik
Ok, we will file a System Wide Change then.
Yet it's not filed here [1] as a system wide change. Why?
The change proposal is in WIP state.
Given it's the updates system there, at least IMO, needs to be full contingency
plans etc. Sorry, the history of the dnf team not breaking stuff even
on small bumps gives me little faith this will be smooth.
The internal DNF testing stack undergone radical improvements during the
last year. Core DNF functionality is now covered by functional tests.
Therefore, we expect only minor issues with adoption of 2.0.
Michal
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
