Added option for including priority/milestone to cros_changelog.

Added option for including priority/milestone to cros_changelog.

You can access this by passing:
   --tracker-user="user@chromium.org"
   --tracker-passfile="fileContainingPassword"

...to access anonymously, just set --tracker-user=""

...if you don't include the --tracker-user option, we won't try to
fetch priority/milestone.

To use this feature, you need the GData library.  Until we get that
put in hard-host-depends, the script will simply print instructions
for installing GData if it detects that you don't have it.

At the moment, I believe that logging in isn't giving you any extra
access.  Therefore, any bugs that don't allow anonymous access will
not show their priority/milestone.  I am working on figuring out what
the problem is there.

Change-Id: If388c20c43ee2fb0c1ab8f748ffea65e354eeb1e

BUG=chromium-os:8205
TEST=Ran ./cros_changelog 0.9.104.0 --tracker-user="" and verified that some bugs got priority/milestone.

Committed: http://chrome-svn/viewvc/chromeos?view=rev&revision=48849e2

[diandersAtChromium, 2010-10-29 18:01:13]

Getting this submitted in, even though it seems to have trouble accessing
protected bugs (even if you give it a username/password).  It seems like it is
useful even now.

I'm going to keep working on this a bit, first focusing on the protected bugs
and then misc other cleanup tasks.

Let me know if you would like a different format for things.

[diandersAtChromium, 2010-10-29 18:47:07]

Fixed login problems.  Proving a username / password will now get you access.  

One note: if you are running this script with full access then publishing the
results to the world, you are potentially publishing information that the world
shouldn't have access to...  At the moment, this is only priority / mstone
information, but it is something to be careful of.

On 2010/10/29 18:01:13, diandersAtChromium wrote:
> Getting this submitted in, even though it seems to have trouble accessing
> protected bugs (even if you give it a username/password).  It seems like it is
> useful even now.
> 
> I'm going to keep working on this a bit, first focusing on the protected bugs
> and then misc other cleanup tasks.
> 
> Let me know if you would like a different format for things.

[davidjames, 2010-10-29 21:23:23]

LGTM w/nits

http://codereview.chromium.org/4102013/diff/5001/6001
File chromite/bin/cros_changelog (right):

http://codereview.chromium.org/4102013/diff/5001/6001#newcode113
chromite/bin/cros_changelog:113: info_str = ' (%s)' % (self.milestone)
No need for parens here. Just end with % self.milestone.

http://codereview.chromium.org/4102013/diff/5001/6001#newcode115
chromite/bin/cros_changelog:115: info_str = ' (P%s)' % (self.priority)
Same here.

http://codereview.chromium.org/4102013/diff/5001/6001#newcode290
chromite/bin/cros_changelog:290: options.tracker_pass =
open(options.tracker_passfile, "r")
Can you just open and read the file here, rather than passing in a file object?

http://codereview.chromium.org/4102013/diff/5001/6002
File chromite/lib/tracker_access.py (right):

http://codereview.chromium.org/4102013/diff/5001/6002#newcode38
chromite/lib/tracker_access.py:38: # Assume password is a file-like object and
read out the password.
Let's get rid of the whole condition and just always pass in the password as a
string.

http://codereview.chromium.org/4102013/diff/5001/6002#newcode127
chromite/lib/tracker_access.py:127: # If password was specified as a file, we'll
get a file path...
Please always pass in the password as a string. Easier :)

http://codereview.chromium.org/4102013/diff/5001/6002#newcode143
chromite/lib/tracker_access.py:143: if (len(args) >= 2) and (args[0] == "help")
and (args[1] in commands):
Too many parens. Remove the extra ones.

http://codereview.chromium.org/4102013/diff/5001/6002#newcode164
chromite/lib/tracker_access.py:164: if (len(sys.argv) <= 1) or (sys.argv[1] not
in commands):
Remove extra parens.