On Mon, Mar 29, 2010 at 11:03 AM, Bertrand Delacretaz <[email protected]> wrote: > Hi Nicolas, > > The trunk is supposed to be stable at all times, but we're not > religious about it so it can be broken from time to time (and whoever > broke it should fix it, hint, hint ;-)
Yeah, I know what software development usually is ... > > The best way to find out about the latest SVN revision that passed all > of our tests (which have a reasonably good coverage, at least for the > core things) is to look at our Hudson continuous integration builds. > > Looking at > http://hudson.zones.apache.org/hudson/view/Sling/job/sling-trunk-1.6/ > now, for example, shows that the latest build had a number of failed > tests, but build #348 was all green. I was ready to tell you to give more visibility to this hudson link, but saw that it is already mentionned on sling website. Anyway, I guess the informations provided in this mail would be of great interest to other sling users. > > The most important/most tested modules are those in the "bundles" > folder, the other folders contain extensions/samples/optional > components that might not be always stable. Yeah, i've already closed all the test* projects, as well as the *scala* which brings lots of compile issues. After having closed all those, there were no more issues. > > Hope this helps - we really should to a launchpad release soon, for > people like you who want to play with a stable release. I guess it could be more reassuring to work on so-called "stable" branches, at least for the on-site demos, even if it would more work for you when performing a release (since you would have to update some site pages (but I guess they use a sling instance with some good "variables"). -- Nicolas Delsaux
