Rockbox.org home
release
dev builds
extras
themes manual
wiki
device status forums
mailing lists
IRC bugs
patches
dev guide



Rockbox mail archive

Subject: Release policy and coordination

Release policy and coordination

From: bk <mutualaid_at_gmail.com>
Date: 2006-05-30

Hey all,

Since 3.0 didn't happen today (despite it being the proposed absolute
deadline) I think some rethinking needs to be done about releases.

Obviously there's some problems to deal with, since we've been in a
freeze forever, there's little CVS activity and no clear indications on
when a release might happen, what's holding it up or who even makes the
final decision.

Maybe with how development is now working so-called 'stable' releases
aren't really suitable? Would it be better to just release a CVS tarball
once every 30 days like wine used to do? The 2.x series is already out
there so we could call the new tarballs something like
"rockbox-3.20060531.tar.gz".

Regardless of the release style I propose that something be done about
communication. Let's appoint someone the title of release
coordinator/manager who's job it is to get the devs together on a
specific date or feature goal and make sure it gets stuck to. If we
promise to release on a certain date it will happen. If it doesn't, the
user/contributor community will get a specific list of reasons why and a
new target date. I'm not saying the person would have dictatorial
control, but instead that person would make sure that there's consensus
among the core devs and that decision making is open and transparent.

bk
Received on Tue May 30 01:15:20 2006


Page was last modified "Jan 10 2012" The Rockbox Crew
aaa