[fedora-websites] #267: Prepare websites for F21 Alpha release

[fedora-badges]

#267: Prepare websites for F21 Alpha release
-----------------------+-----------------------
  Reporter:  robyduck  |      Owner:  webmaster
      Type:  task      |     Status:  new
  Priority:  major     |  Milestone:
 Component:  www.fp.o  |   Keywords:
Blocked By:            |   Blocking:
-----------------------+-----------------------
 We are moving towards Fedora 21 Alpha and this time we will have some more
 changes on the webpages, although we will '''NOT''' switch to the
new
 layout for prerelease versions. So, as for the other Alpha releases we
 need to:
 * Add Alpha banner
 * change globalvar.py accordingly
 * add checksums
 * check DL links

 The release schedule actually doesn't have a release date, it's still
 ''not earlier than August 5th'', so our script for the the upcoming Beta
 and GA release dates probably will not work properly.

 Remember the images will not be the same as for F20: we will have 3
 prodcucts and accordingly we should keep only 3 jquery tabs, without
 preferring any product on the main get-prerelease page.

 Server WG asked and obtained a different deadline for Alpha release, that
 means we need to keep in mind Server will be released later than Cloud and
 Workstation.

-- 
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/267>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance

[fedora-badges]

#267: Prepare websites for F21 Alpha release
----------------------+------------------------
 Reporter:  robyduck  |       Owner:  webmaster
     Type:  task      |      Status:  new
 Priority:  major     |   Milestone:
Component:  www.fp.o  |  Resolution:
 Keywords:            |  Blocked By:
 Blocking:            |
----------------------+------------------------

Comment (by robyduck):

 Branch f21-alpha has already been created.

-- 
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/267#comment:1>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance

[fedora-badges]

#267: Prepare websites for F21 Alpha release
----------------------+------------------------
 Reporter:  robyduck  |       Owner:  webmaster
     Type:  task      |      Status:  new
 Priority:  major     |   Milestone:
Component:  www.fp.o  |  Resolution:
 Keywords:            |  Blocked By:
 Blocking:            |
----------------------+------------------------
Changes (by cydrobolt):

 * cc: summermontreal@… (added)


-- 
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/267#comment:2>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance

[fedora-badges]

#267: Prepare websites for F21 Alpha release
----------------------+------------------------
 Reporter:  robyduck  |       Owner:  webmaster
     Type:  task      |      Status:  new
 Priority:  major     |   Milestone:
Component:  www.fp.o  |  Resolution:
 Keywords:            |  Blocked By:
 Blocking:            |
----------------------+------------------------

Comment (by robyduck):

 F21 primary and secondary keys added.

-- 
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/267#comment:3>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance

[fedora-badges]

#267: Prepare websites for F21 Alpha release
----------------------+------------------------
 Reporter:  robyduck  |       Owner:  webmaster
     Type:  task      |      Status:  new
 Priority:  major     |   Milestone:
Component:  www.fp.o  |  Resolution:
 Keywords:            |  Blocked By:
 Blocking:            |
----------------------+------------------------

Comment (by cydrobolt):

 F21 Alpha status added to globalvars.py.

-- 
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/267#comment:4>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance

[fedora-badges]

#267: Prepare websites for F21 Alpha release
----------------------+------------------------
 Reporter:  robyduck  |       Owner:  webmaster
     Type:  task      |      Status:  new
 Priority:  major     |   Milestone:
Component:  www.fp.o  |  Resolution:
 Keywords:            |  Blocked By:
 Blocking:            |
----------------------+------------------------

Comment (by robyduck):

 Alpha Banner requested with design ticket #331.

-- 
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/267#comment:5>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance

[fedora-badges]

#267: Prepare websites for F21 Alpha release
----------------------+------------------------
 Reporter:  robyduck  |       Owner:  webmaster
     Type:  task      |      Status:  new
 Priority:  major     |   Milestone:
Component:  www.fp.o  |  Resolution:
 Keywords:            |  Blocked By:
 Blocking:            |
----------------------+------------------------

Comment (by robyduck):

 I gave a try at the product overview page and used the new product logos
 there. Sure, we can also use bigger icons or banners, but it's better to
 keep it simple IMHO.

 The link anchors are just CSS, so if we change the splash image please
 check if they are still working the right way.

