I saw a lot of @removal(4.2) and hence I've asked. I would now update those to @removal(5.0).
My problem with cleaning up our technical debt is, that this often affects also the API and needs to be done on the major version change. In the other hand we like to have a stable API for a longer period. I guess the key to solve this, is a better branching method. So we can clean up while the minor versions are updated/back ported. As I'm only a very casual GIT user, I would need some lessons on how to do it effectively. With SVN feature branches and a parallel development this will be more effort, which I like to avoid. If GIT is the answer to such problems, we could vote about it and eventually check with INFRA to switch the repo. Andi. -- Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org For additional commands, e-mail: dev-h...@poi.apache.org
