Hi, > > With an automated release process, we can release more often. > We can, but should we?
I think, we should release more often. Release early. Release often. And listen to your customers: (http://catb.org/~esr/writings/cathedral-bazaar/cathedral-bazaar/ar01s04.html). To release often, we need better tests and a automated release processes. Better tests, otherwise changes would be too risky. Automated release processes, otherwise a release takes too much time. > Think about Jackrabbit 1.4 and tell me how a better test suite would have > noticeably expedited the release? A good test suite should improve software quality and reduce the risk of changes. Automated release processes save time. Unfortunately both (writing tests and automating processes) is an investment and takes time. > change our releasing strategy to time-driven That's an option, but not really required. Most features can be split, and the first release will only contain a subset of the planned functionality. This helps getting feedback. What I mean is Agile software development (http://en.wikipedia.org/wiki/Agile_software_development). Regards, Thomas