-- 
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/267#comment:6>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance

[fedora-badges]

#267: Prepare websites for F21 Alpha release
----------------------+------------------------
 Reporter:  robyduck  |       Owner:  webmaster
     Type:  task      |      Status:  new
 Priority:  major     |   Milestone:
Component:  www.fp.o  |  Resolution:
 Keywords:            |  Blocked By:
 Blocking:            |
----------------------+------------------------

Comment (by robyduck):

 Next update here, 4 weeks left to Alpha release date and 3 weeks to
 readiness.

 So the overview page is now done with a sprite image and CSS, product tabs
 have a prominent download box for the main image(s). I guess we won't have
 for all products a 32 bit version, but the solution proposed is flexible
 about this.

 Workstation have a secondary Spins section. I don't know how and where we
 should add the torrent images, maybe we can use the Cloud script and do
 something similar as for EC2 images, with a direct download/torrent and
 64/32 bit selection...

 We also need some text content for the single products, what about asking
 the single WG about it? Alpha banner is almost done, we just need to add
 it. The rest is "after readiness" work (CHECKSUMS, links, images, sizes).

 http://stg.fedoraproject.org is now built against f21-alpha branch.

-- 
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/267#comment:7>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance

[fedora-badges]

#267: Prepare websites for F21 Alpha release
----------------------+------------------------
 Reporter:  robyduck  |       Owner:  webmaster
     Type:  task      |      Status:  new
 Priority:  major     |   Milestone:
Component:  www.fp.o  |  Resolution:
 Keywords:            |  Blocked By:
 Blocking:            |
----------------------+------------------------

Comment (by jreznik):

 One possibility would be use of Mission statements to describe each
 product. But seems like it's not available for Cloud. I'll try to get this
 description, would be nice to let it through marketing, so it sounds cool.

-- 
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/267#comment:8>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance

[fedora-badges]

#267: Prepare websites for F21 Alpha release
----------------------+------------------------
 Reporter:  robyduck  |       Owner:  webmaster
     Type:  task      |      Status:  new
 Priority:  major     |   Milestone:
Component:  www.fp.o  |  Resolution:
 Keywords:            |  Blocked By:
 Blocking:            |
----------------------+------------------------

Comment (by mattdm):

 Replying to [comment:8 jreznik]:
>  One possibility would be use of Mission statements to describe each
 product. But seems like it's not available for Cloud. I'll try to get this
 description, would be nice to let it through marketing, so it sounds cool.

 The mission statements might not be quite right... we need something more
 like "elevator pitches". One or two sentences that grab you.

 We're also working on an API-based system that will automatically update
 the cloud images page with the latest version for different providers.
 More on that RSN. :)

-- 
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/267#comment:9>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance

[fedora-badges]

#267: Prepare websites for F21 Alpha release
----------------------+------------------------
 Reporter:  robyduck  |       Owner:  webmaster
     Type:  task      |      Status:  new
 Priority:  major     |   Milestone:
Component:  www.fp.o  |  Resolution:
 Keywords:            |  Blocked By:
 Blocking:            |
----------------------+------------------------

Comment (by robyduck):

 Now it gets more interesting here. Things are coming up very different as
 expected, here a few updates and TODOs.

 '''Spins:''' will get under a separate page, nothing will be
under
 Workstation. I thought about a get-spins-prerelease page where we can
 collect all the spins. Releng will build '''all''' spins for F21
Alpha. If
 we are ok with that we shouldn't forget to add that page to the
 redirect.conf file on puppet.

 '''Cloud:''' it's all very new. i386 and x86_64 "Cloud
Base"; x86_86
 "Fedora Atomic"; x86_64 "Big Data".[[br]]
 At least, the Atomic, Cloud Base, and Big Data choices should be a big top
 level choice -- like a different page or tab. From there people can go in
 the single block to get more information.[[br]]
 Cloud WG also wrote a new service that takes all these images and uploads
 them all to one place, with datagrepper. We need a script to get this data
 the right way, maybe oddshocks can help us here.[[br]]
 Some tickets with more information:
 * https://fedorahosted.org/rel-eng/ticket/5891
 * https://fedorahosted.org/cloud/ticket/36
 Remember we need also to review the verify page to have all the CHECKSUMs
 linked the right way!

 With all these images and products we probably need new download-slpash
 pages. As mentioned in the comments before we need to get some content for
 the single products, to do ASAP (for now we don't have any information
 about the Server Product!) because the content has to be pushed to TX to
 permit L10n temas to translate them in time for F21 Alpha release.

 At this point any help, suggestion or idea is very appreciated.

