[
https://issues.apache.org/struts/browse/SITE-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40065
]
Don Brown commented on SITE-8:
------------------------------
I think so. Some folks put beta software into production, so we should have
accessible docs.
> Website archive handling
> ------------------------
>
> Key: SITE-8
> URL: https://issues.apache.org/struts/browse/SITE-8
> Project: Struts Shared Resources
> Issue Type: Improvement
> Reporter: Ted Husted
>
> We have started to provide archives of past GA releases on the website under
> folders named for the version.
> * http://struts.apache.org/1.2.9/
> We could start creating the versioned folders upfront and then redirecting
> from struts/1.2 to struts/1.2.9, and so forth.
> If we want to do that, then we should setup physical folders for 1.3.5 and
> 2.0.0 and setup the appropriate redirects for struts/1.3 and struts/2.0 to
> the latest versions. Then once each version rolls, we could create the 1.3.6
> and 2.0.1 folders and update the redirects.
> In this way, people could link to Struts/1.3 or Struts/2.0 and be directed to
> the site for the latest working milestone in the each minor series. We could
> also create redirects for Struts/1.x and Struts/2.x to link to the lastest GA
> milestoren for each major release series.
> One issue to consider is what do we do if a version does not go GA. If we had
> been doing this all along, then we would have created a website folder for
> 1.3.1. Would we have kept 1.3.1 around once we decided it was a permanent
> Alpha, or do we delete folders for versions that we know are not going GA?
> If we are careful to constrain the references to a specific version of the
> website, it would be possible to remove "beta" release sites, so that we only
> retain the GA sites over time.
> For background see:
> * http://www.mail-archive.com/dev%40struts.apache.org/msg23359.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
