#304: Create new pre-release pages for getfedora.org
-----------------------+------------------------
Reporter: robyduck | Owner: webmaster
Type: task | Status: new
Priority: blocker | Milestone: ASAP
Component: getfedora | Resolution:
Keywords: | Blocked By:
Blocking: 305 |
-----------------------+------------------------
Changes (by robyduck):
* blocking: => 305
* priority: major => blocker
* cc: jreznik@… (added)
Comment:
I've created the f22-alpha branch and all changes should be committed
there. It's the first time we'll go through the pre-release process with
getfedora.org, so before we add the usual things we need to create new
pre-release pages, decide if and where to place the Alpha banner and also
add a pre-release checksum page.
I'm still not sure if we should have a similar JS checksum as for final
images, my idea would be to have a simple checksum/verify page for pre-
release images where people can pick up the checksum.[[br]]
Pre-release pages whould be three, one per product we can link from the
sidebar of the download page, layout could be pretty the same (just
adapting it to the new layout) we used to have with
fedoraproject.org.[[br]]
Finally, if we want to run the schedule and display the the day of the
next pre or final release, we have to reactivate our schedule script. It
has been already tested, but we dropped it before releasing F20 because it
was a bit slow. So, this need also some improvement.
Once we have these basic steps we can continue with the normal Alpha
release process. Websites should be ready in a month from now, so we have
4 weeks to have this ready. Please code pages with variables, this will
help us for Beta.
I'm tagging this ticket as blocker of #305, don't forget we have also
spins.fpo ;)
--
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/304#comment:1>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance
--
websites mailing list
websites@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/websites
