Hi, I propose changing the release plan as follows. Please let me know what you think
Major point: *1.6 should be named 2.0*, since we have API changes: - Configure will go - pyinstaller.py will come - Analyse() will get arguent `hidden_imports` - _mounzzlib, unicode and _useTK et al. will vanish Here is my proposal for feature planning: *Features for 2.0* - see above - eliminate config.dat etc. - PyInstaller home should be "read only", this is: no files are written there - binchache is going to $HOME/.... (already implemented, but need to be changed) *Features for 2.1* - time-stamp (ans maybe checksum) based cache (at least for bincache) - find import in extension modules (this would allow some hooks to be removed) - can be installed using setuptools/easy_install/pip - infos about how to package as an rpm (ReadMe-Pacakgingg.txt) - idea, internal: use Python zlib instead of own copy *Features 2.5* - support for Python 3k - we may need to drop support for Py 2.3 any 2.4 *Features 3.0* (currently "2.0") - Cover the distribution phase of installation: build an installer wizard on Windows (through InnoSetup/NSIS), a DEB/RPM for Linux and a DMG for Mac. - for GTK+ automatically package all other stuff (pang0, icons, etc.) - same for other complex bundels *Schedule* Since we made considerable progress last month, I propose a staight schedule: 1.5.2: 2011-12-31 (already planned for this release) 2.0: 2012-03-31 2.1: 2012-06-30 2.5: 2012-09-31 3.0: 2012-12-31 -- Schönen Gruß - Regards Hartmut Goebel Dipl.-Informatiker (univ.), CISSP, CSSLP Goebel Consult Spezialist für IT-Sicherheit in komplexen Umgebungen http://www.goebel-consult.de Monatliche Kolumne: http://www.cissp-gefluester.de/ Goebel Consult ist Mitglied bei http://www.7-it.de
smime.p7s
Description: S/MIME Cryptographic Signature
