From Fedora Project Wiki

(→‎Websites critical: new section)
No edit summary
 
(One intermediate revision by the same user not shown)
Line 3: Line 3:
== Websites critical ==
== Websites critical ==


If/when this is finalized, RelEng should inform Websites team, so the URLs in the next following iteration of the site templates are written against the naming policy. This was again an issue for F22, because Cloud images all changed location without their knowledge.  So our release had 4 hours where any downloads of Cloud images met with a 404/blank page.
If/when this is finalized, RelEng should inform Websites team, so the URLs in the next following iteration of the site templates are written against the naming policy.


== Websites critical ==
Related issue is directory structure. This was again an issue for F22, because Cloud images all changed location without their knowledge.  So our release had 4 hours where any downloads of Cloud images met with a 404/blank page. Can that be addressed in this policy?
 
If/when this is finalized, RelEng should inform Websites team, so the URLs in the next following iteration of the site templates are written against the naming policy. This was again an issue for F22, because Cloud images all changed location without their knowledge.  So our release had 4 hours where any downloads of Cloud images met with a 404/blank page.

Latest revision as of 18:02, 26 May 2015

Would it be reasonable for the order to be the same as that in the download directories (in other words, something like Fedora-$VERSION-$PRODUCT-$ARCH-$IMAGETYPE)? That's the same order as the old pungi images, for example Fedora-20-i386-DVD.iso. - Robatino

Websites critical

If/when this is finalized, RelEng should inform Websites team, so the URLs in the next following iteration of the site templates are written against the naming policy.

Related issue is directory structure. This was again an issue for F22, because Cloud images all changed location without their knowledge. So our release had 4 hours where any downloads of Cloud images met with a 404/blank page. Can that be addressed in this policy?