Many tools fail to pass the recommendability threshold. There are two reasons why: poor capability or poor visibility.
Many tools garner consistent complaints from ThoughtWorkers about their lack of capability. (ThoughtWorkers being what they are, all tools, including the preferred set, get some complaints. Those behind the threshold get mostly complaints.)
(Link: MF Bliki: VersionControlTools)
Uncategorized
Codebase is developed in Ruby, using the Rails framework for the web application. In addition to this we have also developed our own libraries which power two of the most important parts of the system. Tripod is a library which provides SCM-agnositic access to repositories allowing us to easily interface with Git, Mercurial or Subversion repositories using a unified API. SCAM is our “source control access manager” and it interfaces directly with the Codebase database to control access to all repositories – regardless of the SCM, your request for access will pass through SCAM. We’ll post some blog entries with more details about our actual infrastructure in the next few weeks.
(Link: Codebase – Subversion hosting with complete project management – tickets, milestones.)
Uncategorized
Unlimited Repositories
Unlimited Trac Projects
Unlimited Users
Custom Domains
Custom Logos & Colors
SSL Secured
WebDAV Shared Drives
Scheduled Backups
2GB Storage
$1/GB Additional Storage
(Link: Repository Hosting – Subversion Hosting, Git Hosting and Trac Hosting)
Uncategorized
HTTP push/pull support
SSH push/pull support (with public key authentication)
Integrated flexible issue tracker
Per-repository wikis (backed by hg repositories)
Plenty of “services” for repositories, automatic issue resolving, web hooks, etc.
Email support (for both paid and free plans)
CNAME support, so you can keep the code on your own domain
Collaborate with other users easily
Source view with highlighting for many languages
Forks and Mercurial Queue (MQ) integration
A bunch of social aspects
RSS/Atom feeds for everything
Host static files on our CDN (Content Delivery Network)
(Link: bitbucket.org – Mercurial hosting)
Uncategorized
If you lack the courage to quit, then use Ant. Ant is the second best existing build tool for Java projects. Although inferior to Rake, Ant is still a great build tool. Ant is mature and stable, it is fast, and it comes with a rich library of tasks. Ant makes it possible (but not at all easy) to script rich, complex builds processes custom-tailored to your project.
So, write your own build tool, or else switch to Rake, or fight to switch to Rake, or quit and go some place where you can use Rake. And if all else fails, use Ant until you can find a new job somewhere else that uses Rake.
That’s it! Those are the only choices I can recommend! Because you never, ever, under any circumstances want to use Maven!
(Link: Java Build Tools: Ant vs. Maven)
Uncategorized
Table of Contents
* Feature Development
* Bug Fixes
* QA Branch Management
* Production Tagging
* Summary
* Notes
(Link: ReinH — A Git Workflow for Agile Teams)
Uncategorized
Created because we’d rather not use Maven. JavaGems provides gem hosting and gem creation for the JVM-based-language community. Instantly publish your gems and install them. Use the API to interact and find out more information about available gems. Become a contributor and enhance the site with your own changes.
(Link: javagems | awesome jvm gem hosting)
Uncategorized
Feature flags and flippers mean we don’t have to do merges, and that all code (no matter how far it is from being released) is integrated as soon as it is committed. Deploys become smaller and more frequent; this leads to bugs that are easier to fix, since we can catch them earlier and the amount of changed code is minimized.
This style of development isn’t all rainbows and sunshine. We have to restrict it to the development team because occasionally things go horribly wrong; it’s easy to imagine code that’s in development going awry and corrupting all your data. Also, after launching a feature, we have to go back in the code base and remove the old version (maintaining separate versions of all features on Flickr would be a nightmare). But overall, we find it helps us develop new features faster and with fewer bugs.
(Link: Flickr Developer Blog » Flipping Out)
Uncategorized
