[PySide] Cutting PySide 1.1.3 with Qt 4.8.4 (Was: typesystem_core_common.xml memoryleak remains)
techtonik at gmail.com
Tue Jun 18 07:07:13 CEST 2013
On Mon, Jun 17, 2013 at 7:02 PM, John Ehresman <jpe at wingware.com> wrote:
> On 6/15/13 2:46 PM, anatoly techtonik wrote:
> > Hi,
> > There are plenty of bugs fixed since Qt 4.8.2  and PySide 1.1.2
> > , so it seems to be a good time to cut a new PySide release. Anybody
> > knows how to do this? I expected to find release checklist here -
> > http://qt-project.org/wiki/PySideDevelopment - but couldn't find any.
> I want to do a release soon. There are a few changes that are in
> process on gerrit that I would like to land and it looks like multiple
> tests are failing with Python 3.3, at least on OS X. I will be looking
> at the failures.
> I'm planning to call the release 1.2 -- some of the changes since 1.1.2
> are significant in terms of preventing segfaults. Note that pyside
> itself isn't dependent on the newer Qt versions -- the current release
> works with Qt 4.8.4 as well as with older versions.
I'd follow semver.org - if there is nothing added into API, then there is
no need to increment major version. As for 4.8.4, the problem is that
binaries are compiled against 4.8.2 and there is little sense to recompile
them against 4.8.4, because it will make some bug reports invalid.
> > 3. actually, there is not enough information about issues affecting
> > 1.1.2 at
> > https://bugreports.qt-project.org/browse/PYSIDE/fixforversion/12609
> I don't know what you're getting at here. Are you looking for a list of
> all known bugs?
For the list of fixed bugs in 1.1.2
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the PySide