<div>I think i haven't explain myself as i should. The thing was that: developer A uploaded a package on the past release circle, then a merge was publiched on MoM, a contributor take the merge, work on it and upload the debdiff to launchpad reporting the bug as it needs to be, the developer A commented on that bug report, so we can be sure that he knows about the contributor working on that merge, then developer B work on that merge and upload it by himself without noticing the bug report and contributor's work.</div>
<div>That, on the side of the contributor, being a new one, is a really bad thing because he wanted to be his work on the repos, but not only it isn't there, it has been done and uploaded by someone else.</div>
<div>DaD's comments were a good feature to avoid such things, if contributor left a comment in there, the developer B could see it and work on another merge.<br><br></div>
<div class="gmail_quote">On Tue, May 13, 2008 at 8:18 AM, Scott Kitterman <<a href="mailto:ubuntu@kitterman.com">ubuntu@kitterman.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>
<div></div>
<div class="Wj3C7c">On Monday 12 May 2008 20:51, Nicolas Valcarcel wrote:<br>> Hi,<br>> Since hardy i have notice that some times contributions are not taking<br>> into account, mostly on merges. For MOTUs and core devels is not needed to<br>
> file a bug since it's only needed to upload the package, but some times, a<br>> contributor, which need to file a bug, upload his debdiff and ask for<br>> sponsorship, make the work for nothing, becase one developer (no one in<br>
> special) work on that merge and upload it. I think is not fair, and<br>> discourage for new contributor, so i think it lack for a common process<br>> where this things doesn't happen.<br><br></div></div>I appreciate your problem. I remember such things happening in the past too.<br>
It's unfortunate when such things happen, but I don't know what can be done<br>to prevent it completely. MOTU are supposed to check bugs when they do a<br>merge.<br><br>Ideally we'll have the new merged (pun intended) MoM and DaD up soon so there<br>
is one place to go for merge information that can include comments about what<br>people are working on. That should help too.<br><br>From our IRC discussion, I gather you had discussed the merge with the<br>previous uploader, but that the MOTU that uploaded his own merge (apparently)<br>
did not. While there is no rule requiring people to check with the last<br>uploader, I still think it is generally a good idea (particularly early in<br>the release cycle when there is no great rush to get merges uploaded). That<br>
might have avoided the problem in this case.<br><br>I think we have sufficient process in place (MOTU should check bugs before<br>uploading a merge to see if there are other fixes that should be included) or<br>coming (single source of merge information with comments) to minimize this<br>
problem. I don't think we'll ever eliminate it completely.<br><br>Scott K<br>
<div>
<div></div>
<div class="Wj3C7c"><br>--<br>Ubuntu-motu mailing list<br><a href="mailto:Ubuntu-motu@lists.ubuntu.com">Ubuntu-motu@lists.ubuntu.com</a><br>Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu" target="_blank">https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu</a><br>
</div></div></blockquote></div><br>