Hi,
when preparing the next board report I was wondering what to write about our
plans for the next release.
I guess it's obvious that sooner or later we will go for a 2.x release. The
major release may include the following
- merge/replace Jempbox/Xmpbox
- remove deprecated stuff
- move to java6 as minimum requirement
- switch to the (completed?) conforming parser as default
- ....
IMO we have different options how to do that:
1.
Release a 1.7.x version based on the current trunk. Start with the major release
using the current trunk.
pros:
- new feature release after 9 months
- 1.7.x release without much effort
- enough time for the major release
- ...
cons:
- 2 XMP libs
- unstable conforming parser
- ...
2.
Choose a couple of improvements/fixes from the trunk and apply them to the 1.6
branch and release a 1.6.x bugfix or a 1.7.0 feature release. Start with the
major release using the current trunk.
pros:
- new feature/bugfix release only with chosen features/fixes
- enough time for the major release
- no unstable conforming parser, as it wouldn't be part of the release
- ...
cons:
- 2 XMP libs (if we would do a 1.7.0 release including preflight)
- a lot of discussion on what will be part of the release and what won't be
- a lot of work to create the release compaired to alternative 1
- ...
3.
Drop all 1.6.x/1.7.0 plans and start with the major release using the current
trunk.
pros:
- we wouldn't have to spend time on a 1.6.x/1.7.0 release
- ...
cons:
- too much time without release
- too less time to work on the new major release, because of con 1
- ...
I prefer option 1, what do you think?
BR
Andreas Lehmkühler
