#2670: WzConfig: UPnP always gets enabled again.
-+-
Reporter: Fastdeath | Owner:
Type: patch (an actual patch, not a |Status: new
request for one)
#2671: Fatal error during loading save game
---+-
Reporter: Emdek |Type: bug
Status: new |Priority: normal
Milestone: 3.0.1 |
On Sunday, 24 April 2011 at 21:28, Daniel Kliman wrote:
> It sounds like the development model described in
> http://nvie.com/posts/a-successful-git-branching-model/
Mostly it is influenced by the Linux kernel development process (arguably the
group of users most familiar with git).
> Is that wha
On Sunday, 24 April 2011 at 18:55, Per Inge Mathisen wrote:
> On Sun, Apr 24, 2011 at 12:43 PM, Christian Ohm wrote:
> > I've wondered if the concept of "stable release" is actually useful for us.
> It is useful for users.
Hm, that was supposed to read "stable release branch". We bare can keep 2.
On Apr 26, 2011, at 4:10 PM, Christian Ohm wrote:
> On Sunday, 24 April 2011 at 21:28, dak180 wrote:
>> It sounds like the development model described in
>> http://nvie.com/posts/a-successful-git-branching-model/
>
> Mostly it is influenced by the Linux kernel development process (arguably the
>
On Tuesday, 26 April 2011 at 16:31, dak180 wrote:
> I have yet to see a clear illustration of how the kernel development is
> managed can you point to what you would consider to be the best such?
http://en.wikipedia.org/wiki/Linux_kernel#Development_model for a summary,
http://git.kernel.org/?p=li
On Tue, Apr 26, 2011 at 10:24 PM, Christian Ohm wrote:
> I think the feature branches model is our best bet to achieve that. master
> won't ever have unfinished stuff delaying a release, and features can be
> developed in a branch as fast or slow as wanted without delaying a release.
I still reme
#2672: autorevision.sh produces garbage output if hggit extension is enabled
--+
Reporter: stiv | Owner:
Type: bug |Status: new
Priority: normal
On Tuesday, 26 April 2011 at 23:05, Per Inge Mathisen wrote:
> I still remember lua branch, qt branch, netsync branch, and terrain
> branch that festered like bad wounds while we struggled with lack of
> testing and little idea what to do with them until they were merged
> more or less untested (le
