[PyKDE] PyKDE for sip 3.5 and 3.6

Ricardo Javier Cardenes Medina rcardenes at debian.org
Fri Apr 18 22:09:01 BST 2003

On Fri, Apr 18, 2003 at 10:00:19AM +0200, Gerard Vermeulen wrote:
> > 
> Ricardo has proposed to do more intermediate releases. Since sip and
> the sip files evolve together, I do not like the idea because it makes
> maintaining PyQwt harder (and PyQwt is much smaller/simpler than PyKDE
> but I would like to keep PyQwt compatible with several sip/PyQt versions,
> if possible). 

Well. I'm not telling that Phil/Jim/yourself have to release
intermediate releases just for every change you do on your code, or even
a micro release every (say) two months.

It isn't even useful if some of those micro releases introduce
incompatible changes (eg: the latest sip_Name mangling of Phil).

So, what's a desirable "point release"? The one that fixes bugs, but:

  * doesn't changes the way you expect the software to work (eg: same
    input/outputs, etc), except where the previous behaviour was buggy.
  * doesn't substracts symbols from binary objects (it's fine if it
    adds symbols, since the current software won't notice), or changes
    the names of previous working symbols.

These two conditions allow to recompile only the buggy software, and
deploy it on a previous buggy environment, to make it work with no need
to recompile other software, depending on the buggy one.

Every programmer collects a number of this kind of fixes, between one
release and the next. I think that isolating those fixes, applying them
and releasing the result software on a periodic basis as intermediate
releases, is good.

More information about the PyQt mailing list