[
https://issues.apache.org/jira/browse/YETUS-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey updated YETUS-163:
------------------------------
Attachment: YETUS-163.0.patch
-00 first pass
- use middleman data file for releases
- generate a download blurb for each release
- download link to docs in header for each release
with this in place as-is, the site should look the same because the given data
file for releases has none.
These changes would work with a "publish release" process that is essentially
- release notes are made during RC generation in
asf-site-src/documentation/in-progress/release_notes.md
- publish release source/bin artifacts to dist
- publich documentation/in-progress generated from release tag to asf-site repo
at documentation/%VERSION%, e.g. documentation/0.1.0
- update data/versions.yml on master
- publish site
example of what data/versions.yml will need for the 0.1.0 release:
{code}
diff --git a/asf-site-src/data/versions.yml b/asf-site-src/data/versions.yml
index 30e78e8..dbb8f98 100644
--- a/asf-site-src/data/versions.yml
+++ b/asf-site-src/data/versions.yml
@@ -15,3 +15,4 @@
# specific language governing permissions and limitations
# under the License.
releases:
+ - 0.1.0
{code}
> parameterize site for releases
> ------------------------------
>
> Key: YETUS-163
> URL: https://issues.apache.org/jira/browse/YETUS-163
> Project: Yetus
> Issue Type: Improvement
> Components: website and documentation
> Affects Versions: 0.1.0
> Reporter: Sean Busbey
> Assignee: Sean Busbey
> Priority: Blocker
> Attachments: YETUS-163.0.patch
>
>
> our site needs to handle having releases, i.e. downloads and version specific
> documentation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
