[Qt-creator] Creator segmentation faults becoming common...

[Coda Highland]

On Tue, Jul 7, 2009 at 10:56 AM, Daniel Teske<daniel.teske at nokia.com> wrote:
>
>> Thats the thing... DVCS doesn't have the same notion of "commit" which lies at the heart of why SVN / CVS is broken / painful / bad.  The idea is that one can publish to a separate repo or non-master branch but it doesn't get merged into  "blessed" branch / repo until its been vetted.  The model moves from a central store with "controls" to one based on a "web of trust"... the Qt community / Nokia identifies this branch... but other fixes can be made available by anyone at any time, tested, and easily backed out if necessary or, more importantly, incorporated when one synchronizes with the blessed branch.
>>
>> Take last weekend.  There was a trivial bug which broke the build (needed a header file).  Easy fix but the patch needed to be pushed around by pastebin because of this, um, somewhat broken use of git.  The google tech talks by Linus and Schwarz (i recommend the latter) describe the development and dissemination model and the "web of trust".  It has nothing to do with controlling dissemination, and everything to do with trusted branches and repos.
>>
>>
>>
> I don't think you need to tell us how git works. We are using git in a
> way which best suits our requirements. As such we have decided to
> automatically update gitorious/master with a 12h delay from our internal
> master. This creates situations in which master does not build, and yet
> the fix was already applied internally. That is obviously a drawback,
> but we have decided that the benefits outweight the drawbacks.
>
> git supports a lot of different work flows. While some recommend indeed
> "web of trust", to claim that is the "right" way to use the tool and
> claim that other usages are "broken" is simply wrong. In fact one of
> strengths why we choose git over other version control systems was, that
> we could implement a work flow which fits our requirements.
>
> daniel

To be honest, I must say I agree with Glenn. I've done a LOT of
research into DVCS in trying to find a suitable SCM for the projects
I'm working on. This unimaginative SVN-holdover workflow is... rather
inappropriate for a project like Qt or Qt Creator, especially one
that's trying to be more "open" to the community, and ESPECIALLY one
that has a lot of people using "unstable" builds on a day-to-day basis
due to shortcomings (bugs and/or missing features) in the "stable"
versions or simply due to a desire to help improve the project.

Glenn's description of a more appropriate workflow is spot-on. The
potential of a distributed VCS is wasted on this kind of procedure;
the fact that you CAN have an "almost-always-works" bleeding-edge
branch without much effort at all is, I think, an clear indication
that you SHOULD have one. The Linux kernel -- the premiere
poster-child for git -- uses a workflow like this and THRIVES.

/s/ Adam Higerd