what is currently missing for a release is finalizing conversion to feature
model - using natively FM, still a couple of thinks that are not done -
archetype, documentation, docker images -
https://cwiki.apache.org/confluence/x/RBgRCQ
creating sling releases in the current approach takes a considerable amount of
time and involves a lot of manual steps
we should not wait until more feature that are currently in progress are ready,
would be nice to have out Sling 12 soon
the discussion then did go further whether we should rethink the way of doing
sling releases in the future:
- should we still perform releases this way?
- JavaDoc generation should be decoupled from our annual releases, should be
done automatically and updated for each module release
- probably we could just do with "snapshot releases" / "nightly builds" - and
vote from time to time to make an official release out of it?
- Should we replace the Sling Starter release with a "release generator" web
page that allows the user to download a project? For instance:
Scripting: [ ] jsp, [ ] htl, [ ] freemarker, [ ] thymeleaf
Discovery: [ ] standalone, [ ] oak
Persistence: [ ] Tar, [ ] MongoDB
Launcher: [ ] feature model, [ ] karaf
- We have two launcher alternatives - Feature Launcher, Kickstarter. We should
only keep one.
