Improvements on the release Process

1. Installation and Packaging – Presence and Future Dr. Ingo Schmidt-Rosbiegal Project Lead OpenOffice.org Installation Sun Microsystems OOoCon 2009, Orvieto, Italy

3. What is new in OpenOffice.org 3 ?

4. Plans for the Future

6. Was motivated by the support of native installer techniques (Windows Installer, Solaris packages, Linux RPMs, …)

7. Is completely based on OpenSource tools

8. Includes several source code modules

10. setup_native : Helper programs for packaging, CustomActions, S hell scripts, Package defs, ...

11. epm : External helper program, ESP package manager (www.epmhome.org)

12. javainstaller2 : Java GUI Installer for Unixes

13. instsetoo_native : Product definitions and packaging, only module “knowing products”

14. solenv : Perl packaging tooling

15. The Packaging Framework Tooling contains Installation sets Helper programs

16. The Packaging Framework Defining a Product: (3x instsetoo_native, 1x scp2)

17. The Packaging Framework The Meaning of the Properties: -> many switches for the product

18. The Packaging Framework Helper Programs:

19. The Packaging Framework Supported installation set formats:

21. OOo SDK

22. OOo Dev

23. OOo Dev SDK

24. BrOffice.org, also with JRE

25. BrOffice.org Dev

26. URE

27. The Packaging Framework Creating an installation set: A B C

29. Files are unzipped, created (services.rdb, ini-files), changed (Customization), compressed, registered, filtered (Language Packs), …

30. Full support of Windows Installer technology

31. Unix: Pool administration for packages

32. and much, much more ...

34. Java GUI Installer for OOo with JRE (OOo 2.4)

35. Minor Upgrade for Windows 3.0.1

36. Package Pool for Linux rpm and Solaris (increasing packaging performance)

37. Windows: Integration of Windows Installer Merge modules msi database

38. Customization with “extension” folder (Windows)

39. Plans for the Future Two motivations for changes:

41. is responsible for installation, maintenance, update and deinstallation of the product.

42. has to be created for each product individually.

43. needs WI 4.5 concerning to MS -> not for old Windows versions (min. Win XP SP 3)

44. Plans for the Future Idea:

45. Plans for the Future Installation process:

46. Plans for the Future Two kinds of installation: A B

48. Language independent : Java jar file contains all available localizations

49. Platform independent : Java jar file contains all informations about native installer processes

50. Flexible : The number of packages next to the Java jar file has to be flexible -> adding a new OOo language by adding the package

52. Less upload, less redundancies (DLLs, ...).

53. More releases can be made available online.

54. Less download, because module and language selection happens before download starts.

55. QA concentrated on one installation set.

57. Introduction of a Chainer, that supports micro-msi-packages also on older Windows systems.

58. msi databases separated like RPMs. Better modularization and easier development.

59. Micro-msi-packages can be in Pool process.

60. Unique installer appearance on all platforms, but using native installer.

61. Summary The packaging and installation framework was presented and the most visible new features for OOo 3 were introduced. The plan for the future is the consolidation of installation and download leading to a dramatic reduction of installation sets. This can be realized by the Java GUI Installer, that needs to become a Chainer also for Windows msi packages.

62. Installation and Packaging - Presence and Future Dr. Ingo Schmidt-Rosbiegal [email_address]