Hi,
Is what's in JIRA representative of the next release? Just wanted to
make sure that what's there actually gives users some idea of what's
coming up.
Also, I feel that the version should go back to alpha. Archiva is
simply not even close to being beta software and misrepresents it's
stability in operation and its API. It simply falls apart constantly
on the central repository. There's something seriously wrong with it.
The we have some serious API issues and design problems like:
- having the reporting coupled to the discovery
- the reporting API is completely incomprehensible: Report,
ReportingDatabase, ReportExecutor, ReportingMetadataFilter,
ReportGroup, ReporterProcessor, ReportingStore. It should not be that
complicated
- we nothing for scalable indexing and distribution of indices
critical for many applications like IDEs
- scanning continually just does not scale and is not required (up
coming proposal for something i call ArtifactReceptors)
So I'm all for more releases, lots of folks need Archiva but it has
to go back to alpha. I will -1 any releases as a beta until, at a
bare minimum, these issues are resolved. We can't flog this off to
users at beta software. That's just wrong.
Jason.
