Menu
▾
▴
#20 Fixes are not dependencies
If a change is entered as a fix for another change,
the fix can still show up in the "Safe to Apply" list,
even if the original change is not applied. It might
make sense to make the fix dependent on the original
change, whether they use the same files or not.
Logged In: YES
user_id=280857
The fix no longer shows up in the safe to apply list.
However, if a change is stamped as passed, the fixes for it
are stamped as passed as well. Even if those fixes have
not been applied. I'd like to see hop confirm that the
fixes have been applied and display "Fix xxxx must be
applied before this change can be passed", if they haven't
been.
Logged In: YES
user_id=209227
Personnally I don't think we need to make fixes into
dependencies (in fact I deliberately avoided it)--it is
quite conceivable that a Fix might be completely
independent of the broken change unit. In fact I've seen
it happen that another change unit is already in Hop, all
you have to do is add a fixes/fixed by entry to the
existing thing and you're done. There is no need to
introduce a dependency usually. All the information is
already there. However, a warning would be fine as long as
it didn't confuse anybody.