|
WhatsNew
Announcements of the latest project hosting features
Welcome to the What's New page for project hosting on Google Code. Here you'll find descriptions of our latest improvements to our collaborative development environment. September 2009User ClonesAny user can visit any Mercurial repository and create a server-side user clone of that repository, without asking permission from the project owner. These personal user clones can be easily shared with other developers -- who also can make a clone of that clone. Learn More. Issue Tracker Data APIThe Issue Tracker Data API is a Google Data API that you can use to programmatically add new issues, make changes to existing issues, or simply access issues for your open source project. Learn More. August 2009Multiple Repository Support for MercurialMercurial Projects can now have multiple repositories. These new project repositories can be added through the Source sub-tab under the Administer tabs. Project repositories can be clones of the original default repository. July 2009Commit emails with or without diffsCommit notification emails can now include diff output or not. Project owners can control that via a checkbox on the Source subtab of the Administer tab. Subversion upgradedGoogle Code's subversion server has been upgraded from version 1.5 to 1.6. People subtab and configurable permissionsThe new "People" subtab on each project home page allows project owners and members to easily document what each project member's duties are. A new "contributor" role and the ability to grant permissions gives project owners a lot more flexibility when they need it. Learn more. May 2009Commit log commandsIt is now possible to update an issue via a commit log message. For example, you can commit a code change that fixes a defect, and write "(fixes issue 123456)" and the status value of that issue will be set to "Fixed". Learn more. Keyboard shortcutsKeyboard shortcuts are now available in the issue tracker. Type "?" to see a list of the shortcuts. Mercurial version control systemMercurial support is now available for general use. You can create a project using Mercurial, or convert an existing SVN repository. Our MercurialStatus page has a list of known issues. April 2009Shift-click to select multiple issuesIn the issue list, project owners and committers can now select a range of issues by clicking one checkbox and then shift-clicking on another checkbox. All the issues between the two checkboxes will be selected or unselected. After that, the "Bulk edit..." item in the "Actions..." menu can be used to edit all those issues at once. Privacy option for user updatesIn the world of open source, everyone's contributions are available for everyone else to see. Our user updates feature makes it easy to see exactly what any other developer has been doing on our site. However, some users prefer that their contributions be seen only within the context of each project, so we have added a user setting to disable visibility of user updates. Sign in and see your settings page for details. WikiWords now auto-linked in all toolsIf you mention the name of one of your wiki pages using a WikiWord in any issue, commit log message, or code review, we will automatically link to that wiki page. March 2009Customizable project logosAs announced in our blog post, project owners can now upload a custom project logo to be displayed at the top of every page in the project. The Google-sponsored projects are keeping the "Google Code" logo. All the other projects that we host have a great new default logo with a "g" on a monitor. Soft-delete issues and issue attachmentsWhen you're done with an issue, you should just set its status to Fixed or some other closed status value. But, sometimes you really want to delete an issue. For example, if it contains a password that is hard to change. Now project owners can delete the whole issue via the "More actions..." menu on the issue comment form. Individual attachments can also be deleted. Self-serve repository resetsVersion control is all about maintaining history. If you want to make changes, or even start with a whole new directory structure, you can do that with regular svn commands. However, sometimes you need to reset your repository history so that you can 'svnsync' content from another svn server. You can now do that a little more easily without needing to file a support request. Project creation limit raisedWe limit the rate at which users can create projects, and we also have a lifetime limit on the number of projects created by each account. These limits exist to help us catch abuse and some types of well-intentioned but misguided use. Most users never reach these limits, but some do. Now that we have more ways to deal with abuse, we have increased the lifetime project creation limit to 25. However, please use each project that you create wisely and seriously. For example, please don't repeatedly create a new project as a way to give a fresh start to an existing project, instead 'svn rm' files and close old issues. February 2009"My projects" drop-down for quick navigationNow it's easy to navigate to projects that you are a member of, or that you have starred. Just click on the "My projects" drop-down menu in the far upper right of any project hosting page. Track updates by project or developerTracking open source projects and other developers is now as easy as starring a project or a developer profile. All updates from starred projects and developers can be tracked by looking at the "Updates" tab on your profile page. For the details, see our blog post. Subversion upgraded to 1.5The Subversion component of Google Code Project Hosting has been upgraded to version 1.5. What does this mean to users? If you're using a Subversion 1.5 client, you can now take advantage of Subversion's improved "merge tracking" feature to manage branches. See our blog post for more information. January 2009Post commit web hooksProject owners can now trigger an HTTP POST to a URL of their choice after each commit to version control. This enables users to write POST handlers that kick off builds, tests, notifications, or anything else that they can imagine. See PostCommitWebHooks for details. New wiki featuresYou can now embed videos into wiki pages, including the project homepage. See WikiSyntax for details. Better syntax highlightingWe upgraded to the latest version of google-code-prettify, improving language detection and adding support in the source browser for highlighting Haskell, LISP, CSS, Visual Basic, and our own wiki syntax. Issue filter rulesMuch like message filter rules in an email client, project owners can now set up issue filter rules. These rules look for certain labels on an issue, and then apply default values for the issue owner or status, or add labels or CC addresses. Unlike email filter rules, issue filter rules are applied after every issue change, not just when new issues are entered. And, the field values that are derived in filter rules are always default values: they never overwrite values that are explicitly set on the issue. For example, default issue owners can be defined based on Component-* labels. December 2008More quotaWe're increasing the maximum file sizes from 20MB to 40MB, Subversion quotas from 100MB to 1GB, and download quotas from 100MB to 2GB. New web page headerThe top of each project hosting web page is now a little cleaner and more consistent with other Google pages. -1 on "+1"sAn issue tracker is a serious tool for tracking serious work. When users chime in on a hot issue with a large number of "+1" comments to show their support for the issue, they are actually distracting and annoying the developers who should be working on resolving the issue, as well as other users. We provide a star icon for users to express their interest in an issue without triggering any notification emails, but some users are still in the bad habit of posting "+1" comments. Now we make the star widget easier for average users to find right at the point where they might be tempted to add a "+1" comment. And, we automatically block "+1" comments that don't add other value. November 2008Wiki improvementsWe increased the power of our wiki in three ways:
Autolinking of URLs in issue and revision textNow if you mention a URL in the text of an issue comment or a subversion commit log message, that URL is automatically shown as a hyperlink. More compact issue notification emailsThe format of our issue notification emails has changed to now put the metadata at the top. The summary still includes the issue number, project name, and issue summary. Moving the metadata up improves the snippets shown in Gmail and other mail clients. Artifact sorting by usernameA long-standing problem with sorting issues, downloads, and wiki pages has been fixed. Previously these items did not sort properly by usernames, such as the issue "owner" or file "uploadedby" columns. Also, new issue list columns are available for the issue reporter and Cc list. To see all the built-in columns, click the "..." table header in any list view. Issue blocking and mergingIn a small project, only a few people are involved, and they become pretty familiar with the issues in their issue tracker. But, now that we are hosting more large projects, we are adding the option to formalize more of what small teams know implicitly. Users always had the ability to document in plan language that one issue could not be worked on until another issue was completed, and the issue reference in that text becomes a hyperlink to the other issue. Now, issues can be explicitly marked as blocked on other issues. Changing issue A to make it blocked on issue B adds hyperlinks in both directions between the two issues, and adds a comment to issue B at the same time that issue A is updated. Users could always close an issue as a duplicate and mention the original issue in the comment. Now, if the status field if set to Duplicate, users also have the option to merge the duplicate issue with the original issue. Merging adds all unique stars and Cc values to the original issue, and automatically adds a comment to the original issue. Starred projectsUsers can now star projects that you are interested in so that you can easily revisit them. On the summary page of any project, just click the star icon in the right-hand column. The list of projects that you have starred is shown on your profile page. October 2008Onward or upward?Our issue tracker UI was designed with tabbed browsing in mind. For example, if you want to triage several issues, you can middle-mouse click on links in the issue list to open several issues in separate browser tabs, then step through each of them rapidly. Now there is another way to rapidly step through issues in your project using just one browser tab. When you submit an issue, you can now specify whether you would like to go up to the issue list, stay on the same issue, or go to the next issue in the list. Assigned code reviewsWe love to see developers doing code reviews because it is one of the best ways to improve quality and help everyone on your team stay in-touch with changes as they are made. Since July we've offered a very easy-to-use code review tool that allows anyone to comment on any line of any revision. Now, we are adding assigned reviews: these are issues labeled Type-Review that request that a project member review code that has been committed to a branch. These issues can be created through the Web !UI or through special syntax in a commit log message. The issues are listed in the issue tracker, as well as at the top of the recent changes page. Each issue links to a branch review page that summarizes all the changes made on that branch. Once a review is done, its issue can be closed. See the CodeReviews page for more information. Gadgets in, gadgets outYou can now place any gadget in a wiki page in your project. That makes it possible to show video, charts, and stats. And, you can now put gadgets with info about your project onto your iGoogle page (or any other gadget container). See our blog post for more details. Project updatesThe new "Updates" subtab shows a summary of recent project activity, including commits and issue changes. It's a great way to understand how active a project is, and who did what. See our blog post for more information. August 2008Issue templatesProject owners can now define a set of issue templates that users can choose from when entering new issues. Each template has initial values for the issue summary, description, owner, status, and labels. For example, the template for a user defect report asks for different information than the template for an enhancement request. July 2008Source code review toolsCode reviews can be a very effective way to improve your code quality, and keep your project members involved in the changes that might affect their work. We now offer a source code review tool that is integrated with Google Code's project hosting. Reviewing code in your project is simple: browse any source file or diff, double click on a source line to add comments, then publish your comments along with a general comment and score for the revision. You can see code reviews in action on the code.google.com support project. For complete documentation, see the CodeReviews wiki page. Project feedsWe now have Atom feed available for you to track issues, downloads, Subversion changes, and Wiki updates. For a list of all feeds in a given project, click the Project Feeds link in the right-hand column of the project home page. June 2008Browse history of files even if they were moved or copiedVersion control is all about access, changes, and history. When a source code file is moved or copied from one location to another, subversion tracks the old pathname and the new one. The normal svn log command shows you the entire past history of a file, even if it has been moved or copied over time. Now we present that same information in the web interface for source code browsing. The revision navigation links now offer links to previous versions of the file, even if those previous versions were at a different previous location. And, when viewing the list of all changes to a given file, the list is divided into sections for each pathname that the file has had over time. For example, the Hello.java in GWT 1.5 came straight from trunk, whereas some other files have been moved a few times. May 2008Atom feeds for issue changes and commitsDevelopers need to stay aware of changes happening in their projects and projects that they depend on. Usually that means a very full email inbox and lots of automated message filtering. But, there is a better way. We now offer atom feeds for the most recent svn commits and issue changes in a project. When you visit the source code change list page or the issue list page, click the feed icon in your browser location bar to subscribe to the feed. For example, here is a feed of issue changes in the Gears project. Downloadable issue list .csv fileDo you need to do something with your issue data that our issue tracker just can't do? For example, you might like to produce a bar chart of issues assigned to each developer. Now we help you do that by allowing you to download a comma-separated-value file that has the same information you see in the issue list. Just click the "CSV" link at the bottom of the issue list. With most operating systems and browsers, that will take you straight to a spreadsheet application. Source browsing file diff now includes SVN Property diffsThe title says it all. If you changed file properties in an svn commit, you will now see the old and new values of those properties on the diff page. Issue bulk editingIt's time for spring cleaning of the issues in your project: organize them by milestone, organize them by component, or assign them all to your project members. Doing that just got a lot easier because we now offer issue bulk editing. In the issue list, signed-in project owners and committers can check the checkboxes for several issues on one page and then use the "Actions..." drop-down menu at the top of the list to select "Bulk edit...". The bulk edit page allows you to enter one comment that will be appended to all the selected issues. You can set the status or owner of all the issues by filling in those fields. And, you can add or remove labels by entering the label name, or the label name proceeded by a minus-sign. Autolinking in svn commit log messagesNow when you mention issues or other revisions in your subversion commit log messages, the text will automatically be linked to the detail page for those artifacts. Just as with autolinked references in issues and wiki pages, the syntax is issue 123 or issue #123 for issues, and r123 for revisions. If the linked issue has been closed, it will appear crossed-out. In most browsers, hovering your mouse over the issue link displays the one-line summary of the issue. March 2008Source code browsing improvementsWe've been working on improving the source code browsing tool. Intra-line diffs now make it much easier to notice exactly which characters changed on each line. We've also improved the speed of the tool and made it more robust for projects that have large source trees. Jan 2008Source code browsing toolThe great thing about open source is that anyone can see the source code. Well, that just got a lot easier on Google Code. Unlike many of the existing source code browsing tools, ours allows you to quickly drill down into multiple levels of directories. And, we built in the assumption that you want to get straight to the source, even though file metadata is still easily accessible on the same page. Syntax highlight makes your source code easier to read, and our syntax highlighting works without bloating the HTML markup. Source code is not just about code, it is also about how and why the code has changed over time. So, the "Changes" subtab gives you a concise list of all revisions to your source code repository, and each revision can display the log message and show diffs. We also made it easy to flip through revisions or diffs of a given file. To browse the source code of any project, just click the "Source" tab, and then the "Browse" subtab. If you have already memorized the instructions for how to check out source code, you might want to change your personal settings so that the "Browse" subtab is shown by default. Enjoy! Dec 2007Replace a project tab with a wiki pageTo keep our project hosting service simple and easy to use, we only offer one version control system, one wiki, one download system, and one issue tracker. These tools are designed to be flexible to fit the needs and best practices of most small- to medium-sized open source projects. However, we know that one size does not fit all: some projects have existing tools hosted elsewhere, or simply prefer to use other google products or tools hosted on another site. Now project owners can write a simple wiki page giving end-users instructions on how to get to your external tool, and then replace the corresponding project tab with that wiki page. That wiki page can link to the other site, or you can customize the landing pages for our hosted tools by linking to specific pages within your own project. And, undesired project tabs can be hidden from users, for example a documentation project you might not need the Downloads tab. Sept 2007Use any Google Account, not just Gmail accountsPreviously, we required that all project members use Gmail accounts. That restriction helped us manage certain types of spam, but it inconvenienced many legitimate users as well. We've made improvements to the way that we manage the site, and can now pass on the convenience to users. Project members can now be specified with the full email address of any Google Account. July 2007Easier way to get to project home pagesShorter, simpler URLs look better and are easier to remember. When developers put their heart into a project they want it to make the best first impression, which is often in the form of a URL in an email or on another web page. We've always valued clean URLs for project home pages, and have used http://code.google.com/p/PROJECTNAME since we started offering project hosting. Now, projects can also be reached via an even cleaner URL: http://PROJECTNAME.googlecode.com. Grid view of issuesWhen projects start, they have a few defect reports and requests for enhancements. A simple list of issues is good enough: a developer picks some issue, solves it, and closes it. But, as projects grow in scope, the number of open issues can grow and it can be hard to know which issues to work on first. Sorting and filtering the list can help developers understand the set of open issues, but now there is an easier way. The grid view of issues uses rows and columns to lay out issues according to any two attributes. For example, support issues by milestone and priority. The grid view can also easily show the number of open issues associated with each component, or the number of issues owned by each project member. Improvements to list viewsProject artifacts in your project workspace have a variety of built-in attributes, and can be labeled with Key-Value pairs as user-defined attributes. These attributes can be used as column headings in any list view as a way to bring out and organize information according to the structure that makes the most sense for that project. Several improvements were made to the list views to help project owners use the power of user-defined attributes more fully:
Clarification of the purpose of starsWhen a user clicks the star icon on an issue, he or she is indicating an interest in that issue. We make it easy for users to search the issues that they have starred. Also, users will receive email notification of changes to issues that they have starred. And, everyone who visits the project can see the number of users who have starred each issue. We have clarified the email notification aspect of stars by adding tool-tips to the stars and a reminder that starring causes notification of changes to the issue detail page. Issue tracker commentsSometimes a user leaves a comment on an issue that is irrelevant or which contains information like a password that should not be displayed to other users. It can happen to any of us if we accidentally comment on the wrong issue or paste in a big chunk of text. Now, those unwanted comments can be deleted or undeleted by the user who entered them, or by the project owner. Wiki page commentsWiki's are community-owned knowledge-bases: they should allow contributions from anyone who notices a problem or wants to add valuable information, but they can also lose some of their value if they are vandalized, if they become disorganized, or if incorrect information is added. The project wiki feature that we offer now strikes a balance between these trade-offs by allowing any logged in user to append a comment to the wiki pages. Project members may then review the comments and choose to:
Google Analytics integrationOpen source projects are all about collaboration between project members and the users of the software being developed. To provide the most useful software to your users, you might want to know simply how many potential users have visited your project workspace, which countries they come from, which browsers they use, and which of your wiki pages they have viewed. Now all those questions can be answered. Project owners may simply sign up for Google Analytics and enter an analytics profile number into the project admin page. Tracking data can be viewed on the Google Analytics site about 24 hours later. Bug fixesWe continue to work hard to improve the quality and reliability of the project hosting service by finding and fixing defects. Please check our current support issues, star the issues that are most important to you, and report and new defects that you find. April 2007Autolinking of issuesSoftware development is all about putting ideas into working software. It turns out that the software created has a lot of interconnections, and the process of creating that software requires even more connections, dependencies, and references between all the information produced as part of the project. Google code hosting has always offered the developers the ability to link web pages in subversion, and wiki pages. We also encourage the use of Google groups or other mailing list archives that make past messages accessible via a link. And, every issue has had a clear URL that can be linked to, but only by specifying the full link. Now, you can easily and automatically link to any issue from another issue comment or from a wiki page. Just write "issue N" or "issue #N" and it will be linked to the corresponding issue in your project. If that issue is closed, the link text will be crossed out. Moving your mouse over the link shows the summary of the issue. The content on this page created by Google is licensed under the Creative Commons Attribution 3.0 License. User-generated content is not included in this license. |
Sign in to add a comment
The issue tracker is already awesome, thanks for working to make it even better!
Issue linking is nice. Waiting for the similar functionality for SVN to navigate changes and track history conveniently.
Grid view of issues is very useful. Nice design. Looking forward to being able to save a default grid view.
The grid view reminds me of Mingle. Next step is to support drag and drop to set the properties.
I would like to export the grid to a Google Document Spreadsheets. The service is very easy to use.I like it very much!
Easier way to get to project home pages... Great detail. Thanks!
Please, add issue deleter.
It would be nice to have SVN statistics (lines of code, activity, developers, etc.) similar to what statsvn does.
++ to what pavelgj suggested, svn statistics would be great.
Hi! Thanks google for this stuff. So great :) In some way I'm thinking to something like a mini board (forum), really light and minimal to allow a project members to discuss together in public (rather than using comments)
Thanks!
For those looking for Git, I highly recommend setting up an external git repo for publishing to, and using git-svn dcommit to push changes to google code. It's not perfect, but it definitely seems to allow proper git development and a way to publish changes back into the Google Code repos.
Add feed to issues and svn commits! :-D
Those looking for git:
Look here:
http://en.wikipedia.org/wiki/Comparison_of_free_software_hosting_facilities
and use some of those free git hostings for the repository, and google code for everything else.
Can i deny access to my project? i just want certain perople to read or wite on the code??
nasserdw: We only host open source projects. That means that anyone can always read your code. Only project owners or members can write changes to your code.
I just want to receive emails when SOMEBODY ELSE add new issue, change the wiki, update SVN. If the system detects it's me who did it, then it shoudn't send me email notification.
The tracker and Wiki are so cool. If only it supported gi... - wait, no! - Mercurial! (And git, of course.)
Thanks for all the support you give us developers!
Ability to specify page title for home page, please, to help with SEO :) (results are not very descriptive when you search for, say, calendar date select)
Better subversion web interface. History? Diffs? Linking to specific versions?
It would be perfect, if Google-Code would provide nightly snapshots of the svn-repository. So testers could simply download them, without having to install an svn-client first.
Adding the program of the day feature which is to show in a very clear area on google project site the most downloaded program for the day before
add issue deleter
Is there a way to create a project as an subproject of another project?
Let's say I make a plugin/theme for another project hosted on google code?
matthijs.groen: The way to do that now would be to use links from your project home page to the related project. However, the projects would still be independent in terms of members, repository, issues, etc.
Could we have RSS feeds for issues ?
yea rss issues
Hello, I got this e-mail today "Your project notifications generated too many emails to send individually. Here are the subject lines of the emails you would have received: ". Followed by a bunch of subjects (11 of them). I however do NOT want this feature enabled, because I'd like to watch the issues tracking activity. It this planned to allow disabling it? Thanks.
There are lots of requests on this page for a web based tool to view author commits or browse the repository. Check out: http://www.subversionreports.org/ and http://subversionreports.googlecode.com/
With http://www.subversionreports.org/ you can browse any Google code svn repository.
would it be possible to allow anoymous submissions to project issue tracking?
jake.pezaro: We will most likely never allow any unauthenticated contributions of any kind. Allowing that would open the door to automated spam that we would have a hard time cleaning up.
dwoogle: deprecate the old download and upload a new file with a new name.
There is purposely no way to change the contents of a file without changing the name, because that is a poor software development practice that makes life harder on people who use the software you release.
How do I upload my application to the code.google.com project that I created.
sharma.deepak83: basic support questions should be sent to the google-code-hosting@googlegroups.com mailing list.
As for how you upload your application, if you mean putting your source code into Subversion, then you would use 'svn import'. See the Subversion documentation for more info.
If you mean that you want to upload an executable file with your compiled source code, you would click the "Downloads" tab, and then click "New Download".
Would it be possible to make the grid view optionally the default? At least on a per user basis.
If you would like RSS feeds for for your Google Code SVN, check out this site: http://subtlety.errtheblog.com/ It's a great way to stay on top of any changes, without having to use e-mail. I hope that helps someone.
notification by jabber, not only by e-mail, would be a neat feature REALLY cool would be if wiki-pages could be marked as publicly-editable (by entering a captcha) or even more sophisticated wiki-control. The wiki could be more feature-rich, personally I miss an optional Table-of-Contents at the top of each page. good work, keep up
Please add color syntax formating in svn viewing.
From the changelong for September'07: Project owners and members can now be specified with the full email address of any Google Account.
I am hoping to use my Google Apps account. But I get error if I add my Google Apps email address as 'project members'. Is it supported? If not, will it be in future?
Hi! Is it possible to wire the issue tracker with mylyne eclipse plugin (of course everything is possible, but I mean "did you plan to provide one?")? Thanks a lot for your great tools!
Hi, it will be very useful if we have something to bookmark a project, something like "track this project" where I can see the list of projects I'm interested in, and yes RSS feed will be very useful
it would be nice if picture attachments in the issue tracker that are not too large are displayed directly, and if not, sent at request with the correct mimetype.
When i click download on a attached png file, it is offered for download, but with the application/octet-stream MIME-Type, instead of image/png, so I have to select an application to open it manually.
The ability of turning on/off the anonymous SVN access would be great, especially in the early phases of a project, when you don't want to make the code base available to everyone but you still want to use SVN.
Yea, what all does it entail. Is bugtraq supported?
i want updates for foundry items
Please explain what's the "Locales:" and how to use that.
tell me whats a good tranlator for java game launguage
re the Locales thing. It will be great once we can start supplying multi-lingual wiki pages for our projects. Any ETA or guide as to how to utilize it?
howdy, my expertise and research relay around developing a publishing platforms. Any group out there involve into CMS/Semantic Web development/Architect?
i wish to be member of Google..so that i need some project through which i can develop my self please guide me for my future ,now i am pursuing mca from Bangalore
I keep track of projects of my interest (in various hosting places like CodePlex?, SourceForge?, etc) via RSS, and use Google Reader to do so. But apparently cannot do this for Google Code!!! As there is no RSS feed for updated to single projects.
Thanks. I am gonna use it in http://www.forumistan.net
At present I use APlus as my web hosting. I have an email from Netcraft that says that Google is offering free hosting. Where and how do I sign up. RSVP Peter
Yeah; RSS feeds for commit history would be great!
Replace tab with wiki page is great, but is there any plans about add new tab from wiki page? I have few very small projects and there is no need to get separate project hosting for each of them, so I am using one project hosting for all of them, and add tabs for each subproject will be great for me and anyone else who have few projects on one project hosting. Thanx!
I would like to have RSS feeds for svn changes and issues. <3
Why not make stack for each user to add projects in it.
Hi,
Would Google introduce function for end user such as ability to track a package like sourceforge? Where I can set up if I want to know when there is a new release/commit of the code for a particular package and also ability to bookmark it so that I can easily find it later.
Regards
RSS feeds for changes & issues would finish it completely for me. Thanks.
+1 for thomas.bonte
RSS Feeds for changes, issues and wiki, could be usefull
why there isn't a google code ticket api?
The source code browser is useless for documents under source code control because it has no option to wrap long lines.
Google make me up to now to became professional I am new to WiKi? I believe that this also good for me to develop
It would be cool if somebody could fix the http 502 server error which pops up if one tries to delete comments...
It would be a really nice feature if you implemented the seamless install badge for projects written in Adobe Air, so that the distribution process would become even more seamless.
It would be extremely useful to be able to ignore whitespace in a diff. At the least color them differently. Currently diffs are unhelpful in a project where developers are using different tools and are not even aware they are committing large number of whitespace changes.
I would love to be able to "watch" a project -- receive updates on revisions, etc.
It would be cool to have a discussion forum embedded into each project, or the ability to make seperate issues pages (for example, you can have one for compatability issues, and one for programming issues).
It would be great if a continues build service will be added.
Please, send your bug reports and feature requests about Google Code to the issue tracker -> http://code.google.com/p/support/issues/list not as comments here.
Is the feature described under Onward or Upward? (October 2008) available only for project members? I can't find it anywhere.
Does anyone have a URL or a screenshot where that feature appears?
alexkon@gmail.com
This is just a small nitpick, but is it possible for you guys to add a link to the SVN repositories as opposed to just printing the link. For example: http://svn...read-only/
SVN is accessible as a URL in the browser, I am surprised you guys didn't add the href tag to make it browsable.
berlin.brown: We don't link that particular URL because that is a command-line for people to copy and paste, and linking the text can make it harder for people to select it with the mouse.
The main way to browse the source code is to use the "Browse" subtab. We do have direct links to the raw repository URLs from the individual file pages.
jrobbins
Thanks for the response and as a developer, I know that everything is intentional. Did you ever consider an additional browseable URL. Some like the basic plain text output provided by SVN. The ajaxy 'browse' is good too, but sometimes basic work as well.
why don't you add some statistics to the googlecode page like http://www.ohloh.net does, with top committers, etc..
I indeed miss something like statsvn (http://www.statsvn.org/)
this isn't the place to report bugs or request features. Use the bugtracker in the 'support' project.
This page is getting too long. Google Code should have its own issue tracker.
These are the issues/bugs I wish to enter for Google Code Tracker: 1. As mentioned, Google Code should have its own issue tracker.
2. When viewing list of issues, issue tracker lets you view ~200 issues at a page. To get to issue 4010, you have to click and wait for browser response 20 times.
How about applying some good'ol google technology - the listing should be have a row of links to pages like the ones you see at the bottom of an igoogle search page. So that you could have random rather than sequential access to the page you wish to see.
Actually it's 1oo issues per page, so to get to issue 4010, I need to click next-page and wait for browser 40 times.
@BlessedGeek?: Google Code DOES have its own issue tracker. http://code.google.com/p/support/issues/list
BlessedGeek?: usually you would do a search to narrow down what you are looking for rather than page through all issues. However, if you do want to see a really long list on one page, you can add num=500 to the end of the URL to see 500 per page.
Can you add google ads to a project hosted here?
What wouldn't you offer (simple) website development like Yahoo does?