Looking back at Intland in 2009
2009 has been a busy year for Intland. Lots enhancements in our products, lots of awesome customers wordwide, lots of valueable feedback from the community, and lots of exciting changes in the collaboration space.
Let's see the most important events along our 2009 timeline:
And how about 2010?
Please wait a little for our next blog post, coming soon.
Finally
Thank you so much for your support and in-sights in 2009, you are an AWESOME community!
Read the full article
At Last! codeBeamer Managed Repository 1.0 Released
This is a fresh and tasty tool for anyone working with Subversion, Mercurial and Git or even with all the three at the same time! Creating and deleting repositories, and setting up access control ("who can read and write what") is usually a major maintenance issue that developers usually hate to solve, as it is boring and inherently error-prone. In other words, our value proposition is dead simple: MR will help you to spend your valueable time rather with coding, not hacking around in SSH and ACL config files.
Feature highlights in a nutshell:
- Starts and close projects and repositories in just seconds
- Project-, group-, and role-based administration across multiple repositories
- ACL on directory level
- SSH authentication
- Lightweight wiki, issue tracking and project management facilities
- Web based
- Remote API
Best news: it is completely free, and it never expires.
Visit the codeBeamer Managed Repository home page for more information, screenshots and downloads.
Watch the 2-minute guided introductory video
Intland now on Mercurial
Avid readers of our blog posts and users of codeBeamer 5.4 might already know that we are big believers in Distributed Revision Control. This paradigm will be a major driving force in our future product development. Right now, we are in the midst of migrating our internal product development from Subversion to Mercurial. In other words, starting this week our operation relies on Mercurial, one of the most popular Distributed Version Control Systems (DVCS). At the same time, we are reshaping our internal development processes to comply this.
"If you're so sure that DVCS is a better way of team working, why did it take so long to change?", you might want to ask.
Read the full article
Intland now on Mercurial - Part 2: Transforming our tool set
This blog post is a sequel to our previous one titled Intland now on Mercurial. This time we write about what challenges we faced regarding the tools our developers use in their daily work.
In the server side
In the server side, we eat our own dogfood: since the very beginning, our primary collaboration tool when developing codeBeamer is codeBeamer itself. It has already been a brilliant tool to support working with Subversion since the first versions, but to be able to change to a coffee shop style workflow, codeBeamer needed several enhancements to add.
Read the full article
Intland now on Mercurial - Part 3: Giving new momentum to the Eclipse Mercurial Plugin
This blog post is a sequel to Intland now on Mercurial and Transforming our tool set.
As written in the most recent post of this series, we found that quite some features important for us were missing from the latest version of the Eclipse Mercurial Plugin. We really wanted to move from Subversion to Mercurial, but we decided that at that point we could't do it without major productivity losses. We also realized that we couldn't wait for all improvements to be developed and tested by the community. Hence, several weeks ago, Intland Software decided to dedicate a developer to the Mercurial Eclipse plugin project. To put it simply, his task is to complete the most important missing features, and to make sure that the plugin would not be a blocker for our team anymore.
Read the full article
Enterprise mashups with codeBeamer
This post is written by a guest writer, G. Hussain Chinoy of Bespoke Systems.
Hussain is writing about his experience building an awesome timeline mash-up.
His app pulls out events from Google Calendars and issues from codeBeamer's super-elastic trackers, and visualizes them along a SIMILE timeline. What makes it even more interesting from technical perspective is the mix of technologies involved: .NET in the serverside, heavy javascript magic in the clientside, Google Calendar running in the cloud, and codeBeamer running in a Java servlet container and exposing its .NET remote API. The right tool for the right job.
We are incredibly appreciative of the efforts you put into projects like this. We will be doing whatever we can to support them, and would love to see more. Do you have questions? Comments? Something to show for the codeBeamer community? Just tweet us at @intland, and we will get back to you immediately.
Read the full article
Interesting links
Efficient team working is our passion, we love to practice it, to learn about it and to chat about it. Here is a selection of interesting news from the
collaboration space, that keep us excited. We hope these might be interesting for you as well.
git ready - is a geat collection of tips to help you get started with the Git Distributed Version Control System. "Learn Git one commit at a time!"
Nexus One - is the first real Google branded mobile device, announced in the first days of the new year. The war between Nexus One (more precisely, the whole Android platform), the Apple iPhone and the netbooks might easily reshape the way we collaborate, making it more mobile and less location dependent.
Mercurial: The Definitive Guide - written by Bryan O'Sullivan, the number one book for the Mercurial Distributed Version Control System is available online. Do NOT miss it.
Winners of the third annual Crunchies Awards - as you see, (lightweight) collaboration, real-time, distributed teams, and cloud computing were hot in 2009. For Intland, these remain leading trends in 2010 as well! Read our blog and become a fan of codeBeamer at Facebook if you want to follow where we are headed, and what we are currently working on.
|