-- 
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/267#comment:10>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance

[fedora-badges]

#267: Prepare websites for F21 Alpha release
----------------------+------------------------
 Reporter:  robyduck  |       Owner:  webmaster
     Type:  task      |      Status:  new
 Priority:  major     |   Milestone:
Component:  www.fp.o  |  Resolution:
 Keywords:            |  Blocked By:
 Blocking:            |
----------------------+------------------------

Comment (by cydrobolt):

 Sounds good. What is going to be the site structure? Are we going to be
 restyling the website, using a brochure site, or are we simply sticking
 with F20's design? A lot of sites seem to be going for a metro design; if
 we could do that for F21, I'm sure people would appreciate it.

 We could start small and build something like Spins off of Bootstrap. I
 would love to help build it.

-- 
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/267#comment:11>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance

[fedora-badges]

#267: Prepare websites for F21 Alpha release
----------------------+------------------------
 Reporter:  robyduck  |       Owner:  webmaster
     Type:  task      |      Status:  new
 Priority:  major     |   Milestone:
Component:  www.fp.o  |  Resolution:
 Keywords:            |  Blocked By:
 Blocking:            |
----------------------+------------------------

Comment (by msuchy):

 I still do not see F21 GPG keys at https://fedoraproject.org/keys

-- 
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/267#comment:12>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance

[fedora-badges]

#267: Prepare websites for F21 Alpha release
----------------------+------------------------
 Reporter:  robyduck  |       Owner:  webmaster
     Type:  task      |      Status:  new
 Priority:  major     |   Milestone:
Component:  www.fp.o  |  Resolution:
 Keywords:            |  Blocked By:
 Blocking:            |
----------------------+------------------------

Comment (by robyduck):

 Replying to [comment:12 msuchy]:
>  I still do not see F21 GPG keys at https://fedoraproject.org/keys
 That's ok, you won't see any F21 keys on our main website before Alpha
 release date. They are not relevant for end users and developers know
 where to get them. F21 keys are already set on the f21-alpha branch, which
 is build actually on our stg website: https://stg.fedoraproject.org/keys

-- 
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/267#comment:13>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance

[fedora-badges]

#267: Prepare websites for F21 Alpha release
----------------------+------------------------
 Reporter:  robyduck  |       Owner:  webmaster
     Type:  task      |      Status:  new
 Priority:  major     |   Milestone:
Component:  www.fp.o  |  Resolution:
 Keywords:            |  Blocked By:
 Blocking:            |
----------------------+------------------------

Comment (by robyduck):

 Replying to [comment:11 cydrobolt]:
>  Sounds good. What is going to be the site structure? Are we going to
> be 
 restyling the website, using a brochure site, or are we simply sticking
 with F20's design? A lot of sites seem to be going for a metro design; if
 we could do that for F21, I'm sure people would appreciate it.
>  We could start small and build something like Spins off of Bootstrap. I 
 would love
to help build it.
 No, we are still on F20, and will be on F20 until october at least.
 Therefore we will use the actual webpage layout, but we need to rewrite
 the get-prerelase pages in order to fit the needs of the 3 main products.

-- 
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/267#comment:14>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance

[fedora-badges]

#267: Prepare websites for F21 Alpha release
----------------------+------------------------
 Reporter:  robyduck  |       Owner:  webmaster
     Type:  task      |      Status:  new
 Priority:  major     |   Milestone:
Component:  www.fp.o  |  Resolution:
 Keywords:            |  Blocked By:
 Blocking:            |
----------------------+------------------------

