<br><div class="gmail_quote">On Tue, May 13, 2008 at 2:48 PM, Scott Kitterman <<a href="mailto:ubuntu@kitterman.com">ubuntu@kitterman.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Tuesday 13 May 2008 17:22, Nicolas Valcarcel wrote:<br>
> I think i haven't explain myself as i should. The thing was that: developer<br>
> A uploaded a package on the past release circle, then a merge was publiched<br>
> on MoM, a contributor take the merge, work on it and upload the debdiff to<br>
> launchpad reporting the bug as it needs to be, the developer A commented on<br>
> that bug report, so we can be sure that he knows about the contributor<br>
> working on that merge, then developer B work on that merge and upload it by<br>
> himself without noticing the bug report and contributor's work.<br>
> That, on the side of the contributor, being a new one, is a really bad<br>
> thing because he wanted to be his work on the repos, but not only it isn't<br>
> there, it has been done and uploaded by someone else.<br>
> DaD's comments were a good feature to avoid such things, if contributor<br>
> left a comment in there, the developer B could see it and work on another<br>
> merge.<br>
><br>
I think I got that and agree it's unfortunate. The contributor certainly has<br>
my sympathy. I completely get the frustration. I just don't know what can<br>
be done that isn't already planned.<br>
<br>
A strict check with the last uploader rule would likely have solved this, but<br>
the community rejected that approach last time it was discussed.<br>
<div><div></div><div class="Wj3C7c"><br>
</div></div></blockquote></div><br>I too agree that it's unfortunate. However, I don't think it's something people should be getting too upset about (people make mistakes) and I don't think ping-last-uploader is a proper solution to the issue, for various reasons.<br>
<br>My feeling is that the best way to help make sure this kind of thing doesn't happen is to have *one*, canonical place to track merges. Launchpad bugs seems to be the best way we have of doing that currently. Basically, file a merge bug if you're going to be working on a merge and *all* people working on merges, including MOTU sponsors, should be looking *first* to see if somebody has already filed a bug before working on it.<br>
<br>-Jordan<br>