Hi Tim,
> When those are merged in, and I expect that to happen before December 1st,
> I suggest we roll those up as a real beta and start working towards a New
> Year's Eve release. I won't plan on merging anything else to the master
> branches before the release except for bug fixes.
A new year
Tim Moore wrote:
> On 11/27/2009 10:08 AM, Erik Hofman wrote:
>> You could argue that the new sound code has little benefit over the
>> previous code (it does have the slight advantage of source management)
>> to make it necessary to include it in the next release already.
>>
> It's up to you. It
On 11/27/2009 10:08 AM, Erik Hofman wrote:
> Tim Moore wrote:
>> In my git repositories on gitorious, http://gitorious.org/fg, I've been
>> keeping
>> "master" branches that are supposed to be stable; the intent is for them to
>> be a kind of rolling release candidate that could be turned into a r
Tim Moore wrote:
> In my git repositories on gitorious, http://gitorious.org/fg, I've been
> keeping
> "master" branches that are supposed to be stable; the intent is for them to
> be a kind of rolling release candidate that could be turned into a release
> in short order. I've just pushed a bunch
On 27 Nov 2009, at 06:28, Tim Moore wrote:
> In my git repositories on gitorious, http://gitorious.org/fg, I've been
> keeping
> "master" branches that are supposed to be stable; the intent is for them to
> be a kind of rolling release candidate that could be turned into a release
> in short ord
In my git repositories on gitorious, http://gitorious.org/fg, I've been keeping
"master" branches that are supposed to be stable; the intent is for them to
be a kind of rolling release candidate that could be turned into a release
in short order. I've just pushed a bunch of commits to them that hav
6 matches
Mail list logo
