| Re: [scout-dev] bugzilla tickets updated for scout 3.7.1 |
|
Please note that it is generally preferred to set the iplog+ flag on
attachments. The IP Log tools provide a lot of help with contributions. But you need to do some work to leverage this help. If you set the iplog flag on an attachment that contains a contribution (e..g a patch), that contribution will appear in an automatically-generated log (note that, iplog+ marked contributions from existing committers will be skipped). This is probably the most natural way to use the flag. To set this flag, open the "Details" for the attachment, set the value to “+”, and commit. That’s it. Do this for any attachment that contains something that you’ve committed into an Eclipse source code repository. This includes things like code patches, image files, XML schemas, and pretty much anything else. Only mark those attachments that actually make it into the project's code repository; just leave any other attachments alone. There is more information here: http://wiki.eclipse.org/Development_Resources/IP_Log#Contributions HTH, Wayne On 10/11/2011 03:18 AM, Matthias Zimmermann wrote: hello all ticket status for scout 3.7.1 (indigo sr1) is now up to date. to check resolved tickets in this service release you may consider the scout indigo wiki page [1] @committers: please make careful and correct use of the following bugzilla fields: - Target Milestone (new tickets fixed on indigo need to have 3.7.2 here, even if they're also fixed for juno) - iplog (all applied patches from non-scout committers need to be flagged by selecting the '+') [1] http://wiki.eclipse.org/Scout/Release/Indigo#Bugzilla_Tickets best matthias_______________________________________________ scout-dev mailing list scout-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/scout-dev -- Wayne Beaton The Eclipse Foundation Twitter: @waynebeaton |