In the past, we would normally begin syncing soon to be EOL releases over to Archives so that the mirrors would be ready for it. We haven't done this for a bit and a couple of mirrors have complained that /pub/fedora is larger than they want to keep. I would like to get an official policy to them about how many releases that a mirror should expect to be in /pub/fedora and when we plan to archive off releases.

The steps for syncing/hardlinking releases was the following:

log into a box with read-write access to the the release tree.

sudo su -s /bin/bash ftpsync

cd /pub/fedora/linux/releases

ls -l /pub/archive/fedora/linux/releases/ # to see if tree is already synced

If I were to archive off 23 I would now do the following:

cp -lr 23/ /pub/archive/fedora/linux/releases/

this should hardlink everything across so we save disk space.

cd ../updates

cp -lr 23/ /pub/archive/fedora/linux/updates/

cd testings

cp -lr 23/ /pub/archive/fedora/linux/updates/testing/

cd /pub/fedora-secondary/releases

cp -lr 23/ /pub/archive/fedora-secondary/releases/

cd ../updates/

cp -lr 23/ /pub/archive/fedora-secondary/updates/

cd testing

cp -lr 23/ /pub/archive/fedora-secondary/updates/testing/

Make any changes to scripts which do fullfilelist to make it know about new trees. 

Announce the mirroring to mirrors-list and then wait 2 weeks.

After two weeks are done, have mirrormanager point to the archive tree.

Remove the data out of /pub/fedora and /pub/fedora-secondary

Hardlink the file in a previous archived directory to the empty directory

Update the fullfilelist

Email mirrorlist about the changes being completed

======

What should we tell the lists that the number of releases which will be in the main repository now? And how many releases should I archive off after F24 goes EOL next week?