Google Project Hosting is all about helping software developers work together on source code, code reviews, issues, and wiki pages for technical documentation. In fact, the projects we host have collectively accumulated several million issue comments. Working together means that, from time to time, the ball is in your court and you need to respond to other users.
We send out notification emails to let the appropriate users know when an issue has been entered or a comment has been added to an issue, wiki page, or code review. These emails contain a link that allows you to enter your response in your project on code.google.com/p. But starting now, we are making it much easier and faster to respond to these comments by processing email replies that you send us.
So, check your inbox for new notification emails sent directly to you. When you see an email footer line that says that you can reply, just press the reply button in your email client, bang out a thoughtful response, and hit “Send”. Project committers and owners can even update an issue’s status and other values via email. For example, to let your teammates know that you are working on an urgent defect report that just came in, reply with:
| Subject: Re: Issue 123 in your-project: data loss when src == dst |
|
Status: Started Owner: your-email-address Label: Priority-High Thanks for that detailed defect report. I never realized that we need to handle that case specially. I’m going to add a check for it right now. |
Please try it out the next time you receive a notification email. If you have questions, see our documentation on inbound email and user groups.
This comment has been removed by a blog administrator.
ReplyDeletenice2see
ReplyDeleteOk google code might get even worse with this change for big projects (chrome, android, ...) where you want to vote/star for issues... Staring an issue automatically send all comments (even from non developers) to you by mail, with this change it's even easier to get "me too" comments...
ReplyDeleteThe situation now get to the point where only developers are allowed to comment on big starred issue
For small projects with a lot less noise on issues it's a welcome addition BTW.
This comment has been removed by a blog administrator.
ReplyDeleteVirtualBlackFox: Actually those large projects have already been testing email replies for quite a while now, with good results. Opening it up to every project is really more for the benefit of all the other smaller projects that we host.
ReplyDeletePlease keep in mind that the issue tracker is a software development tool, not a regular discussion forum. Most projects also have a regular mailing list for general discussion.
This is fantastic. Thanks to the Google Code team :)
ReplyDeleteThis is great I love it so far. Hope doesn't get full of crummy codes that are not SEF.
ReplyDeleteHi,
ReplyDeleteRecent changes in wiki added page border and #wikimaincol css style with predefined width: 64em.
Since that moment our class diagrams don't fit the specified width. Just wonder is it possible to configure it or to switch to old wiki style we had before.
Could you please clarife this.
Thank you in advance.
Ayrat.