Warning this article may contain opinions of the author that you and iTWire don't agree with.
Visit the last page to have your say in our forum.

No. 1 Story

Cloud alliance sides with Optus on copyright

OzHub, the Macquarie Telecom-led cloud computing alliance, has come down firmly on the side of Optus over the copyright controversy surrounding Optus TV Now, warning that any moves to change the law "risk branding Australia a global luddite state."

read more

Fedora edges closer to Debian development process

Opinion and Analysis

Last month, Fedora, the community GNU/Linux distribution sponsored by Red Hat Linux, announced that it would create a new development branch in order to avoid putting a speed hump in the way of developers.


Fedora's old way was to stop development at a certain point in Rawhide (the name of the development branch), stabilise, release, and then pick up development again. This meant that uploads to the development branch would have to cease until the release process was over.

Fedora's new method is to split off the development branch at the point when it is deemed fit for stabilising and releasing. This is then released as the next Fedora release. Development on Rawhide continues apace.

But there is a way to go yet for Fedora to catch up with the Debian development pattern which has three streams of development - stable, testing and unstable. Stable is the last release which receives only security updates,  unstable receives all the latest software which moves into testing when it has been in unstable for a while and now shown any major bugs. Testing becomes the next release.

Asked for comment, Debian GNU/Linux project leader Steve McIntyre said: "What they seem to have switched to is a common methodology: at the point when development freezes for a stable release, switch the frozen code onto a new branch so that you can continue to develop your bleeding-edge new stuff without jeopardising your stable release.

"It's a little bit similar to what we used to have in Debian before we started doing the 'testing' distribution, and it's a reasonable compromise. So long as you can still find people to do the stabilisation work, you can let your eager 'unstable' developers continue playing with new ideas.

One problem remains with the new Fedora model - at what point does one freeze things? "The reason that we moved on from this cycle and added the testing distribution was that we found it nigh-on impossible to find a good point to simply declare the unstable branch ready to freeze," McIntyre pointed out.

"When you have lots of developers uploading daily, it's possible you'll never get a stable enough base to be able to stick with it. It can be a lot of hard work to get there."




 

Loading comments ...

- sponsored feature -

The Death of Traditional BI: What’s Next?

How to Make Business Discovery Work for Your Business IP PABX BUYING GUIDE

Business Discovery takes its cues from consumer apps. Like Google, it encourages us- ers to hunt for and explore data without worrying about or even noticing the underly- ing technology. Their entire experience is working within an intuitive interface to get real-time, self-service results with only minimal training. ...more