Details
-
Improvement
-
Resolution: Fixed
-
Major
-
3.0 Beta 1
-
None
-
None
Description
Currently I have to proceed multiple steps before releasing manually. Even if the maven release plugin helps a lot.
Following the log:
- update the license.xml in the core jar (could be done by a filter)
- update the license.txt file and the release.txt
- date
- version number
- magnolia.properties --> set magnolia.develop=false
- bind name in repositories.xml must differ for the plublic war
- bootstrap the war (magnoliaAuthor, magnoliaPublic)
- default changes (not yet bootstapped)
- activation port is 8081
- secure /.magnolia/*
- default /features.html
- cache (switch on)
- set admin flag false
- delete the war files
Checklists
Acceptance criteria