2018

11. December 2018

- Release readiness of Qt for Python 5.12 evaluation
- branching missing (to be done today)
- snapshot generation not working properly (but no impact on release
- first release test automation established
- release announcements in work
=> conclusion: release ready (pending final smoke test)
- working on debugger helps for python on windows users and unresolved dlls
- more cmake work to enable opening of qt for python project from within creator

8. November 2018

- General bug fixing week throughout Qt RnD
- continued work on recursive type crashes
- will look at https://bugreports.qt.io/browse/PYSIDE-735
- doc snippet work
- uic port to python (uic generating python code - same for rcc under consideration)
- feature work to come to conclusion for 5.12 in early December (feature freeze 22. November 2018)

11. October 2018

- Qt for Python 5.12 will be first official release
-> Python developers have a guarantee to have source/behavior compatibility
-> Exception: - no BC/SC statement for libshiboken and libpyside
- XML schema may change as well
-> expectation: later releases of Qt for Python will commit on the exceptions above
- 5.12 branch was created and hooked into CI
- lots of discussions on how to solve the deployment use case across platforms
- wheel separation patches up on code review
-> new wheels: shiboken2, pyside2 (need new project on pypi)
-> users wanting to build their own bindings should currently build shiboken from source
- added ability to test build-able example (the script-able C++ examples)
- QVariant bugs
- PYSIDE-821 - dealing with circular dependencies around QAction
- Worked with https://talkpython.fm/ on Qt for Python podcast
- PYSIDE-795 Numeric Python support

02. August 2018

- 5.11.1 released (docs being updated on server)
- coin 5.11 broken because version mismatch between Pyside & Qt
- documentation for PEP 384 under review
- Qt Creator Python scripting support is improving
- submodule for QtCreator was requested to upstream the changes
- added support for reproducible builds
-> different builds caused different numbering for Qt types
- continued work in template specialization support
- looking into issue whereby Pyside generates bindings for Qt classes which have been disabled during the build by Qt (PYSIDE-762)
- progressing on QVariant bugs
- splitting Shiboken and Pyside from build system perspective (work in progress)

26. July 2018

- 5.11.1 release
- SHA will be current 5.11/HEAD
- 5.11.2 release tag created in Jira
- macOS 10.13 fixed in coin (build test only atm)
- documentation for PEP 384
-> code review during documentation revealed some bugs
- QTableWidget caused performance issues which was identified and fixed
- added C++ using stmt support to shiboken
- further work on PYSIDE-743
- addressing QVariant bugs
- preparing content for trade show visits and webinars
- Research: Python based plugins for QtCreator
-> bindings for QtCreator
-> 3rdparty scripts which can interact with QtCreator
- effort into splitting wheels to Python, Shiboken module and Shiboken generator
- more snippet updates on Qt side to enable override on Python side

12. July 2018

- Work on shiboken's type system (PYSIDE-672) merged
- Started checking the XML elements/attributes of the typesystem language to identify unused elements (PYSIDE-743)
- Started looking at emerging new API of Qt 5.12, which unveiled bugs in shiboken
- Finished the port of new examples related to PYSIDE-738
- Fix a Python 3.7 hang/crash (PYSIDE-737)
- Fix a Python 3.7 compatibility issue (PYSIDE-741)
- Work on hinting stubs for Python IDEs (PYSIDE-735)
- Will return to documenting PEP 384 at the weekend, promised.

05. July 2018

- Work on shiboken's type system (PYSIDE-672)
- Fixed COIN for macOS/dev branch (PYSIDE-734 / PYSIDE-724)
- helped with a very old bug (PYSIDE-60)
- started type hinting support (PYSIDE-735)
- Investigating the slowness of our bindings (PYSIDE-727)
- Working on expanding the examples related to QtCharts and fixing a few other examples.

28. June 2018

- Fixed some bugs for the 11.1 release (fix PYSIDE-570 , PYSIDE-693)
- code cleanup in shiboken
- Added option for C++ language level to shiboken
- Doc fixes, start using conditional section the Qt documentation
- Worked on PYSIDE-641 to handle the case of undefined len().
- Started work on method hinting. Discussion with the Wing IDE guys.
- Fixed issue related to the QLibraryPath
- Fixing a couple of examples.

21. June 2018

- Publishing snapshot wheels was disabled for some time, but is now back online.
- The team has been mainly solving issues related to the first set of wheels from the Technical Preview.
- Missing DLLs for the Windows wheels
- Examples incompatibility due to previous changes, missing resources, etc.
- Wrong paths associated to the QLibraryInfo class
- PEP 384: Tried to further reduce the patch size and to avoid Introduction of PepType.
- Stopped after it turned out to be impossible.
- Documentation:
- There are many snippets that contains the C++ counterpart, so there is a lot of effort to translate them to Python
- Continued on documenting the Limited API after it is now fixed.

31. May 2018

- ready for TP?
- 32bit win wheels not available yet
- request to upload larger than usual pypi wheels filed with pypi/warehouse project
- some wheel renaming related patches still pending to comply with pypi requirements
- PEP changes have merged earlier this week
- example patches still under review
- documentation not packaged as part of release (published on doc.qt.io on day of release)
- ByteArray changes re-based on top of PEP patches -> to be merged until end of week
- have release candidate wheels early next week for testing
- aim to release it on 13th June 2018 (might shift till Monday (18th June) afterwards)
- assessed missing bindings situation

26. April 2018

- New icons for project in work
- 5.9 branch working (5.11 branch is broken due to issues on the Qt side)
- snapshot tool for Windows broken (crashing) -> fix pending but blocked by CI
- in the mean time only mac and Linux snapshots working at the moment
- 5.6 branch broken as well as 5.9 changes for qt5.git need to be merged to 5.6 too
- delivery of 32bit Windows binaries not started
- tiny bug fixes and other types of cleanups (e.g. build scripts) left and right
- General replacement of Pyside name against Qt for Python (module name remains as Pyside)
- APIExtractor documentation still being merged to git
- style sheet issues being addressed
- QtWebEngineCore bindings finally merged
- PEP work ongoing (and coin to work)

19. April 2018

- COIN finally back in working shape
- Further fixes for documentation, module pages, experimentally tried to show in Qt Assistant
- Tab Browser example further improved
- Qt for Python blog posts being worked on
- Continued working on WebEngine issues
- Some investigation and preparations to make WebEngine apps work with PyInstaller (very early phase, still doesn't work)
- Pending patch for QtWebEngineCore bindings
- Installation adjustments for standalone builds on Windows
- Heap types are complete. Starting integration with PEP 384.
- Finished the integration between ApiExtractor and Shiboken documentation.
- Worked on a couple of blog posts.
- Wiki structure and started to write the Tutorials

12. April 2018

- Getting Started guide under works by doc engineer
- focus on fixing coin on Mac & RedHat 7.4 (looks promising so far)
- shiboken documentation and diagrams being updated
- old and unused docs dir shall be cleaned out
- Tab Browser example improved
- License page generated based on attribution files
- lots of discussion when to release Qt for Python TP
- after Qt 5.11 release (scheduled for 31.5.)
- likely to be mid June (stay tuned)
- WebEngine issues
- needs updated qt.conf files to be deployed for apps
- Heap types (work in progress)
- still more work in pipeline to get code PEP 384 ready (Heap types are prerequisite)
- Qt for Python blog posts being worked on

01. March 2018

- automatic snapshot process almost in place (pending reviews) (RTA to follow)
- general bug fixing (including build and version problems)
- most community Pyside1 pages point to official Pyside 2 (Qt for Python) wiki pages
- PYSIDE-595 - Heap Type conversions ongoing
- documentation improving
-> class diagrams being generated
-> missing links and references
-> dependencies to qdoc bugs
-> snapshot process in works
- added support for scoped enums in pyside
- Important things discussed:
- PySide2 versioning (current proposal WIP patch at https://codereview.qt-project.org/#/c/221767/)
- Do official releases follow Qt branch names? -
-> yes (minor release of Pyside is bound to same minor release of Qt
-> patch level version may differ
- Will we have snapshots, and if so, will they be uploaded to pip? How will we handle snapshot versions?
-> tentative yes, if public pip server supports snapshots Pyside should be good citizen
- alpha / beta / RC versioning?
-> Pyside should follow the Qt schema
- Probably need to take into account PEPs for versions pushed to Pypi.
- Shiboken / PySide2 versions in sync?
-> yes, they should be in sync
- Will we specify a version for 5.6 branch?
-> yes, but no packages being made
- Are we sticking to the package name PySide2, but follow Qt 5.x versions as PySide2 versions?
-> Pyside2_5.11.0 as in https://codereview.qt-project.org/#/c/221767/
- Do we want to deploy msvcrt dlls into Windows packages?
-> needs more research - is it really needed ?
- Do we want to ship debug symbols for Qt inside the PySide2 packages?
-> not for now
- Do we want to ship debug Qt shared libraries for macOS packages? (not possible on Windows, not applicable on Linux afaik).
-> not for now
- How will the pip upload process look like? Manual uploads? Who takes care of it?
-> Qt release team will take care of it
- Current branching policies:
-> 5.6 branch stops being merged into 5.9 (after pending patches have merged) -> cherry-pick mode
-> 5.9 is base line for patches and being forward merged to 5.11
-> no packages from 5.9 & 5.6 (interested parties need to get it from git)
-> 5.11 becomes branch for first TP
-> dev is feature development
-> all first TP release related patches go to 5.9 (and 5.11 subsequently)

22. February 2018

- dev branch is still/again broken in CI, seems like pyside issues
- changes to create automatic snapshots out of CI is still under review
- Numerous small fixes to the doc generation, significantly bringing down the number of documentation warnings
- Massaged build rules to improve built packages
- Removed unnecessary _utils.py file PYSIDE-600
- Changed wheel package names to contain both PySide2 version and Qt version against which it was built PYSIDE-613
- Finally got libclang to be deployed into packages
- Improved build process not to copy unnecessary symlinks and duplicating libraries when creating wheel (so that you don't get 3x size increase because of 3x number of WebEngine libraries) PYSIDE-495
- Fixed wheel package names to contain correct minimum deployment target with which macOS was built with (on further analysis, this will need further improvement) PYSIDE-612
- Fixed rpath handling for QtWebEngineProcess when creating standalone packages on macOS PYSIDE-605
- Added CMake build rules for scriptable application example PYSIDE-597
- Investigated and fixed a heap corruption bug in a test that caused constant crashes on macOS CI runs
- Reduced number of warnings when running shiboken to create user bindings (like scriptable application example) PYSIDE-587
- PYSIDE-595: Making slow progress, still debugging. It's a difficult process, but assumption is that it will work.
- Havent's merge this new patch because we should be 200% sure it's properly working.
- Working on a few bugs PYSIDE-106PYSIDE-570
- One of the bugs PYSIDE-611 was valid only for 5.6, but I noticed a strange behaviour on 5.9, so I will keep working on it, even after we move 5.6 to cherry pick mode.

8. February 2018

- Looking through previous EuroPython talks to write a proposal for this year.
- Working on a few bugs (fixed a couple related to objects references),
- that sadly will open new issues with memory management. A further analysis on this matter could improve the current memory leaks on PySide.
- Trying to "organise" a little the typesystem XML files.
- Working on PYSIDE-104 that ended up being a general issue on PySide about a proper verification between slots and signals arguments, to find the best match.
- Merged a few build related changes in 5.6
- Pending change for PYSIDE-593
- Pending change for PYSIDE-605
- Merged changes for PYSIDE-603 and PYSIDE-604
- Investigated and attached minimal reproducible example for PYSIDE-585
- Investigated some macOS build related aspects for package release
- 5.6 CI is unblocked, but 5.9 CI is blocked due to qtbase issues (version bumping)
- PYSIDE-560 waiting for view
- PYSIDE-595 work ongoing, not ready yet
- PYSIDE-363 Documentation: Fixed images, fix handling of qdocconf files that contain several modules. Looking at snippet resolution.
- Problems with Qt3D due to refactoring of Qt3Dextras in 5.10. Pushed patch suggestion.

1. February 2018

- Continued work on documentation PYSIDE-363, fixed static pages, add more modules, fixed parameters to qdoc, images
- The GettingStarted wiki is getting better, besides a cleaning it a bit
- moved the topics around to have guidelines by supported platform (a la Qt)
- have received feedback and trying to add more information
- Addressed bugs:
- PYSIDE-34
- PYSIDE-264
- cleaning a bit Shiboken's XML files.
- PYSIDE-560
- ported to 5.9, extended to 18 header files
- solved unicode problem
- reduced the patches to be minimal (avoid many #ifdef's, use a verbose macro name if possible)
- made everything compile but one announced file: "object.h" depends on the heaptypes solution (PYSIDE-595). Removed WIP status,review pending.
- PYSIDE-595
- Started experimenting
- turned out that the signature extension barfed because it could no longer find the type "__name__". The function PyType_Type.tp_new needs to be called to provide the "ht_name" attribute that is used in heaptypes.
- solving the attribution file issues.
- Pending patches to fix libICU issues
- Pending patches to fix OpenSSL issues PYSIDE-599
- Pending patches to deploy libclang library for shiboken
- Improved documentation about OpenSSL dependency
- Pending patches for cleaning up build scripts a bit (logging and refactoring)
- Pending patches to reduce barrage of warnings PYSIDE-587
- Pending patch for adding CMake build rules for the scriptable_application example (useful as a reference on how to use shiboken for custom bindings) PYSIDE-597
- Old 5.6 CI integration issue fix, but a new issue appeared that was fixed for 5.9 and dev, but still blocks 5.6
- Updated the qml basics tutorial

4. January 2018

- multi pyside packages (not easy to do)
- renaming Pyside to "Qt for Python"
- quite challenging due to implied import and lib changes
- alias for existing imports would be beneficial
- discussion around existing function test
-> working assumption is that we ignore added function and check for existing base line only
-> effort too large to maintain every single new addition
- discussed issues around concurrent existing Qt builds while building pyside (potential cross leakage)
- various fixes to doc generation steps (see PYSIDE-363)
- discussed need for good examples as part of documentation
-> considered options to cleanup and remove need for submodule

2017

21. December 2017

- Issues building for Windows for Python 2 and 3 (on coin)
- discussing potential pyside demo/example for RTA purposes
- Continued work on macOS / Qt 4 header issues, progress is there
- breaks GL signature test on Linux, needs further investigation
- Investigated PyInstaller (potential option to deploy apps written with Pyside)
- seems to work almost out-of-the-box for deploying PySide apps
- Investigated building one package compatible with multiple Python 3.x minor versions
- not possible currently, will require a lot of work, possibly not feasible
=> we need to build 3.4,3.5,3.6 * win, linux, mac packages = 9 packages
=> 3 more for each platform and Python 2.x
=> commercial packages?
- lots of discussions and fixing of doc tool chain (qdoc in dev currently broken)
- adding documentation has begun in earnest
- continued work on PYSIDE-578

30. November 2017

- packaging related coin changes
- last weeks merges between 5.6 and 5.9+ blocking coin have been fixed (in particular on RHEL)
- 5.9 + 5.6 are passing, dev has some private Qt changes which will affect pyside/dev
- lots of coin infrastructure issues
- RTA test wheels added (install and launch single example)
- crash bugs in 5.6 branch reported but not details known yet (waiting for more details)
- some discussion what changes should be put to 5.6 vs 5.9 branch
- Qt3D bindings started
- some changes in qt3d/5.9 required)
- shiboken bugs discovered in the process (virtual function guessing & some comparison operators for namespace generated)
- small regression related to rpath handling on Linux
- open pip wheel issues:
- handling of multi Python version wheels
- testrunner bugs addressed and reducing flakiness
- issues in Pyside when building with gcc 7.x
- qdoc from qt5/dev is required for pyside due to webxml support
- it is a problem for the pyside/5.9 branch

16. November 2017

- Build system cleanup. It is now possible to build only a subset of Qt modules per cmd line option
- this is not complete and may need further patches
- Added QAxContainer, more classes from 5.10
- Preparing to add Qt3D
- Removed flaky test
- further research on how pip wheels might be used for Pyside
- seems to work well on win & macOS
- problems on Linux related to libICU (or in general due to different system libraries)
- implemented and tested --standalone feature for the main Qt platforms PYSIDE-558
- open question remains how 3rdparty Pyside deployment path might look like
- PYSIDE-510

9. November 2017

- Work on simplifying the build system, made it possible to specify a module subset to build
- PYSIDE-558 Fixing rpaths and making --standalone work on the 3 platforms. Result: Self-contained binary wheels. Needs Review.
- Trying to setup the project for building the docs. I managed to build the rsts from the patch in gerrit but running sphinx on those rsts results in errors about python 2 style code.
- PYSIDE-510 work continued

2. November 2017

- Releasing:
- continued work on macOS installer
- binaries must be patched during the install from repo (rpath setting)
- adopting the scripts from Qt for Pyside
- made pip install work on Mac -> would be alternative to online installer approach
- two deployment choices available
- discussions on how void* pointer should be handled, two options on the table
- add additional Pyside module handling such pointers
- add feature to shiboken to transparently add the support to any arbitrary C++/pyside project using shiboken
- documentation snapshot generated
- simplified setup-pyside and related build script options

26. October 2017

- Releasing:
- test repo for online installer created (mac seems to deploy)
- first evaluation of suggested installer approach on various platforms
- Documentation:
- Qt doc team joined the effort
- first experiences are collected
- should new documentation be done in rst rather than qdoc format?
- Getting started, General platform requirements and general fixes turning up during generation
- PYSIDE-571 received further fixes and reviews
- REDHAT not working on Coin (caused by gcc header issues)
- other minor improvements

17. August 2017

- Almost everyone is still on holiday - not much progress
- PySide 5.9 branch CI changes are still pending integration / ongoing due to issues with the CI infrastructure switch
- Investigation ongoing regarding QSSL classes on 5.9 branch
- PYSIDE-510 - ongoing work to make separation of different licensed code
- PYSIDE-156 - initial work to stop crashes when using methods that require an allocated QApplication instance
- PYSIDE-558 - initial investigation on how to proceed
- Updated the PySide2 wiki documentation to clear up build steps and requirements.

10. August 2017

- holiday time is hampering project at the moment - not much progress
- CI changesin Qt affected Pyside project such that focus was on different CI matters
- PYSIDE-557 being addressed
- some very minor issues were fixed

03. August 2017

- PYSIDE-510 under code review https://codereview.qt-project.org/198654
-> license issues have to be addressed
-> some testing aspects still open (delayed till later on)
-> investigation of impact on deployment across multiple python run-time versions required
- missing bindings script/wiki page updated: Missing PySide2 bindings
- first working array support has been delivered (some adjustments still required), now proceeding to extend for OpenGL PYSIDE-516
- Missing classes in works (e.g. QAbstractnativeEventFilter, QFileLock,....)
-> revealed some issues of handling void* pointers

20. July 2017

- coin
- license test passing
- setup issues wit Python 3 and msvc 2008 vs 2015 issues
=> need to install newer Python 3 binaries
=> otherwise looks like enforced testing can be set alive on 5.6 branch
- 5.9 still having clang header issues
- 2D array support work in progress
- PYSIDE-331 -> waiting for PYSIDE-510 dependency
- PYSIDE-510-> issues with Python 2.x left
- need to get a handling what functions are not supported by pyside due to exclusions or missing support in shiboken

13. July 2017

- coin
- Production coin was updated today and all fixes are finally executed
- 5.6
- macOS 10.11 machines have Python 2.6, which causes test script to fail due its usage of a
module added in 2.7. Investigation in progress on the best way to fix this.
- build failure with Windows 8.1 (msvc2013-x86)
- 5.9
- macOS 10.12 missing virtual env (https://codereview.qt-project.org/200006)
- Rest Linux/macOS configs are failing various build issues
- dev is still pending for qt5 merge from 5.9
- PYSIDE-510 development completed, test added, needs review
- PYSIDE-331 ongoing work
- PYSIDE-550 investigated, needs a working solution to allow proper building on distros that separate Qt private headers into separate packages
- PYSIDE-354 ongoing work on C / C++ array support in PySide, some questions remains on how to deal with xml syntax and multiple dimensions.

29. June 2017

- coin
- Qt 5.6 all coin changes for Pyside are done but waiting for coin production update (after Qt 5.9.1 release)
- Pyside/Qt 5.6 on new OpenNebula infrastructure confirmed to run
- Qt 5.9 based setup still misses clang libs (merge pending)
- Pyside/Qt 5.9 test failure fixes on macOS
- worked on array support (passing arrays between Pyside and Qt API) - work in progress (PYSIDE-354)
- continued work on debug builds across the platforms
- embedded Python example under review (further testing across the platforms)
- PYSIDE-510 finished (not yet merged) -> revealed a few more problems in PYSIDE-331 & PYSIDE-308
- added a way to dynamically detect the available Qt modules in Pyside

22. June 2017

- building pyside on Win with debug and non-debug
- QSSL* classes do not build on macOS & Windows (patch in progress)
- dll name handling work finished (build system issues were addressed)
- PYSIDE-531 discussions
- coin
- followup from 18 May (windows issues in coin)
- test runner changes being merged should address this
- new regression on macOS targets though
- 5.9 issues due to clang continue to exist (will be addressed after 5.6 is enforced)

15. June 2017

- dll name handling fixed across the platforms (e.g. pkgconfig handling)
- PYSIDE-500 fixed
- PYSIDE-331 is still not done (in parts a module by module fix is required)
- PYSIDE-510 ongoing
- no further progress on coin
- Getting started guide has been updated dealing with Qt 5.6 and Qt 5.9 based Pyside builds
- scriptable Pyside example been developed to demonstrate SDK-like usage of Pyside
- lots of small infrastructure changes/fixes

8. June 2017

- Proposed solution for PYSIDE-500
- Further work on example for PYSIDE-526, work on shiboken2 command line handling to ease usage with qmake
- Updated Getting started Wiki
- Introspection work continued (PYSIDE-510)

18. May 2017

- Coin
- Win nodes didn't run the cleanup functions -> test failures due to artifacts -> no solution yet
- Clang issues persist and this must be addressed in the broader scope of Qt/qdoc depending on libclang too
-> until this point in time the setup is a manual one for pyside/5.9+
- merge of psyide repositories -> no objections against the plan in the community
-> merge will happen in the next few days (pyside.git, pyside-setup.git and shiboken.git become one repo)
-> examples, wiki and tools will remain as they are
- QOpenGL* porting continuing
- qttext2speech ported to Pyside2
- failing QML tests in Qt 5.9 based Pyside
- PYSIDE-510 - introspection solution in the works
- Qt World Summit Berlin 2017 (talk for Pyside being handed in)

12. May 2017

- looked into the Windows tests failures, and the reason might be related to how we copy around build artifacts, leading to an incorrect folder structure. Coin team to look at it.
- Fixed a small regression in 5.9 with building on macOS after some cmake changes that happened in 5.6
- Implemented, tested, reviewed and committed the multimedia widgets examples
- documentation from Pyside1 days can not be generated anymore
-> new approach required using exiting Qt5 doc tools
- QOpenGL* port to Pyside has started -> missing support for arrays in shiboken
- more thorough design discussion needed
- Coin
- provisioning for clang in Qt CI ongoing: https://codereview.qt-project.org/#/c/192517/10

04. May 2017

- Coin
- libclang 4.0 provisioning available (code reviews ongoing -> enabler for Pyside and qdoc testing)
- 5.6 coin issues resolved
- macOS related CI/cmake failures were resolved
- some CI sync issues among pyside submodules (always submodules HEAD is tested)
=> may have to change once we come closer to the final release ->
=> fine as long as we are in heavy development mode
- discussion around Ubuntu and OpenSuse configurations
- minimal cmake requirements not met on all distros
- 5.6 only be build using RedHat 6.6
- 5.9 builds have updated Linux distros -> may be able to obtain a new cmake version without hacking the standard toolchain
- QtMultimedia and QRaster* API bindings further completed
- added tests and examples for the above bindings/APIs
- PYSIDE-510 (required for simplified and more generic testing of bindings)
- PYSIDE-504 work is ongoing
- PYSIDE-507 -> avoid hardcoded includes when certain Qt modules are not available
- brief discussion whether to merge the shiboken and pyside repo
-> advantages from a CI perspective and reduces pyside setup complexity

26. April 2017

- Coin
- provision for 5.9+ branches -> we would like to use libclang 4.0
- test still not yet executed due to branch mismatch which pulls in dev branches
- missing bindings in QtCore/QtGui/QtMultimedia - work in progress
- clang support done (except for a Mac issue)
- Pyside clang version required Qt 5.7 or later
- PYSIDE-500 done
- work on PYSIDE-500, 502, 504, 497 will continue
- qdoc work started trying to recover whatever documentation is left from Pyside 1.x

16. March 2017

- Coin
- the fixes are still integrating or are under review (no further progress until this is done)
- clang parser replacement PYSIDE-323
- most test failures related to clang are fixed
- tests ran pretty much through on Qt 5.9 (Windows and Linux - Mac not yet verified)
- code cleanups in shiboken
- will create feature branch on all pyside repos to get the clang patch series under CI control
- merges from regular pyside branches into clang branch will commence
- readme required that explains how clang is to be built (if not provided by platform)
- [PYSIDE-331] - in progress

9. February 2017

- Clang progressed
- pure C++ tests for API extractions are passing (C++ parsing based on clang)
- even works with cmake
- old C++ preprocessor still to be replaced
- working through old preprocessor and checking what magic it did and how clang might be able to replace it
- PYSIDE-315 & PYSIDE-462 fixes pending for review
- COIN
- continue progress an getting more platforms to pass (unblocking one step at a time)
- Windows (32bit) and mac are building, Win 64bit still not building
- OSX and Windows are stopping in the test runner phase
- missing cmake update still on Linux (provisioning update required)

26 January 2017

- PYSIDE-315
- principle fix merged but some minor improvements still pending
- Pyside-462
- essentially a feature request as C++ default parameters are not yet supported by Pyside
- discussion ongoing how to address the problem
- COIN
- 10.11, 10.9 & 10.8 build passes
- 10.10 still failing during build
- Progress on Windows and running into new problems further down the path
- Redhat failed to general brokenness of the platform in CI
- Ubuntu no further progress
- clang parser work progressing
- completeness of work is currently measured by passing unit tests
- there is a long way to go
- see PYSIDE-323 and associated patches for progress monitoring
- Fixed regression which prevented Pyside to compile with Qt 5.5.1
- shared pointer support
- no update on 2nd February 2017 (next week)

19 January 2017

- PYSIDE-315
- a possible fix is pending, some minor performance improvements are still possible
- caused by different signal/slot ordering in Qt4 and Qt 5
- COIN
- issues on 10.8 and 10.9 platforms should pass now
- 10.11 & 10.10 still have issues
- Windows timeout problem fix in COIN (but no COIN update until 5.8.0 released)
- Linux builds are failing
- Ubuntu 14.04 fails due to cmake issue
- Redhat 6.6 & OpenSuse 13.01 deferred
- current COIN freeze for 5.8.0 release affecting patching of COIN for Pyside
- next steps in priority -> run tests on 10.8/10.9 and get Linux running
- PYSIDE-79 regression fixed as well (some interaction between PYSIDE-315 & PYSIDE-79)
- PYSIDE-462 to be looked at next
- clang parser work progressing

12 January 2017

- PYSIDE-315
- sorting of slots/signal connection changed on Qt side and Pyside side has not caught up
- had similar connection issues on the QML side, need to investigate whether there is a connection
- PYSIDE-79
- caused a regressions (not yet investigated)
- fixed OpenGL types not being recognized on MacOS (partly fixed)
- API's with shared/smart pointers in Qt don't work
- has potential long term effects and investigation has started into the reasons
- Refactoring shiboken in preparation for clang
- COIN currently runs tests with namespaced Qt
- short term fix to exclude namespaced Qt builds with Pyside (broken on MacOS 10.9)
- other failures: missing libraries on MacOS (10.11), missing provisioning on Windows, cmake issues on 10.10
- unknown state on Linux (current Redhat too old)
- Prioritization after status round:
- PYSIDE-315 to be investigated based on recent signal/slot patches for QML
- Smart pointer issues reduced in priority to provide space for PYSIDE-315 & PYSIDE-79 regression
- verify that COIN runs testrunner (not just building Pyside)
-> not yet verified since we are still failing builds in COIN

5 January 2017

- COIN update
- COIN changes merged (no further patches pending)
- need to run an integration test
- issues related to different build platforms still to be expected
- Continue with clang
- backtracking a bit (reusing some node API's during parsing but otherwise use clang to populate the tree)
- test blacklisting reviewed (some removed - mostly signal related ones, one new regression)
- regressions in QtQuick were worked around (caused by recent Qt Quick changes)
- issues with macos framework style includes in Qt
- PYSIDE-315 debugging ongoing, very hard to track down
- was it a regression from a previous Pyside release (e.g. Qt 5.4?!?
- hard-copied Qt 5.4 based headers still in existence
- updated needed but would shut Qt 5.4 users out

1 December 2016

- COIN
- PYSIDE-79 there seems to be a final work around (https://codereview.qt-project.org/#/c/176374/)
- fixing a few tests in the process
- clang update
- dumping AST, identifying the required info
- work in progress...
- problems with global static QObjects on the Qt side calling back into Python during app exit
- may require some changes on the Qt side

24 November 2016

- automatic COIN triggering for submodules work in progress
- several discussions on this topic this week
- Clang investigation (what library to use)
- fixing bugs on Qt side for Pyside
- Qt QML support almost done, work will continue with Qt Quick
- PYSIDE-79 work story continues
- reference counting not quite accurate but point of deallocation of ref count not identifiable

17 November 2016

- Pyside team suffering from sickness -> not much progress this week
- Pyside-79 fix had a lot of negative side effects (breaking existing tests)
- internal object reference counting is the predominant issue at hand
- continue to work on the bug (no resolution yet as delayed due to sickness)
- COIN some progress but still open discussions on branching policy required

11 November 2016

- PYSIDE-79 being fixed
- PYSIDE-315 to be addressed
- Shiboken and Clang
- familiarizing with clang and its parser's inner working
- added experimental qmake project definition for shiboken (makes work in Qt Creator easier)
- Qt QML on Pyside work progressing
- work on COIN did not progress due to conflicting priorities inside COIN development

3 November 2016

- working through the QML stack esnuring all required API's are exported (https://codereview.qt-project.org/#/c/175682/)
- small build system patches
- PYSIDE-79 work progressing
- OpenGL support fixed (PYSIDE-314)
- COIN issues
- repo interdepencies not working yet, suggestion under discussion and to be implemented
- most license checks have been fixed
- Qt 5.6 based Pyside to skip check
- after branching for C++11 work the dev branch should work from license check perspective
- eventually the entire CI needs to run through (more hidden problems could be hidden)
- Started working on C++11 compliant parser for shiboken
- libclang will be used
- first target is to replace the AST tree implementation
- requires clang setup in the CI

27 October 2016

- Work on WebKit/WebEngine support
- Further work on COIN support
- Planning meeting
- Workshop for C++11 support in Pyside (PYSIDE-323)

20 October 2016

13 October 2016

- Qt CI update
- Coin changes have merged but integration not yet working
- Qt CI enables on Pyside side merged
=> COIN integration fails with license issues
=> requires review of license conditions for all files, some files are not even relicensable
=> skipping license check for now, most likely to be done later again but requires changes to license check script
- more issues of interworking between QtCI and Pyside expected (won't be visible until license problems resolved)
Open issue: does a change in Pyside repo trigger a rebuild of everything?
- Qt QML support progressing and first patches merged
- serious bugs have been fixed, more complex QML examples are now working

29 September 2016

- Coin integration close but not merged
- Bugfixing in particular on the shiboken parser side
- QML/Python binding and tests fixed -> general check all day-to-day aspects of QML are working
- QML examples porting
-> still some failing tests
-> Check all QML/Quick class are exported

22 September 2016

- Refactored Shiboken, udnerstanding build sequences
- black list for unit tests defined and tested
- fixing of tests
- QML example fixing continued (QML bindings not working)
- Pyside side for COIN done (pending integration checks)
- COIN integration still wip due to long test and retest cycles
- pyside and shiboken repo to be relicensed similar to other Qt products
=> this should address any issues regarding the status of generated code too

16 September 2016

- Pyside side for CI testing ready for testing
- status of COIN side to be determined. Code exists need help from CI team to confirm status.
- build system infrastructure improvements in pyside setup
- Qt logging now working
- and more
- Update on bug handling
- PYSIDE-88 continuing
- PYSIDE-349 (Multimedia ported)
- PYSIDE-344 fix pending on codereview
- make debug builds of Pyside work (OSX works, Linux has work in progress patch, Windows side awaiting contribution)
- QML support work in progress
- examples are slowly ported with aim to identify bugs

Backlog

The list below represents some short term targets and long term ideas for Pyside2 development. There is no guarantee that this will happen as written down. It is meant as a short reminder and idea collection for future development. In the long term this list is likely to move to https://bugreports.qt.io/browse/PYSIDE.