Ivy is a flexible tool and also the release process can be tuned according
to your own needs.
Personally, I think that you should not try to copy the "release process"
used in the maven world.
I believe more in a continuous build process where builds are promoted to
releases when they have been
We are searching for a best practice documentation about the release process of
an IVY module like described here [1]. For us it is quite important to produce
reproducible builds with all dependencies of the release build. For that, we
have to push the resolved IVY descriptor in the SCM system