Comment (by robyduck):

 We have TC2 images now for almost all poducts, it looks like we are set
 the right way this time. For ARM we will have an Install tree on the
 Server Product.

 New text on stg.fpo has already been pushed to the L10n teams, we still
 needsome other text content but there is time.

 TODOS before readiness meeting:
 * complete text content and push it to TX;
 * create new splash images and activate them through our JS file;
 * once we have all DL buttons, check the links (they are actually '''ALL
 WRONG''') and fix them. Path will be the same as TC and RC images;
 * make the Spins Link on the pre-release overview page a little bit more
 prominent;

 The rest has to be done after we have a GO for a RC image.

-- 
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/267#comment:15>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance

[fedora-badges]

#267: Prepare websites for F21 Alpha release
----------------------+------------------------
 Reporter:  robyduck  |       Owner:  webmaster
     Type:  task      |      Status:  new
 Priority:  major     |   Milestone:
Component:  www.fp.o  |  Resolution:
 Keywords:            |  Blocked By:
 Blocking:            |
----------------------+------------------------

Comment (by mailga):

 Added workstation download splash, updated file js and get-prerelease and
 references to the workstation WG

-- 
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/267#comment:16>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance

[fedora-badges]

#267: Prepare websites for F21 Alpha release
----------------------+------------------------
 Reporter:  robyduck  |       Owner:  webmaster
     Type:  task      |      Status:  new
 Priority:  major     |   Milestone:
Component:  www.fp.o  |  Resolution:
 Keywords:            |  Blocked By:
 Blocking:            |
----------------------+------------------------

Comment (by robyduck):

 Thanks mailga, patch applied. I just corrected the I18n string, the rest
 looks fine to me. We will have mostly ISO files, want to do the download
 splash also for Cloud and Server?

-- 
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/267#comment:17>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance

[fedora-badges]

#267: Prepare websites for F21 Alpha release
----------------------+------------------------
 Reporter:  robyduck  |       Owner:  webmaster
     Type:  task      |      Status:  new
 Priority:  critical  |   Milestone:
Component:  www.fp.o  |  Resolution:
 Keywords:            |  Blocked By:
 Blocking:            |
----------------------+------------------------
Changes (by robyduck):

 * priority:  major => critical


Comment:

 Alpha release is straight ahead and we still need to finish some things
 and do the usual operations between GO decision and release date. I
 modified the download-splash a bit for Alpha and created a separate verify
 page, which should make all the F21.next stuff clearer. We still need to:
 * ask Product WGs/Marketing for the final text content they want to have
 on the prerelease page
 * Push that content to TX in time for L10n
 * Add a torrent section for each product (will do that today)
 * Check and rewrite '''ALL''' Download Links, remember we have a
RC
 release number in the filename
 * We have some Image sizes, add them for Alpha as globalvar
 * Add CHECKSUMs
 * Check links for docs (Release Notes and bugs) and other stuff we have in
 the prerelease page
 * '''Cloud:''' We need to know ASAP which products we will ship
and what
 they are for. We also need EC2 IDs for both architectures

 Anything I'm forgetting now? Should be all ready for thursday :)

-- 
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/267#comment:18>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance

[fedora-badges]

#267: Prepare websites for F21 Alpha release
----------------------+------------------------
 Reporter:  robyduck  |       Owner:  webmaster
     Type:  task      |      Status:  new
 Priority:  critical  |   Milestone:
Component:  www.fp.o  |  Resolution:
 Keywords:            |  Blocked By:
 Blocking:            |
----------------------+------------------------

Comment (by mattdm):

 Okay, so, here's the picture for cloud deliverables. :)


 * We have two major "subproducts"
  * '''Fedora Cloud Base'''
  * '''Fedora Atomic'''
 * Each of these is available either to download in several formats
