Skip to content

Commit

Permalink
A few addition and corrections to readme
Browse files Browse the repository at this point in the history
  • Loading branch information
rwbaer authored and Joel Palmius committed Apr 5, 2017
1 parent b21b1b5 commit 5183753
Showing 1 changed file with 9 additions and 8 deletions.
17 changes: 9 additions & 8 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,18 +1,19 @@
# makehuman_stable_python3

This is now a near viable to backport of the current MakeHuman 1.1.1 stable branch to a python3 dependency. The port
includes support for the pyside binding to QT4. This late addition recognizes the end of availability of the pyQt4 Python binding from Riverbank, and it allows testing proceed. However, the intention is ultimately to move to QT5 support as final bugs are fixed.
This is now a near viable backport of the current MakeHuman 1.1.1 stable branch to a Python 3 dependency version. The port
includes support for the pyside binding to QT4. This late addition recognizes the end of availability of the pyQt4 Python binding from Riverbank, and it allows testing to proceed. However, the intention is ultimately to move to QT5 support as final bugs are fixed.

The testing vision for this code is to build a community release that includes the ported code and often-used, user-contributed
plug-ins. We hope that the utility of this integrated functionality is sufficient to entice a larger cohort of testers who get
value-added in exchange for the possibility of uncovering deficiencies in our port. When testing verifies it's robustness it should
a suitable replacement for the current bitbucket code extending the future of MakeHuman beyond the Python 2 "end-of-life".

The testing vision for this code is to build a community release that includes the ported code and often-used user-contributed
plug-ins. The utility of this integrated functionality is hoped to be sufficient to entice a larger cohort of testers who get
value-added in exchange for the possibility of uncovering defficiencies in our port.

## Branches

There are four branches and some working developer branches:
There are four standard branches and some additional developer working branches:

* master: At the time of creating the repo, this is the same code as in bitbucket-stable. Master is the branch is the branch
representing canonical development.
* master: At the time of creating the repo, this is the same code as in bitbucket-stable. As changes have been made to bitbucket-stable they have been periodically merged with this code. Master is the branch representing canonical development.

Reference branches
* bitbucket-stable: This is the code as it looks right the stable branch at bitbucket
Expand Down

0 comments on commit 5183753

Please sign in to comment.