Hi Venkat, It looks like we posted a response to Ant's message at the same time and missed each other's email and my changes show up on the site. Is the flow of information OK?
Basically the old releases page linked to from the .90 page would be the page that you have suggested. Haleh On 5/31/07, Hernan Cunico <[EMAIL PROTECTED]> wrote:
Done! Cheers! Hernan Hernan Cunico wrote: > I'll run a manual autoexport to fix it. > You should see the changes in about 2 mins > > Cheers! > Hernan > > Luciano Resende wrote: >> Why it shows in [1] and not in [2] ? >> >> [1] http://cwiki.apache.org/TUSCANY/home.html >> [2] http://cwiki.apache.org/TUSCANY/ >> >> >> On 5/31/07, Venkata Krishnan <[EMAIL PROTECTED]> wrote: >>> I've changed the home page to include a box highlighting the latest >>> releases. Let me know if it seems ok >>> >>> - Venkat >>> >>> On 5/31/07, haleh mahbod <[EMAIL PROTECTED]> wrote: >>> > >>> > I made the following updates: >>> > Tuscany Download page, 'SCA Java' is linked to [1] >>> > on [1], Other release DOWNLOAD is linked to the old Java SCA >>> Download page >>> > (old releases) >>> > >>> > To do: >>> > [1] could be renamed to SCA Java Latest Release. This page could >>> always >>> > hold >>> > info about the latest release. >>> > [2] could be renamed to SCA Java previous Releases. >>> > [2] needs to be updated to the format that we discussed earlier on >>> this >>> > thread >>> > >>> > If this looks OK, I go ahead and make the changes for the 'to do' >>> list. >>> > >>> > >>> > [1] >>> > >>> > >>> http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Java+0.90-incubating >>> >>> > [2] http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Downloads >>> > >>> > >>> > On 5/31/07, ant elder <[EMAIL PROTECTED]> wrote: >>> > > >>> > > Ok, I've added a new download page for the SCA Java 0.90 release >>> which >>> > > hopefully isn't to far away from whats been talked about: >>> > > >>> > > >>> > > >>> > >>> http://cwiki.apache.org/confluence/display/TUSCANY/SCA+Java+0.90-incubating >>> >>> > > >>> > > Its not linked to from anywhere yet as I'm not sure after all this >>> > > discussion where to put it. The main things I think would be good >>> are to >>> > > not >>> > > have to click through many links to get to the actual download >>> link for >>> > a >>> > > latest release and for it to be quite obvious what the current >>> latest >>> > > release is of something and its not obscured that with lots of old >>> > > download >>> > > links. >>> > > >>> > > I wondered if the download page pointed to from the "General" >>> menu box >>> > > could >>> > > be expanded to have links to each of the current download pages >>> (the >>> > > above >>> > > SCA+Java+0.90-incubating etc) and at the bottom another link to a >>> page >>> > > with >>> > > all the old downloads? >>> > > >>> > > ...ant >>> > > >>> > > On 5/30/07, Venkata Krishnan <[EMAIL PROTECTED]> wrote: >>> > > > >>> > > > Hi >>> > > > >>> > > > What we are attempting to do now it really far better than >>> cluttering >>> > > all >>> > > > the downloads together on one page. Here is what I think about >>> this >>> > > > >>> > > > - for every Release (SCA / SDO / DAS) have a separate page >>> whose first >>> > > > section talks about what comprises of that release (including spec >>> > > levels >>> > > > etc.) and then have a next section that is titled 'Downloads'. >>> > > > - then have a single page titled 'Releases' where we list all the >>> > > releases >>> > > > and each entry is a link to the separate Release page. Here >>> again we >>> > > > could >>> > > > choose to have SCA Releases, SDO Releases, DAS Releases on >>> diff. pages >>> > > or >>> > > > just have all in one under diff sections. >>> > > > - Finally from the global home page and the home page of the >>> > subprojects >>> > > > have a menu item 'Releases' that will point to the 'Releases' >>> page. >>> > > > >>> > > > This way, with every release we simply have to go an make the >>> specific >>> > > > release page and add a link to the Releases page. I had >>> created a >>> > > > Release >>> > > > page for the recent SDO Release without the Downloads section >>> > > > though. Here >>> > > > it is just for people to get an idea of what I mean >>> > > > >>> > > > >>> > > >>> > >>> http://cwiki.apache.org/confluence/display/TUSCANY/SDO+Java+1.0-incubating-beta1 >>> >>> > > > >>> > > > When creating these Release pages my request is that we >>> maintain the >>> > > page >>> > > > hierarchies. For example the release page for the SCA 0.90release >>> > > should >>> > > > be >>> > > > added under Home->SCA Overview->SCA Java->Releases->SCA 0.90 >>> Release. >>> > > > >>> > > > By the way there is a SCA Java and a SCA Java Subproject page - >>> can we >>> > > > merge >>> > > > these two into one. >>> > > > >>> > > > Thanks >>> > > > >>> > > > - Venkat >>> > > > >>> > > > On 5/30/07, haleh mahbod <[EMAIL PROTECTED]> wrote: >>> > > > > >>> > > > > I am including tuscany-users to get their opinion if interested. >>> > > > > >>> > > > > Here are my thoughts influenced by your comments :) >>> > > > > - Separate the download information for latest release from >>> the old >>> > > > > releases. >>> > > > > - Having the text of the change file/read me on the front >>> page of >>> > the >>> > > > > download page is good. This makes it easier to identify what >>> is in >>> > the >>> > > > new >>> > > > > release. So, added a section called 'what's new in this >>> release'. >>> > > > > - It is good to have download information for at least the >>> back 2 >>> > > > > releases. >>> > > > > >>> > > > > - It is useful to know what level of spec is supported by each >>> > > release. >>> > > > > For >>> > > > > example, for SCA there are several specs. A release can be at >>> > Assembly >>> > > > > 1.0level and an older version of Client spec. >>> > > > > - Having a page that takes user to all the downloads[2] is >>> good. >>> > > > > - Having a download page per subproject is good since the >>> audience >>> > > for >>> > > > > each >>> > > > > download page may be different. For example, someone using >>> SDO may >>> > not >>> > > > > necessarily want to download SCA. >>> > > > > >>> > > > > Here is an attempt for a sample download page which incorporates >>> > your >>> > > > > feedback [1] >>> > > > > User will reach[1] from [2] (not linked yet) >>> > > > > >>> > > > > [1] >>> > > > > >>> > > > >>> > > >>> > >>> http://cwiki.apache.org/confluence/display/TUSCANY/Java+SCA+Download+Page >>> >>> > > > > [2] >>> > > http://cwiki.apache.org/confluence/display/TUSCANY/Tuscany+Downloads >>> > > > > >>> > > > > Does it look OK? >>> > > > > >>> > > > > >>> > > > > On 5/29/07, Luciano Resende <[EMAIL PROTECTED]> wrote: >>> > > > > > >>> > > > > > The idea of a single download page sounds good, but if we are >>> > > thinking >>> > > > > > about tracking page visitors to correlate to the number of >>> > > downloads, >>> > > > > > we won't be able to identify if the person is visiting the >>> page to >>> > > > > > download SCA, SDO or DAS. >>> > > > > > >>> > > > > > On 5/29/07, ant elder <[EMAIL PROTECTED]> wrote: >>> > > > > > > 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] >>> > > > > > > > >>> > > > > > > > >>> > > > > > > >>> > > > > > >>> > > > > > >>> > > > > > -- >>> > > > > > 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] >>> > > > > > >>> > > > > > >>> > > > > >>> > > > >>> > > >>> > >>> >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
