Hi Bjorn,
this is very exciting!
Can you share a little bit of technical detail, e.g. based on
what information
you're planning to have the automatic IP Log generated?
Are you going to
use Bugzilla's "attachment isPatch" field together with a check whether
the
attachment has been created by a non-committer, and the bugzilla FIXED
state?
Are you going to take the bugzilla "contributed" keyword into
account?
Note that we have bugs where contributors attached patches, but the
final
fix was created by a committer without using the contribution. I'm
really
curios how you're planning to sort these things out -- personally, as
well
as on behalf of my project, since I want to know whether we'll be in
bucket 2 or bucket 3.
Thanks,
--
Martin Oberhuber, Senior Member of Technical
Staff, Wind River
Target Management Project
Lead, DSDP PMC Member
Ganymede teams and leads,
In a last minute attempt to reduce
your workload, Janet and I are implementing an "automatic IP log" feature as
described in https://bugs.eclipse.org/bugs/show_bug.cgi?id=220977
You are in one of these four buckets:
- Saved by the Bell. You have not yet submitted an IP log and you
would like to use the automatic IP log feature
- Relieved at Lower Effort. You have already submitted an IP log
but you'd like to swith to the automatic IP log
- Stay the Course. You have already submitted an IP log and do not
want to use the automatic IP log this year
- Luddite. You have not yet submitted an IP log but still want to
do your IP log manually this year
If you are in bucket 1, please
wait for another email early next week where we will explain how to use the
one-button "submit the automatic IP log" feature. If you are in bucket 2
or 3, we (Janet and I) will check your submitted IP log against the automatic
one and tell you how to reconcile the two. If you are in bucket 4, well,
you're about to be late with your IP log (they are due in 5 1/2 hours from
this email) and you need to send it to Janet ASAP.
Thanks,
Bjorn
& Janet