Leo Famulari <l...@famulari.name> writes: > When moving packages around, all users of the package need to have their > module imports updated. Copyright attribution must be carefully handled. > And merging the various *-updates branches into master and vice versa > becomes more complicated and prone to error.
Perhaps it makes sense to schedule package moves just after big merges (e.g. before cutting a new core-updates branch). Or have them in separate short-lived branches to give users (and Hydra, considering the recent tcsh evaluation failure) some time to test and prepare. My 2 NOK, Marius
