Re: git bikeshedding (Re: triggers in dpkg, and dpkg maintenance)
John Goerzen writes ("Re: git bikeshedding (Re: triggers in dpkg, and dpkg maintenance)"):
> On Friday 29 February 2008 6:16:59 am Otavio Salvador wrote:
> > That's why you should avoid using the branch as basis to others until
> > it's clean and also avoid to make it public (without a reason) too.
> Whatever happened to "release early, release often"?
Also, Otavio is quite wrong to suggest that I shouldn't have based my
experimental flex branch on the triggers branch. To do otherwise
would have made conflicts inevitable because the two overlap; I would
have had to do my flex work based on the old code and then do parts of
them again, with a merge trainwreck to sort out.
It is exactly that merge trainwreck which my workflow - which is the
same as that adopted by nearly all users of every drcs except git -
avoids. It is that workflow which the present `dpkg team' insist that
they are unwilling to accept.
It is a `policy' that they have `agreed' and in their view as a
supplicant I should just knuckle down and obey it. Well, firstly the
policy is wrong, and secondly I am not really interested in playing
some game where I have to bow and scrape and do makework to prove