On Thu, May 31, 2012 at 8:20 PM, Wayne Beaton <wayne@xxxxxxxxxxx> wrote:
Try it now.
Wayne
On 05/30/2012 10:36 AM, Michael Golubev wrote:
Hello,
GMF-Tooling is one of the 15 projects that haven't submitted
IP logs yet.
I stuck with the problem which, to my understanding, is
related to the fact that we a) migrated from CVS to Git, and, b)
at the same time completely changed the set of active
committers.
As a result, the automated IP log generator creates a
hundreds of records [1] associated with GIT commits for old
commiters.
E.g, at the top of the table, there are ~7 pages of commits
from account 'ahunter()' which is the CVS login for Anthony
Hunter, correctly listed as 'Past and Present Active'
committer.
All of that commits had been just recreated in git repository
by the CVS -> Git migration, but the association between the
login and committer record is lost somewhere.
And the worst part is that in contrast to the contributions
from Bugzilla, where I can manipulate with iplog flag, I don't
see any ways to directly affect the presence of the records
associated with git commits.
I would appreciate any help and hope that I missed something
very simple.
On Mon, May 28, 2012 at 11:24 PM, Wayne Beaton <wayne@xxxxxxxxxxx>
wrote:
Greetings folks.
I've been creating tracking bugs for each project release
as I've received IP Logs.
At this point, I have created tracking bugs for 55
projects [1]. There are 72 projects on the list [2]. I
know that two of them are contributing bits from
already-completed releases, so that still leaves 15
projects that have not submitted their IP Logs but need to
do so.
Sharon is starting to work her way through the IP logs
that have been submitted, so there is still time to get
yours in.
Note that I've discovered missing stuff from about half of
the logs. You need to assume that you're going to need a
day or so to resolve problems. If you have not already
done so, please submit your log now or soon.
If I have bounced your log back to you for clarification,
please action that now or soon.
Review documentation is due on June 6th at the *latest*.
We have considerably less wiggle room for this than we do
for IP logs. If you're late, you'll miss the June 13th
end-of-review date and we'll have to schedule an
embarrassing couldn't-get-our-crap-together follow-up
review.
Sooner is better than later. Feel free to upload your
PMC-approved review documentation as an attachment on the
tracking bug for your release; you can still email it to emo@xxxxxxxxxxx
if you'd prefer. Please provide a link to the PMC
discussion (and approval) regarding the review material.