|Re: [mmt-dev] QVTo downloads cleanup|
I've moved downloads/m2m/qvtoml to /home/data/httpd/archive.eclipse.org/mmt/qvto but die to a permissions problem (https://bugs.eclipse.org/bugs/show_bug.cgi?id=381977) many of the source files have not been deleted.
I've created an extras-qvto.php so that old releases appear as archives.
In order to make the archives downloadable I had to replace most of the index.php files by the one from the 3.0.0 release, moving the old index.php to saved.index.php first.
The older index.php had smart layout that did not relocate to archive.eclipse.org. The 3.0.0 index.php is a simple directory listing.
In the archives area I have pushed the current releases down below a zz sub-folder, awaiting your ok to delete it.
In the downloads I have pushed the archived releases down below a zz sub-folder, again awaiting your ok to delete it.
I have updated about four Portal entries, so QVTo now consistently uses downloads/mmt/qvto, which now looks plausible, but:
3.1.1M4 is, I think, really 3.2.0M4 and so can just deleted as obsolete compared to RC1 and RC3.
3.0.1 has a maintenance build a little after 3.0.1. This is confusing to me and other users. Is it 3.0.1a? Is it a practice? Is it superseded by 3.1.0? Anyway it appears on the download page to allow the user to make a difficult decision.
2.0.1 similarly has a maintenance build a little after 2.0.1. The archive display script is not keen on two 2.0.1 entries, so it's not visible. What needs to be done here?
mmt-dev mailing list
Back to the top