[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-devel
Subject:    Re: KDevelop UI
From:       "Alexander Dymo" <dymo () ukrpost ! ua>
Date:       2007-07-20 19:31:16
Message-ID: a178f7b00707201231n4ed5093x823054fc628365e7 () mail ! gmail ! com
[Download RAW message or body]

Ok, to branch or not to branch is not a question ;)
Let's say that if you work on smth big and lengthy that is not
self-contained (aka plugin), you should better create a branch. It's
just as simple as that.

But... the whole idea behind proposed branching policy is to make sure
KDevelop is always stable (or at least usable). But I believe that
having a branch is not enough. When you merge your branch back, what
you usually know is that your new feature works. This means other
features might easily become broken. So IMHO what we need not to have
developer's branches, but rather we need to have (more) tests.

_______________________________________________
KDevelop-devel mailing list
KDevelop-devel@kdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
[prev in list] [next in list] [prev in thread] [next in thread]