When an issue has a report in Mantis we have to maintain the information
there, like the status. When a fix is moved from the inbox to trunk the associated issue needs to be 'resolved' as fixed in trunk and with a quick note noting the URL or filename and that it has been moved into the trunk. Ken On Sun, 2009-08-23 at 20:26 +0000, [hidden email] wrote: > Andreas Raab uploaded a new version of System to project The Trunk: > http://source.squeak.org/trunk/System-rkrk.133.mcz > > ==================== Summary ==================== > > Name: System-rkrk.133 > Author: rkrk > Time: 23 August 2009, 6:06:34 am > UUID: d65acf42-f8d7-400a-a4f1-2d8a9ab09cbb > Ancestors: System-ar.132 > > Fixed Preferences giveHelpWithPreferences. > > See http://bugs.squeak.org/view.php?id=7391 > signature.asc (196 bytes) Download Attachment |
Ken Causey wrote:
> When an issue has a report in Mantis we have to maintain the information > there, like the status. When a fix is moved from the inbox to trunk the > associated issue needs to be 'resolved' as fixed in trunk and with a > quick note noting the URL or filename and that it has been moved into > the trunk. You're right. I'll do that. Cheers, - Andreas > On Sun, 2009-08-23 at 20:26 +0000, [hidden email] wrote: >> Andreas Raab uploaded a new version of System to project The Trunk: >> http://source.squeak.org/trunk/System-rkrk.133.mcz >> >> ==================== Summary ==================== >> >> Name: System-rkrk.133 >> Author: rkrk >> Time: 23 August 2009, 6:06:34 am >> UUID: d65acf42-f8d7-400a-a4f1-2d8a9ab09cbb >> Ancestors: System-ar.132 >> >> Fixed Preferences giveHelpWithPreferences. >> >> See http://bugs.squeak.org/view.php?id=7391 >> > > > ------------------------------------------------------------------------ > > |
In reply to this post by Ken Causey-3
On Mon, Aug 24, 2009 at 11:47:43AM -0500, Ken Causey wrote:
> When an issue has a report in Mantis we have to maintain the information > there, like the status. When a fix is moved from the inbox to trunk the > associated issue needs to be 'resolved' as fixed in trunk and with a > quick note noting the URL or filename and that it has been moved into > the trunk. There are some issues in Mantis that have been resolved in the trunk, but still have status of "new", "testing", etc. I have set a couple of these to "resolved" based on the note above, even though I'm not the person who added the fix to the trunk (hopefully that is OK?). There are plenty more that should be updated. In some cases, the actual changes in the trunk may not be the same as those in the change sets on Mantis, which would pose a problem for building an image automatically from links to the Mantis change sets. Personally, I don't have a lot of confidence in some of those "fix begin" links anyway, but it's still a problem if you want to build an image directly from the various documented patches. Dave |
David T. Lewis wrote:
> On Mon, Aug 24, 2009 at 11:47:43AM -0500, Ken Causey wrote: >> When an issue has a report in Mantis we have to maintain the information >> there, like the status. When a fix is moved from the inbox to trunk the >> associated issue needs to be 'resolved' as fixed in trunk and with a >> quick note noting the URL or filename and that it has been moved into >> the trunk. > > There are some issues in Mantis that have been resolved in the trunk, but > still have status of "new", "testing", etc. I have set a couple of these > to "resolved" based on the note above, even though I'm not the person who > added the fix to the trunk (hopefully that is OK?). There are plenty more > that should be updated. > > In some cases, the actual changes in the trunk may not be the same as > those in the change sets on Mantis, which would pose a problem for > building an image automatically from links to the Mantis change sets. > Personally, I don't have a lot of confidence in some of those "fix begin" > links anyway, but it's still a problem if you want to build an image > directly from the various documented patches. Could one solve this by uploading a changeset containing the actual fix to the Mantis issue? This could be a common situation, anyway. Foo proposes a fix, but Bar, the package maintainer, sees a slightly better way, inspired by Foo's proposed fix. Bar commits the change, uploads the change to the Mantis issue (*), and marks the issue as "resolved". (*) This should be automatic, of course!) frank frank |
Free forum by Nabble | Edit this page |