[fedora-websites] #191: outdated requirements
by fedora-badges
#191: outdated requirements
---------------------+------------------------
Reporter: shaiton | Owner: webmaster
Type: defect | Status: new
Priority: major | Milestone: Fedora 19
Component: General | Version:
Keywords: | Blocked By:
Blocking: |
---------------------+------------------------
We don't have the same requirements on fpo/index and fpo/get-fedora (and
other?).
I just updated to feature 1Gio minimum of RAM.
But we should probably drop the 400Mhz computer...
Should conform with docs
--
Ticket URL: <https://fedorahosted.org/fedora-websites/ticket/191>
fedora-websites <https://fedoraproject.org/wiki/Websites>
Fedora Website Team's Trac instance
10 years, 10 months
Introducing changes on the Workflow
by Kévin Raymond
Hi Fedora webmasters,
We already discussed this during last winter, and are going to apply the
new workflow, starting now.
Here is the major changes:
- Production should always be against the "master" branch. If you have a
quick fix to make, that's where it should go. For every websites.
- Preparing the websites for a new release is made on an fXX-Alpha,
fXX-Beta or fXX branch. The current one should be built on staging. At
release day, we just merge this branch into master to go live in prod.
We should not forget to tag this commit.
- Enhencements or test could be made on the "stg" branch. That way we
always have a developing branch.
[skip the following point if you don't need to read about translation
management]
- Please don't push a new POT unless you know what you are doing. We know
have only one Transifex resource per website, without duplicates as
before (fpo-master, fpo-f18-alpha...) Therefore, from one branch you can
break the translations on the other branch. It won't cause too much
damage as Transifex keep an history of the translations (pushing back
the right POT restore it), but the strings won't be translated for the
other branch. I introduced an any way to block pulling translation
during the build by keeping a file named "PO_FREEZE" at the top of the
website directory. This file is tested on Makefile.in.
The usual workflow is to share the same POs files (not locking pulling)
during Alpha and Beta, while we will probably want to lock it during the
Beta stage in order to let translators work for the new release
(translating the new slideshow, features page if needed, and other new
change). At release day we should check that "PO_FREEZE is deleted on
master in order to pull again the translations.
This translation things is hidden here, it works on our builder with
syncTranslations.sh script on puppet aside with syncStatic (puppet). The
first script pulls the translations from Transifex twice a day (or so)
while the usual syncStatic script hourly calls the "syncpos" Makefile.in
target in order to sync the POs from the pulled POs. "PO_FREEZE" just
lock the "syncpos" target.
There was no need to (force) pull hourly all translations. We should
probably pull hourly few days before GA, if asked by translators. But
it is now separated from our builds.
Therefore, we will need the infrastructure help only to manually build the
websites at the right time and to change the redirect (as get-prerelease).
And to change the PO pulling cron.
Anyone from our team would be able to push the new website for the
release. It is now easier to understand, easier to handle if for any
reasons we need someone else to do the task for GA, you have full power!!
Of course, the best is to let those doing it everytimes to do it the next
time... :)
We are quite ready for Alpha (#196), we will see then if it works nice or
if we should go back to our shadow workflow.
This is basically all, with Robert we also wrote the following pages in
order to make it easier for new contributors to understand our
workflow/tasks.
https://fedoraproject.org/wiki/Websites/workflow
https://fedoraproject.org/wiki/Websites/workflow/checklist
I also updated our following SOP, please comment:
http://infrastructure.fedoraproject.org/infra/docs/fedorawebsites.txt
--
Kévin Raymond
(Shaiton)
11 years
Re: [Call to Arms] Fedora 19 Test Days starts this week
by Bryan Sutherland
Martin,
I am cc'ing this to the FWN and Website list as I think this is a great
opportunity to get more community testing and input in.
There is some discussion about a few more FWN releases as we get ready
to open up fedoramagazine.org. The testing requests should be fine to go
out in pretty quick order.
Cheers
Bryan
On Tue, 2013-03-12 at 17:31 -0400, Martin Holec wrote:
> Hi,
>
> I want to open discussion on how to improve marketing for Fedora Test Days and pre-release testing in general.
>
> Few thoughts:
> * I heard about FWN revival. Can we provide some content to support Test Days or regular announcements are enough?
> * How to promote Test Days on fedoraproject.org website?
>
> Best Regards,
>
> Martin Holec
> Desktop QE, Red Hat Brno
>
> ----- Original Message -----
> From: "Martin Holec" <mholec(a)redhat.com>
> To: test-announce(a)lists.fedoraproject.org, "For testing and quality assurance of Fedora releases" <test(a)lists.fedoraproject.org>, devel(a)lists.fedoraproject.org, devel-announce(a)lists.fedoraproject.org, users(a)lists.fedoraproject.org
> Cc: marketing(a)lists.fedoraproject.org
> Sent: Tuesday, March 12, 2013 10:16:46 PM
> Subject: [Call to Arms] Fedora 19 Test Days starts this week
>
> Hi Fedora users, developers and friends!
>
> today Fedora 19 was branched from Rawhide. That means testing season begins now and will continue till Fedora 19 Final Release, which may be (or may not be) on 2013-06-25. Please, fasten your seatbelts, fire up your virtual or baremetal machines and enjoy this crash testing ride with us.
>
> Remember: https://is0.4sqi.net/userpix/D1Y3XKHJVN4GIMRW.jpg
>
> Before Alpha will (or won't) be ready on 2013-04-16, we have prepared some Test Days[0] for you. Starting this Thursday with KDE 4.10 [1] with one major innovation. You are invited to try how new KDE 4.10 [2] stuff not only using Fedora 19 Live test images, but also from updates-testing repository on your current Fedora stable installation, including both Fedora 18 and Fedora 17 releases. For first time, you can test new version of whole KDE platform before it rolls up and in as an stable update for your Fedora!
>
> [0] https://fedoraproject.org/wiki/QA/Fedora_19_test_days
> [1] https://fedoraproject.org/wiki/Test_Day:2013-03-14_KDE_4.10
> [2] http://www.kde.org/announcements/4.10/
>
> Well, you may already know about and use Bodhi[3] with karma voting process. But Test Day provides an opportunity to actually talk to developers before KDE 4.10 reaches stable updates and interactively report, explore, debug and fix your issues (or at least find workarounds for the time being). Together we can make this update less painful for everyday Fedora KDE users.
>
> [3] https://admin.fedoraproject.org/updates/
>
> Join IRC #fedora-test-day on FreeNode and ask QA or developers for help, if you get into trouble. We can try to find workarounds and help you with debugging. Please report all bugs under appropriate component preferably at upstream bugzilla https://bugs.kde.org/ regarding common KDE 4.10 issues or Red Hat bugzilla http://bugzilla.redhat.com/ if you have problems with Fedora distribution integration. You can also report other Fedora bugs not related to this Test Day. Feel free to ask on IRC, if you don't know against which component or on what bugzilla you should fill the report.
>
> See you in Bugzilla!
>
> Best Regards,
>
> Martin Holec
> Desktop QE, Red Hat Brno
>
> Freenode nick: Martix
> Your self-appointed Fedora 19 Test Day Wrangler.
> --
> marketing mailing list
> marketing(a)lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/marketing
11 years, 1 month
