This List is a incomplete collection of tasks bugs and Management Points that needs to be developed. The Goal is to achieve a better transparency what to work on. There is no Priorization on this list or time scope.
Generic Project Tasks
- Documentation of the 2 VMs
- Migration of VMs
Release 4.2.0
- Test organization
- 4.2.0 - dev issues
- Document Consent
- Setting up JIRA with Kanban
- Writing up a Kanban Guide
- Define a timeframe after review occurs
- Define acceptance / success criterias - Peter Kovacs
Build Enviroment
- Build with SCon
- Create a master program to replace the current build.pl script (still using dmake and make) - Peter Kovacs
- transformation function for dmake
- transformation function for make
- pootle/language integration
- integrate the handle of idl files
- adding code signing infrastructure
- dependency tracer
- Create a master program to replace the current build.pl script (still using dmake and make) - Peter Kovacs
- generic improvments
Something else to consider is that it would be nice to use a different value of $COM for Apple's clang, maybe "ACLANG" or "APPLECLANG" since it has a different version numbering scheme that the open-source version of clang and having a unique identifier would simplify version checking when applying compiler bug workarounds.
- test modification on Mac and OS/2
If you have an existing, populated build tree, then the most important tests can be done without even doing a build. Start off by copying the *env.set.sh script and solver/420/*/inc/comp_ver.mk to a safe location. Next apply the patch below, run autoconf, and then run configure. Compare the values of $COMNAME, $COMID, $CCNUMVER, and $CCVER from the new *.env.set.sh with the values of those variables from the saved copy of comp_ver.mk. Also compare the values of $COM in the new and saved versions of *.env.set.sh.
Note: I think the old value of $CCNUMVER on the Mac is wrong. It should look something like 000800010000 or 000700030000, depending on the installed version.
Recruiting
- write a guide how to debug build results
- write a guide how to get started with development
Code Documentation
Microsoft Windows next steps (Discussion)
- upgrade from MSCV2008 (to newest possible; keep WinXP compatibility for now, to keep support for ReactOS
- Upgrade to Java9 (keep Win32 with Java 8 for now)
- Windows 64 transformation
- MSI update version
- complete MSI updater
- create a new installer with Wix?
MacOSx next Steps
Code health
- risky code string [strlen(string) - 1]
- inspect and update Array code
Bugs
- soffice bin 100% CPU in linux in headless mode?
- Base crashes with macro autoexec
- Bizarre font size input filter behavior
- better html filter
- copy&paste
- Printing issues
- Print preview and incorrect margins
- with result in crashes or freezes
- OpenOffice Crashes when Printer Information is part of the document Mention on Forums
- OpenOffices freezes on Print
- Calc will duplicate the content of MS excel file cells which have line breaks
- crashes and freezes
- doc format related issues
Features
- OOXML integration
- multimedia Gstreamer backend
- update to gstreamer 1.0 API
- Document the stuff
- CentOS6 is to old. Does not support gstreamer 1.0. How do we handle this?
Task report
Looking good, no incomplete tasks.