[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: We need an RFC procedure [Re: Services can now have a default value]

From: ng0
Subject: Re: We need an RFC procedure [Re: Services can now have a default value]
Date: Sun, 23 Apr 2017 12:02:18 +0000

Ricardo Wurmus transcribed 1.0K bytes:
> Ludovic Courtès <address@hidden> writes:
> > As for posting the change before applying it, I should do more of that.
> > I’ve taken the bad habit of pushing what I consider as “simple” changes
> > directly to the repo, but perhaps the criteria should be reconsidered.
> > :-)
> I think it’s fine to push simple changes directly.  There hasn’t been a
> single instance when you pushed something where I thought that it
> shouldn’t have been pushed.
> Between releases we are free to change things; they only have to be
> mentioned in the ChangeLog for the next release.  ABI breakage can get a
> little annoying if one doesn’t know about it and the compilation fails
> with unclear errors.
> It’s a little unfortunate that packages are developed together with
> everything else, because this means that there is no way for people to
> opt out of breaking changes until the next release without also opting
> out of getting any updates at all.
> --
> Ricardo
> GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC

In my opinion it is simple as long as nothing else is affected (or affected
parts are changed at the same time). In other words, if it touches
the way services, packages etc are compossed or definitions which (canonically)
happen to be in the system config, it should be communicated in advance.

I think almost no change Ludovic commited in the time I'm involved broke 
even if it wasn't simple changes.
To discuss changes doesn't hold them back, it gives others a clear view
on what is happening, on the intentions and maybe to help fix mistakes
in advance.
I don't think anyone produces intenionally bad code, it's just a difference
if you develop in reaction to changes you only know about once they are pushed
(or once feature branches are completed) or if you can discuss about them.
In the first case it's an isolated effort which ressembles a group to the 
in the second case it's getting closer to community work.
PGP and more:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]