(No comment was entered for this change.)

(No comment was entered for this change.)

Yes, this would be a great feature!  :-)

+1

This would be great to use with http://timeline.to/

How is this different from  issue 131 ? What do you think of marking this as a
duplicate? Everyone who starred this issue can star #131 instead.

26 people starred this issue, that's a large amount of people to make re-star for the same thing. Why not just 
implement master tickets instead, and then when the master ticket closes, it closes all child tickets with the same 
message, rather than making a large amount of users do legwork.

It's already hard enough to use google code for anything, asking users to do something like that is that much 
harder.

cforsythe, as far as I know, your suggestions are likely to pass unnoticed here. You
may wish to consider filing a new enhancement request about master tickets.

The suggestions are noticed, but the master tickets are much easier to track over
time as alexkon suggested.

(No comment was entered for this change.)

(No comment was entered for this change.)

We just announced feeds at the Google I/O conference this week,
and were planning to blog about it next week.   They're very 'beta',
but they work.

Try:

 http://code.google.com/feeds/p/PROJECT/svnchanges/basic
 http://code.google.com/feeds/p/PROJECT/issueupdates/basic

For the svn feed, you can also add '?directory=/path' to the end, to
restrict the subset of history.  For example, '?directory=/trunk'.

Another caveat:  these are gdata feeds that don't have infinite
history in them -- they only show *recent* changes, starting around
May 22nd.   They're meant to be 'update' feeds, rather than 'mine the
history' feeds.  Add them to your feed aggregator, or your iGoogle
homepage, or whatever.. you'll get nice news updates about projects
you care about.

We're still refining this feature, so it may morph a bit.

Correction: The url param is path=, e.g.

http://code.google.com/feeds/p/google-web-toolkit/svnchanges/basic?path=/wiki/
http://code.google.com/feeds/p/google-web-toolkit/svnchanges/basic?path=/tags/

Note the path param checks all paths for a string prefix match, so include the
trailing slash (/wiki/ not /wiki) if you want to restrict it to that directory.

This is a great start.

Couple of areas of improvement:

1. I would like to see the issue descriptions (titles) not truncated as aggressively.
I see issues titles cut-off fairly often

2. I'd like the commit message bodies to contain the normal (textual) svn diff as
well. Perhaps a "detailed" version of that feed would help.

In both cases I'm really just looking for the feed content to match the email content
coming from project hosting.

Thanks

HTML escaping needs a little tweak. For example, an ampersand ('&') in a SVN log
(commit) message turns into an escaped ampersand ('&') in Google Reader.

Yes, thanks for noticing the quoting bug in titles, I will fix that.  And I do think
the svn diff would be useful as well; however we may focus on adding more feeds
before enhancing existing feeds.

For the length of the issue titles -- the length is arbitrary but I think it has
worked well enough in practice, e.g. I don't see many cut off here:

http://code.google.com/feeds/p/google-web-toolkit/issueupdates/basic

I would like them to be 1 or 2 lines in Google Reader or other feed readers, and
right now it seems to be about right.

(No comment was entered for this change.)

As an example, see http://code.google.com/p/google-web-toolkit/source/detail?r=3123
for the original commit message. The Google Reader version is shown in attached
screen shot.

1. [bug] The new line whitespace is truncated, resulting in the words "no" and
"quite" being stuck together
2. [enhancement] I wouldn't mind seeing an ellipsis at the end of the feed title to
indicate the message was cut off.
3. [enhancement] I'd also like to see the actual textual diff as part of the feed

	r3123.gif
	31.4 KB Download

It is odd that those 2 words are stuck together.  When I look at the feed in Firefox
the spacing is right, and the newline is there in the raw text.  I will contact the
Google Reader team to see if this is a known issue with the way they display feeds.

http://code.google.com/feeds/p/google-web-toolkit/svnchanges/basic

Yes, the svn diff would be useful, I'll see what we can do about that.

The double escaping bug in titles of the svnchanges feed should now be fixed.