''or''
 to launch in public clouds
  * Downloadable Formats
   * qcow2 (recommended for OpenStack)
   * raw.xz (for other cloud infrastructures -- see wording on current
 http://fedoraproject.org/get-fedora#clouds)
   * this list is ''unlikely'' to grow
  * Public clouds
   * Amazon EC2
   * That's all for right now but Rackspace and HP Cloud ''should''
be
 soon, as well as GCE and possibly others
 * What about architectures?
  * Fedora Cloud Base is available in two architectures
   * 32-bit i386
   * 64-bit x86_64
  * Fedora Atomic is '''only x86_64'''
  * It is likely we will add 64-bit ARM to Cloud Base in future releases
  * It is possible that we will drop i386
  * Fedora Atomic just plain can't work in i386 because of Docker; this may
 change in the future but
    it's more likely that we'd add ARM than bother with i386


 Sooo, this makes a kind of complicated matrix, and we can present it
 multiple ways, but I think fundamentally it makes sense to present it as
 "which subproject", then "how do you want it? (download or launch), and
 then details like architecture, specific download format, and EC2 region.

-- 
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/267#comment:19>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance

[fedora-badges]

#267: Prepare websites for F21 Alpha release
----------------------+------------------------
 Reporter:  robyduck  |       Owner:  webmaster
     Type:  task      |      Status:  new
 Priority:  critical  |   Milestone:
Component:  www.fp.o  |  Resolution:
 Keywords:            |  Blocked By:
 Blocking:            |
----------------------+------------------------

Comment (by robyduck):

 Thank you Matthew for the update, please have a look at the stg instance
 if it works for you. I've hidden also the netinstall images, same as for
 workstation.

 We have a TC6 now, but paths are still changing, so let's wait for the
 first RC before updating the links, although they should already be in a
 good shape.

-- 
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/267#comment:20>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance

[fedora-badges]

#267: Prepare websites for F21 Alpha release
----------------------+------------------------
 Reporter:  robyduck  |       Owner:  webmaster
     Type:  task      |      Status:  new
 Priority:  critical  |   Milestone:
Component:  www.fp.o  |  Resolution:
 Keywords:            |  Blocked By:
 Blocking:            |
----------------------+------------------------

Comment (by mattdm):

 Awesome, thanks -- looks good. It's a bit of a choose-your-own-adventure,
 but that's kind of our fault and not yours. We should work on a more
 elegant presentation of some sort for final -- I'll bring this to the
 Cloud SIG....

-- 
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/267#comment:21>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance

[fedora-badges]

#267: Prepare websites for F21 Alpha release
----------------------+------------------------
 Reporter:  robyduck  |       Owner:  webmaster
     Type:  task      |      Status:  new
 Priority:  critical  |   Milestone:
Component:  www.fp.o  |  Resolution:
 Keywords:            |  Blocked By:
 Blocking:            |
----------------------+------------------------

Comment (by robyduck):

 Replying to [comment:21 mattdm]:
>  Awesome, thanks -- looks good. It's a bit of a choose-your-own-
 adventure, but that's kind of our fault and not yours. We should work on a
 more elegant presentation of some sort for final -- I'll bring this to the
 Cloud SIG....

 Yes, agree, it's probably not perfect but it's really hard to find for all
 the options a smooth presentation layout with the actual websites. For
 final we will have a new websites layout, I'm sure we can do that much
 better then.

-- 
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/267#comment:22>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance

[fedora-badges]

#267: Prepare websites for F21 Alpha release
----------------------+------------------------
 Reporter:  robyduck  |       Owner:  webmaster
     Type:  task      |      Status:  new
 Priority:  critical  |   Milestone:
Component:  www.fp.o  |  Resolution:
 Keywords:            |  Blocked By:
 Blocking:            |
----------------------+------------------------

Comment (by hadess):

 As mentioned on the desktop mailing-list, I would put the i686 downloads
 on the same page as the ARM one, leaving us with just one download on the
 main page, with 2 different download methods.

-- 
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/267#comment:23>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance

[fedora-badges]

#267: Prepare websites for F21 Alpha release
----------------------+------------------------
 Reporter:  robyduck  |       Owner:  webmaster
     Type:  task      |      Status:  new
 Priority:  critical  |   Milestone:
Component:  www.fp.o  |  Resolution:
 Keywords:            |  Blocked By:
 Blocking:            |
----------------------+------------------------

Comment (by robyduck):

 Replying to [comment:23 hadess]:
>  As mentioned on the desktop mailing-list, I would put the i686
> downloads 
 on the same page as the ARM one, leaving us with just one download on
the
 main page, with 2 different download methods.
 We should not mix up product images with ''non-products'', I discussed
 this point with the Workstation WG and we found a good compromise I think.
 \\
 It's already pushed to the websites-repo and should be live in about 50
 minutes.
 Thank you.

-- 
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/267#comment:24>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance

[fedora-badges]

#267: Prepare websites for F21 Alpha release
----------------------+------------------------
 Reporter:  robyduck  |       Owner:  webmaster
     Type:  task      |      Status:  new
 Priority:  critical  |   Milestone:
Component:  www.fp.o  |  Resolution:
 Keywords:            |  Blocked By:
 Blocking:            |
----------------------+------------------------
Changes (by jzb):

 * cc: jzb@… (added)


Comment:

 Hi - I have a few changes on the cloud section, have attached a patch (see
 above) which makes some language changes and also removes the 32-bit
 download section for Atomic images (see Matt's comments). Please let me
 know if this works for you, or if you'd like changes another way.

-- 
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/267#comment:25>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance

[fedora-badges]

#267: Prepare websites for F21 Alpha release
----------------------+------------------------
 Reporter:  robyduck  |       Owner:  webmaster
     Type:  task      |      Status:  new
 Priority:  critical  |   Milestone:
Component:  www.fp.o  |  Resolution:
 Keywords:            |  Blocked By:
 Blocking:            |
----------------------+------------------------

Comment (by robyduck):

 Replying to [comment:25 jzb]:
>  Hi - I have a few changes on the cloud section, have attached a patch
 (see above) which makes some language changes and also removes the 32-bit
 download section for Atomic images (see Matt's comments). Please let me
 know if this works for you, or if you'd like changes another way.

 Thank you jzb :)

 I took a look just at the diff and it's perfect, the download sections and
 links are still not final, but thanks to help with that too. I will apply
 the patch ASAP, thanks again.

-- 
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/267#comment:26>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance

[fedora-badges]

#267: Prepare websites for F21 Alpha release
----------------------+------------------------
 Reporter:  robyduck  |       Owner:  webmaster
     Type:  task      |      Status:  new
 Priority:  critical  |   Milestone:
Component:  www.fp.o  |  Resolution:
 Keywords:            |  Blocked By:
 Blocking:            |
----------------------+------------------------

Comment (by robyduck):

 I'm updating this ticket a bit (also for myself :) ), Alpha is around the
 corner (hopefully we will GO next week).
 Most of the tasks have to be done only when we'll have the final RC, but
 we still need to:

 * rewrite all DL and double check them, we will have
'''underscores''' in
 the path;
 * I added a Docker Tab, remember to update the compose date also in that
 page;
 * Update Image sizes, they are all already in our globalvar file and in
 the paths;
 * update ''cloud_prerelease_composedate'' and ''RC_Gold''
variables;
 * Add CHECKSUMs;
 * Rewrite the new verify-prerelease page, we will have a lot of checksums
 and need to display them as clear as possible;
 * Check links for docs (Release Notes are OK) and other stuff we have in
 the prerelease page
 * Add EC2 IDs for both architectures of Cloud Base and Atomic (script is
 ready to get 2 IDs).

 Just as a side-note, pay attention when merging into master, we won't have
 a clean merge this time.

-- 
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/267#comment:27>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance

[fedora-badges]

#267: Prepare websites for F21 Alpha release
----------------------+------------------------
 Reporter:  robyduck  |       Owner:  webmaster
     Type:  task      |      Status:  new
 Priority:  critical  |   Milestone:
Component:  www.fp.o  |  Resolution:
 Keywords:            |  Blocked By:
 Blocking:            |
----------------------+------------------------

Comment (by robyduck):

 We're done! Should be all in place now, as always we will have torrents on
 monday and so we need only to add the Cloud AMI IDs to the script (which
 is already in place and working).
 * Add EC2 IDs for both architectures of Cloud Base and 64bit for Cloud
 Atomic

 Hopefully we will have a smooth release tuesday :)
 Thank you all for your help, suggestions and contents.

-- 
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/267#comment:28>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance

[fedora-badges]

#267: Prepare websites for F21 Alpha release
----------------------+------------------------
 Reporter:  robyduck  |       Owner:  webmaster
     Type:  task      |      Status:  closed
 Priority:  critical  |   Milestone:
Component:  www.fp.o  |  Resolution:  fixed
 Keywords:            |  Blocked By:
 Blocking:            |
----------------------+------------------------
Changes (by robyduck):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 Fedora 21 Alpha webpages are live!

-- 
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/267#comment:29>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance