----- Original Message -----
From: "Tim Flink" <tflink(a)redhat.com>
To: qa-devel(a)lists.fedoraproject.org
Sent: Friday, September 23, 2016 12:09:56 AM
Subject: RFC: URLs for docs and released bits from CI
I submitted a revision today which makes some slight modification to
how the doit.py script is building docs, rpms and tarballs.
https://phab.qadevel.cloud.fedoraproject.org/D1012
My intention is to get this deployed to a non-staging setup soon but I
wanted to reach out to see if anyone had an issue for the URLs that
would end up being used.
https://baseurl/docs/<projectname>
This path would contain docs for <projectname> built per branch for
non-master branches and per-release-version when triggered on the
master branch. The 'latest' symlink will always be updated to point at
the most recent build on the master branch
https://baseurl/releases/<projectname>
Pretty much the same thing as for docs but with the rpms, srpms and
tarball(s) created during the CI build.
Does this seem sane to everyone? Any comments/questions/suggestions? I'd
like to get the auto-docs functionality deployed soon - hopefully right
after F25 beta freeze is over.
Just wondering if URLs would looked better like this:
https://{docs,releases}.baseurl/<projectname>
(assuming there's no technical issues with that).
Other thought I have is to have a index page at
https://docs.baseurl/
which would contain links to various project's version of docs. But
I am hesitant as to how worth is it to spend time on it, so having
apache default file listing might be good enough.
Either way, the proposed URLs and directory structure look sane to me.
Thanks,
Martin