[Qt-creator] [Dev] Qt Creator Submit Policies

Oswald Buddenhagen oswald.buddenhagen at nokia.com
Tue Nov 8 15:09:11 CET 2011

On 11/08/11 11:35, Ziller Eike (Nokia-MP-Qt/Berlin) wrote:
> On 4 Nov 2011, at 16:44, ext Oswald Buddenhagen wrote:
>> what's wrong with everyone pulling the branches?
> [...] A mainline repository with lots of branches with barely half-finished experiments, where it is even difficult to say what the scope of each branch actually was supposed to be without looking at the source changes in there (because branch names as the "description" is not sufficient) would be something to definitely avoid IMO.
that can be solved via policy. every wip/ branch needs to be in The 
Wiki. everything undocumented or stale will be pruned out, just like 
already merged branches.

> I agree that http://codereview.qt-project.org/#admin,projects is not well suited for any management of a larger list.
> The same problem would exist when putting everything in a single repo, "git branch -a" isn't a suitable UI either (where it's even not possible to give the branches a longer description).
still better, because it is for one repo at a time only.

>> i want to enable private namespaces in gerrit [...]
> Sounds ok-ish if that had a sensible UI then, that is better than a single long list and still allows some discoverability.
well, no discoverability for personal branches at all, unless you fetch 
the entire namespace (for the parts you have access to, anyway). but 
that's exactly the point - you don't want to bother all people with your 
experiments - you tell the ones you consider relevant.
this does not affect "official" branches, except that it should keep 
their number down.

More information about the Qt-creator mailing list