Changes

|}

|}

The verification phase taking place before release should pick up hard dependencies which could break an update. What needs to be checked is where a package fixes three bugs and one was not verified. That means that only an older version of that package can be released. Also it can affect other packages if one of the fixes involved multiple packages. Note that  the 'Verified Package Versions' tab in Rnotes will track this - it does what Ian used to do normally and try to build a bug and package dependency graph.  

The verification phase taking place before release should pick up hard dependencies which could break an update. To the best of my understanding, RNOTES tracks hard dependencies. What needs to be checked manually is where a package fixes three bugs and one was not verified. That means that only an older version of that package can be released. Also it can affect other packages if one of the fixes involved multiple packages. Note that  the 'Verified Package Versions' tab in Rnotes will track this - it does what Ian used to do normally and try to build a bug and package dependency graph [To be confirmed].  

We can distinghish between "hard" and "soft" dependencies referred to in this document as follows:

The difference between "hard" and "soft" dependencies referred to in this document are:

:a) Hard dependencies are those from the spec file, eg: requires: e-smith-lib >= 2.0.0-2

:a) Hard dependencies are those from the spec file, eg: requires: e-smith-lib >= 2.0.0-2