[pulseaudio-discuss] Release planning

[Colin Guthrie]

'Twas brillig, and Tanu Kaskinen at 26/03/12 13:32 did gyre and gimble:
> On Mon, 2012-03-26 at 14:42 +0300, Roman Beslik wrote:
>> So, how can I get a release candidate from Git? What URL should I probe? 
>> There is no branch named "2.0" or like. Sorry, I am not familiar with 
>> your terminology "*happen off* the master branch."
> 
> The phrase means that there won't be a separate branch for 2.0. When the
> code is ready, the release will be made from a commit in the master
> branch. For an official release candidates we use tags. The only RC so
> far for 2.0 uses tag name "v1.99.1". So check that out. If you want to
> test the release candidate, and getting the code straight from git is
> ok, I guess testing the latest stuff in the master branch would be
> slightly more useful than v1.99.1.
> 
> Today is supposed to be the release day. Is it going to happen? As for
> the non-fixed "release blocker" bugs that I've flagged as such myself,
> [1] has at least a preliminary patch from David (Arun said he'd have a
> look at it also today), and [2] should be removed from the blocker list
> (I didn't have the time to finish it after all, and it's not a critical
> issue).
> 
> [1] https://bugs.freedesktop.org/show_bug.cgi?id=44397
> [2] https://bugs.freedesktop.org/show_bug.cgi?id=45817

I'd propose we do another tarball tomorrow and then release on Friday or
Monday if no further issues crop up.

Col


-- 

Colin Guthrie
gmane(at)colin.guthr.ie
http://colin.guthr.ie/

Day Job:
  Tribalogic Limited http://www.tribalogic.net/
Open Source:
  Mageia Contributor http://www.mageia.org/
  PulseAudio Hacker http://www.pulseaudio.org/
  Trac Hacker http://trac.edgewall.org/