Ledge & Coral projects have been stuck with 0.x releases for a very long time. This does not reflect on the actual status of this software which is deployed in a few production, large scale systems for several years now.
Here's my plans regarding releases and versions of Ledge & Coral in near future:
- next releases of Ledge & Coral will be versioned 1.0.0
- those releases will coincide with release of Cyklotron 2.5
- releases 1.0.0 will be not contain significant changes over current 0.3.15 / 0.1.11 releases
- unreleased versions currently in Jira will be dropped. issues with affects set to any of those versions will be pushed down to last released version, those with fix for set to any of those versions will get unscheduled
- the above means that all the open issues will end up as unscheduled for now. I'll create 1.0.x versions as I go and include issues that are actually needed / incidentally done in time for the upcoming release
- I'm going to drop the notion of documentation / testing centered releases - this concept did not work. I'll try to include some of these tasks in regular releases
- I'll fill in component information in Jira to give a better overview what's happening
- generally, I'm going to file LEDGE/CORAL issues whenever I do something in those projects - this way we'll have usable changelogs
- release cycles of Ledge & Coral will remain tied to Cyklotron releases for now. There's no compelling reason to do otherwise at this point
- all modules within each of the projects will go on the same release schedule for now. This is a bit superfluous because we re release much code with no changes at all, but it's easier to maintain. We can consider splitting up ledge modules into individual components to give them separate schedules later.
I have successfully installed Atlassian Bamboo and hooked it up with Crowd, thus completing Atlassian goodies install / upgrade cycle.
I tried giving it a spin, but unfortunately it turned out to be unusable:
- It allows checking out only one SCM module per build - in all ObjectLedge projects parent POM is held in a separate module: BAM-1015
- When the former is fixed, we probably still won't be able to build because Maven builder guesses the location of project.xml, and with multiple modules in the build directory chances are it will guess wrong: BAM-2156
- At this point dependencies among plans need to be maintained by hand. For 20+ module setup this is simply not manageable. I refuse to use Bamboo until dependencies are automatically inferred from maven POMs: BAM-230
- Bamboo apparently does perform dependency order based build queue ordering: BAM-1393 as we know from our previous experiences with DamageControl this leads to hailstorm of bogus failed builds
I've signed up as watcher on the bugs mentioned above. I'll be watching Bamboo progress - maybe it'll become a viable option eventually.
Welcome back.
Despite few years silence on the web, objectledge.org project is alive and doing well. Looking at the change logs there has been significant activity in the past months. Now we are also trying to boost our information sharing tools & policies.
Recently objectledge.org infrastructure has been upgraded & expanded thanks to Atlassians's Open Source Community Loyalty program.
Currently we are running the following Atlassian apps:
- Jira 3.12.1 http://objectledge.org/jira
- Confluence 2.7 http://objectledge.org/confluence
- Fisheye 1.4.2 http://objectledge.org/fisheye
- Crucible 1.2.2 http://objectledge.org/fisheye/cru
- Crowd 1.2.2 http://objectledge.org/crowd
- Crowd OpenId 1.2.2 http://objectledge.org/crowd-id
Jira, Confluence & Crucible authentication & user management has been wired to Crowd. You can sign up for objectledge.org account using Jira.
Upcoming infrastructure work:
- Atlassian Bamboo instalation http://www.atlassian.com/software/bamboo/
- Bringing back Maven generated reports for all objectledge.org projects & modules
- Jira & Confluence config tweaks, plugin installs
- Jira & Confluence house cleaning (permissions & notification schemes)
- CVS -> SVN migration before starting Cyklotron 2.6 development cycle