|
|||
|
Welcome to the April issue. This month... Bamboo comes with distributed builds, Confluence gets a facelift, FishEye has new graphs, Crucible offers per-project pages, and lots more. Oh, and in case you missed it, we released JIRA Solver on April 1st. Happy reading!
|
||
|
This release of our continuous integration server introduces the ability to run distributed builds. You will find this particularly useful if you need to run your builds in different geographic locations or on different platforms. Bamboo 2.0 Release Special - Buy Bamboo 2.0 before 31 May 2008 and receive a 50% off discount! Read on | Download | Release notes | MyAccount
The newest version of the enterprise wiki includes major UI improvements with an improved interface, drag and drop page reordering, simplified menus and more. Read on | Download | Release notes | MyAccount
FishEye 1.5 adds the ability to present historical, per-author line count information. This new suite of graphs show how much each user has contributed to the code base, over time. Read on | Download | Release notes | MyAccount
Crucible 1.5 brings new enhancements that make your code review activities quicker and easier. The all-new per-project page consolidates the display of work done on a particular goal or product, while filtered search for defects and comments provides rapid access to Crucible content that you need to see. Read on | Download | Release notes | MyAccount
|
||
|
First, some quick background. My name is Charles Miller. I am (not counting the founders) the fourth-longest serving Atlassian employee. I started back in 2003 as a developer on the Confluence project, worked my way up to be team lead for a while, slipped sideways into an architect role, and am currently on temporary secondment to the JIRA Studio team. About three months ago, at our not-quite-quarterly all-hands meeting, Mike announced that Atlassian would, at some time in the future, in some way shape or form, begin an experiment with 20% time. My immediate reaction was:
|
||
|
Codegeist III , the annual Atlassian plugin contest, is in full effect. So far we've received some great entries. If you're still hacking away, remember Codegeist ends 9 May 2008.
|
||
|
This is a blog about the 20:80 rule. Yes, you have read this correctly. This is not the famous Pareto's Principle which states that 80% of the effects come from 20% of the causes or typically when applied to business, suggests that 80% of your sales come from 20% of your customers. Hudson's Rule No, this is a more important concept which I call Hudson's Principle which states that a 20% disruption to a business needs to have an 80% return for it to be considered a worthwhile initiative. Which is a roundabout segue to Atlassian's 20% time experiment that they announced on the developer blog a couple weeks back.
|
||
|
There have been a few customers wondering how Crowd scales (outside of its integration with JIRA/Confluence). Unfortunately, the answers we could think of ranged from "..yes" to "nfi" — so we decided to take a look at load testing Crowd. Getting a million users We ran a script to insert users into our internal directory, starting with user0 and ending with user999999. This took 5 hours. I came back in this morning and found that Dave, our team lead, had already verified that it was possible to authenticate and use the Crowd console without issues. This shows us that Crowd is capable of not falling over if there are 1 million users in its repository. He also decided to double-check that JIRA integration was very broken with this many users. :)
|
||
|
Sign up for a user group:
|
||
|
This problem was a rather strange one (JRA-14423). I like tooling with JavaScript but sometimes it surprises me how many differences there may be between various browsers. Using JavaScript libraries has its benefits. A library may give us another abstraction layer — a layer that if designed well can hide differences between browsers and provide a uniform interface. Another reason to use a library is that if a library is popular and widely used, it is very likely well tested on probably more browsers than you are willing to test your code on. However, no library is perfect. The problem we encountered and I am about to describe happened with Yahoo! User Interface library. In JIRA, we have a little panel that pops up and shows a list of links.
|
||
|
Here are some blogs and sites we've been tagging around the office:
|
|||
|
We'll be at Web 2.0 this week and JavaOne in May, so stop by our booth and say hi. If you haven't yet registered and want to, use these codes and save $100. Happy hacking! Your mates at Atlassian
|
|||
|
Other ways to keep on top of what's happening at Atlassian: |
|||
Read or subscribe to our 
See what everyone's talking about on the Atlassian 
Get a