The adoption of buildout has aggravated a problem with the
PloneSoftwareCenter: it is very difficult to keep old versions of
product packages online. I have a proposal for a quick fix.
Background
PloneSoftwareCenter's current presentation of downloadables encourages
authors to delete old sub-versions within a release as they move
forward. For example, if you wish to release a new beta of an unreleased
product version, the natural path is to delete the old beta
downloadable, upload the new beta, then re-release the beta.
Whether or not this was ever a good idea, it's a problem when buildouts
all over the Internet may be trying to pick up the old downloadable.
Quick Fix Proposal
On release pages, PSC currently labels every downloadable with the
current state of the release. Example: "Get ArchGenXML 2.0 (Beta release
5) for all platforms". The author's label for the downloadable (e.g.,
"Product Package") is on the next line.
If we simple eliminate the current state portion of the downloadable's
title (the "(Beta release 5)" in the example), authors would be able to
add the release state to their own label. It would then be more
practical to maintain old sub-version downloadables.
This fix may be applied with one change to one skin template. If there
are no objections, I propose to implement this on Plone.Org right away.
So, if you've reservations or suggestions, respond soon!
Steve
--
______________________________________________________
Steve McMahon
Reid-McMahon, LLC
[EMAIL PROTECTED]
[EMAIL PROTECTED]
_______________________________________________
Product-Developers mailing list
[email protected]
http://lists.plone.org/mailman/listinfo/product-developers