Improve the installer so that it is automated instead of requiring so many manual steps. Also, develop streamlined release process so that minor releases 2.1, 2.2, etc. can be accomplished more rapidly.
(7) Improve the installer so that it is automated instead of requiring so many manual steps. Also, develop streamlined release process so that minor releases 2.1, 2.2, etc. can be accomplished more rapidly.
This is critical if we want to make more frequent releases. Also, application wide resources that need to be updated with every incremental release should be stored in one module. An ideal candidate would be the Kepler suite module. That way, if a patch occurs, the splash screen and other resources can all easily be updated to reflect the patch. The splash screen should not longer be done in photoshop, but instead a method should be devised such that text indicating the version number is somehow merged with a background image.
#1 Updated by Christopher Brooks about 9 years ago
Does this mean creating an installer or using the installer?
Creating an installer:
Bug 5027: Users should be able to build installers for the Kepler-2.0 branch
Bug 4995: ant installer fails under Linux
("ant installer" should also work under Windows)
End user experience with the installer:
Bug 4989: The installer should offer to start Kepler
Bug 4003: Support for non-GUI Kepler installer
(Some easy, maybe hit the easy parts in 2.2)
Updating the splash screen using Imagemagick is probably possible.
We could also avoid using images that have text in them.