On Jun 2, 2012 3:19 PM, "O. Hartmann" <ohartman@zeda...> wrote:
> On 06/02/12 14:47, Daniel Kalchev wrote:
> > On 02.06.12 15:32, Erich wrote:
> >> I know that the ports tree is a moving target. But it stops moving
> >> during the release period. This could be used to give a fall back
> >> solution.
> >> Or do I see this really too simple?
> > The ports tree is a moving target during release periods still, although
> > there are efforts to make movements smaller. This is why, after a
> > release it suddenly moves more :)
> > Daniel
> Even IF the ports tree IS a moving target, updating of UPDATING, for
> instance, follows most times AFTER the critical ports has been
> changed/updated and folks started updating their ports without realizing
> that they have shot themselfs into the foot!
Not reading UPDATING until there are problems is not the fault of the ports
tree; it should be checked every time you update.
Of course, many of us forget, but that still doesn't make it anyone else's
problem when we do!