On Thu, 28 Nov 2013, Yaroslav Halchenko wrote:
in case an ftp trainee has checked the -1 version and now sees a new one, he would not be delighted by this, as his previous work would be just a waste of time.is that from personal experience?
I just wanted to mention an argument from a different perspective. As with every team, there are different ways of working. So depending on the person really working on a package, uploading version -2 might be good or bad.
debdiff between the two would quickly show what was changed/fixed thus possibly addressing already enlisted concerns which trainee would need to deal upon resubmission anyways, thus imho the situation would be a win-win
Did you have a look at dak[1]? From my point of view debdiff is not part of the normal workflow. Anyway, you are right that debdiff between two packages of the same version is manageable. But if you also upload a new version, the diff might be too lengthy ...
mne is so early in the queue that it is doubtful anyone is looking at it atm anyways
According to [2] packages in new are handled bursty, so the queue might be empty soon :-).
Thorsten [1]http://ftp-master.debian.org/git/dak.git [2]http://ftp-master.debian.org/stat.html