Hi everyone,
... I'm currently doing some cleanups in our SVN repositories. For those
who don't know: when we do releases then one part of it is handling all
necessary tasks in Git (like creating release branches, tagging etc.),
but we also upload the release artificats (compiled binaries and
sources) as tar.gz files to Apache's Subversion servers (actually twice,
there's a staging area for review and a release area for final release).
Within 24h (more or less) a release gets automatically archived and is
available at https://downloads.apache.org. The versions we have backed
up there go back to version 0.4.0-incubating. On every new release we
have to checkout these two SVN repositories (staging, release) which can
be a bit annoying, because the artifacts stored there are quite big
(several hundred MBs). According to the official rules
(https://infra.apache.org/release-distribution.html#archival) we
can/should only keep the releases that we currently support (which would
be 1.8.4 and 1.7.3... note: to be released within 24h). I've started to
remove the deprecated release artifacts to make the release process
faster. So far, so good.
In SVN we have a couple more release artificats that date back to our
transition from Mifos to Apache, but were not yet archived (either,
because the mechanics were not yet in place at Apache or because of the
incubating status of Fineract, doesn't really matter). My question now
is if we should/have to keep those very early release artifacts for any
(nostalgic?) reason? Again, the archived versions go back to
0.4.0-incubating and our Git repository has release tags going back to
version 1.0.0 (which was the release that made Fineract a top level
project).
The versions affected would be:
- 0.1.0-incubating
- 0.1.1-incubating
- 0.1.2-incubating
- 0.3.1-incubating
- 0.3.2-incubating
What do you think? Keep them or drop them? My take would be to ditch them...
Please let me know what you think.
Cheers,
Aleks
