-
Notifications
You must be signed in to change notification settings - Fork 71
Make Release
Johan Brichau edited this page Oct 25, 2018
·
4 revisions
Release Early. Release Often
- Update the version number of Grease/Seaside in the code
- GRPlatform >> #version
- GRPlatform >> #seasideVersion
- Test the release
- Run the unit tests and make sure they all pass. (This is done using Travis-CI)
- Click through the functional test suite using the all server adaptors and all different encodings.
- Update the Metacello config [TODO: needs updating]
- see
ConfigurationOfSeaside3 >> #DevelopmentProcess
- see
ConfigurationOfGrease >> #DevelopmentProcess
- Load
Package-Dependencies
andGraphViz
fromhttp://source.lukas-renggli.ch/packaging
. Generate the graphWADevelopment graphFunctionalDependencies: true tests: true
and make sure the dependencies are valid. [TODO: still valid?] - Prepare a list of resolved issues.
- Upload image/changes in a ZIP and one-click distribution to website
- locally under
/srv/seaside.st/web/distributions
- update links
http://www.seaside.st/download/pharo
http://www.seaside.st/design/parts/download
- Announce the release in the mailing-list and on twitter.
- Update Past Releases.
- Update and fix this list.
- Repeat forever.
Changelogs
- (newer changelogs, see https://github.com/SeasideSt/Seaside/releases)
- 3.4.0
- 3.3.0
- 3.2.4
- 3.2.2
- 3.2.1
- 3.2.0
- 3.1.3
- 3.1.2
- 3.1.1
- 3.1.0
- 3.0.11
- 3.0.9
- 3.0.8
- 3.0.7
- 3.0.6
- 3.0.5
- 3.0.4
- 3.0.3
- 3.0.2
- 2.8
- 2.7
- Past Releases
Development
Documentation
- Configuration and Preferences
- Embedding Subcomponents
- Maintaining State
- Generating HTML
- CSS and Javascript
- Debugging Seaside Applications
- Links, Forms and Callbacks
- Development Tools
- Call and Answer
- Naming URLs
- Security Features
- Securing Seaside Applications
- Seaside-REST
- Add-On Libraries
- Persistence
- Gettext
- FileLibrary
- The Render Tree
- PDF Generation
- Long-Term Issues
- Ajaxification
- Web Components
- Big Issues
Sprints