Hi Tim, 2009/6/19 Tim Moore <tmo...@atlassian.com>: > I don't trust humans :-) If people are finding problems with the builds that > aren't caught by automated tests, it would be nice if they at least file > bugs to improve the test suite (if not actually make the improvements
IMHO problems will be not in the build or automatic tests but mainly in the code functionality and the stability of the generated artifacts. A typical developer day is to work, to commit, to improve, to recommit, to reimprove etc. If Hudson starts and deploys automatic snapshots on r.a.o between these commits, the build will be fine but the artifacts could be not usable. In Maven land, we decided that it is the responsibility of the devs to deploy snapshots to r.a.o only when the judge the artifacts are stable. > It may also be worthwhile to consider more frequent tagged releases... call > them betas, or milestones... the point is that it will give people a more > stable version to depend on than a snapshot, and a more current version than > 1.0-incubating. I'm not sure what Apache rules are, but I would hope that as > long as the release isn't announced or packaged up for download then it > shouldn't require a vote to release a monthly or biweekly milestone. Since Shindig is in the incubator, it could be hard to have a consensus each month (see the effort to release 1.0...) We are using Hudson to have snapshots but we could certainly deploy them to r.a.o, maybe based on a regular timeline. Cheers, Vincent
