I agree it would be good to not duplicate things for each downloadable artifact associated with a release. Not sure it really needs the day of the release or the assembly spec info either.
And +1 to having old release downloads on a separate page. I'm not sure if this is the proposal but could there be a single download page that has the current latest release of each of SCA, SDO and DAS? ...ant On 5/29/07, Luciano Resende <[EMAIL PROTECTED]> wrote:
My understanding is that you moved the release name and date from the "download section" to the "download table". If they are always same for a group of downloads, won't it take space from the page by repeating it on each table row ? Also, do we want to keep all past releases available on the main download page ? Maybe we could have an separate archive page, and only the latest release available in the main download page, this would encourage people to always use the latest stable stuff ? On 5/29/07, haleh mahbod <[EMAIL PROTECTED]> wrote: > Hi, > > 1) Would [1] be a better format & content for each download page of than > what we have today [2]? > If yes, I'll start upgrading the pages. > > 2) We currently use the same page to record download info for technologies. > For example, SCA Native and Java download pages are the same. > It would be cleaner if we separate the pages. For example, a Java SCA and a > Native SCA download page which gets linked to from a common > download page entry point [3] > Does this seem reasonable? > > > [1] > http://cwiki.apache.org/confluence/display/TUSCANY/Java+SCA+Download+Page > [2] http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Downloads > [3] http://cwiki.apache.org/confluence/display/TUSCANY/Tuscany+Downloads > > > Haleh > -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://lresende.blogspot.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
