We have 10 days before Readiness meeting to setup the websites for F27 Beta release, although the state of F27 Beta is bad, so we might expect to slip a bit. I branched f27-beta right now, so pull the new branch before start working on the beta release. To do list:
We do not need to freeze translations this time, so we will just merge at release date and all should be fine. But we have to update all POT files and po files in our repo. Would be nice to have always an updated content when we tag a release.
Please ask, also by adding a comment if you want to work on something or if you have doubts. All pushes need to go to f27-beta.
For ticket #722 we need to run a sed through all websites to catch the broken links we know of. Does anyone want to make a list of our main links (Install guide, Release notes, etc) for a sed substitute?
Beta is out, websites released.
Metadata Update from @robyduck: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.