Hi all commiters, I'm writing to ask what's the status of your build fixes, Mark? I notice they haven't been even merged yet.
If we step back here for a minute, it's clear we're not adhering to the very Guidelines for Committing we approved in a vote: "No broken builds on the Master Branch, ever." "A broken build is a matter of urgency. Mistakes happen, but if you break the build, please make sure to fix it ASAP or temporarily rollback your changes until you can resolve the issues." Yet the pull request #40 caused not one, but two separate issues with building (one of them is fixed now) and we didn't roll back the commit when we found out about them. Bamboo builds continue to fail, rendering them useless when we should rely on them as our safety net, particularly at this time before the release. I don't mean to blame you, Mark, on the contrary, thank you for your attempts to fix this issue. It just needs to be led to a successfull conclusion. So let me ask all of us. What steps do we need to do to fix the failing Bamboo tests? I imagine it will be something like: 1) merge pull request services #4 and #5 2) build and upload to Maven Central 3) ? Remember, we declared this is a matter of urgency. Regards, ~~helix84 ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
