Archives for Matthew Watson

Making the Switch to DVCS: The FishEye Teams move from Subversion to DVCS

The Tool is the Easy Part - What about the Processes? The FishEye team was the first team at Atlassian to make the switch to DVCS, and while some Atlassians had previous DVCS experience, quite a few had not yet used it in the workplace with a medium-size team of developers before. We looked for help around the web, but there wasn't a lot of people sharing their experiences at the time. We found many resources like "How do I push a branch in Git?" or "How do I pull from multiple remotes in Mercurial?",

Continue reading »

Tags: , , , , , , , , , , , , ,
Comments (4)

FishEye Release Report 2: You Want to Merge What?

The last time I introduced the FishEye Release Report, we focused on how it can show you which JIRA issues are included in your new release based on the source, rather than based on what your developers enter manually into JIRA. Furthermore, the Release Report summarizes important information about those JIRA issues, such as their Fix Versions and relevant code reviews. We find these features alone make the plugin really useful, but we have one other high value use for the Release Report that might

Continue reading »

Tags: , , , , , ,
Comments (0)

FishEye Release Report – Stay On Top of Your Versions

The Release Report is a plugin that the FishEye and Crucible team uses to help their development process. Check out the Release Report as well as many other plugins at plugins.atlassian.com. Tracking Changes Before A Release We at Atlassian frequently use feature branches for the ongoing development of FishEye. Feature branches have proved to be a very practical part of our collaboration process, but it also comes with its own set of headaches - especially when we're about to release a new version. In

Continue reading »

Comments (1)