Search results

Test cases that validate the Server-specific [[Fedora Release Criteria]]. [[Category:Server validation testing]]

...is intended to record server [[QA:Release_validation_test_plan|validation testing]] test results for the Fedora '''21 Alpha TC1''' release. # Download the ISO images for testing: please use one of the [https://dl.fedoraproject.org/pub/alt/stage/F21a-TC1

...is intended to record server [[QA:Release_validation_test_plan|validation testing]] test results for the Fedora '''21 Alpha TC5''' release. # Download the ISO images for testing: please use one of the [https://dl.fedoraproject.org/pub/alt/stage/21-Alpha

...is intended to record server [[QA:Release_validation_test_plan|validation testing]] test results for the Fedora '''21 Alpha TC7''' release. # Download the ISO images for testing: please use one of the [https://dl.fedoraproject.org/pub/alt/stage/21_Alpha

...is intended to record server [[QA:Release_validation_test_plan|validation testing]] test results for the '''Fedora 21 PPC''' release. # Download the ISO images for testing: please use one of the [https://ppc.koji.fedoraproject.org/stage/ Network p

...is intended to record server [[QA:Release_validation_test_plan|validation testing]] test results for the Fedora '''21 Alpha RC1''' release. # Download the ISO images for testing: please use one of the [https://dl.fedoraproject.org/pub/alt/stage/21_Alpha

...is intended to record server [[QA:Release_validation_test_plan|validation testing]] test results for the Fedora '''21 Alpha TC6''' release. # Download the ISO images for testing: please use one of the [https://dl.fedoraproject.org/pub/alt/stage/21_Alpha

This page records [[QA:Base_validation_testing|base validation testing]] test results for the Fedora '''18 Final RC4''' release. # Download the ISO images for testing: please use either a [https://download.fedoraproject.org/pub/fedora/linux/r

This page records base system [[QA:Release_validation_test_plan|validation testing]] test results for the '''Fedora 21 PPC''' release. ( Workstation, Server, KDE, ARM, Cloud, References)

This page records base system [[QA:Release_validation_test_plan|validation testing]] test results for the Fedora '''21 Alpha TC1''' release. # Download the ISO images for testing: please use one of the [https://dl.fedoraproject.org/pub/alt/stage/F21a-TC1

This page records base system [[QA:Release_validation_test_plan|validation testing]] test results for the Fedora '''21 Alpha RC1''' release. # Download the ISO images for testing: please use one of the [https://dl.fedoraproject.org/pub/alt/stage/21_Alpha

This page records base system [[QA:Release_validation_test_plan|validation testing]] test results for the Fedora '''21 Alpha TC7''' release. # Download the ISO images for testing: please use one of the [https://dl.fedoraproject.org/pub/alt/stage/21_Alpha

This page records base system [[QA:Release_validation_test_plan|validation testing]] test results for the Fedora '''21 Alpha TC6''' release. # Download the ISO images for testing: please use one of the [https://dl.fedoraproject.org/pub/alt/stage/21_Alpha

This page records base system [[QA:Release_validation_test_plan|validation testing]] test results for the Fedora '''21 Alpha TC5''' release. # Download the ISO images for testing: please use one of the [https://dl.fedoraproject.org/pub/alt/stage/21-Alpha

This page records [[QA:Desktop_validation_testing|desktop validation testing]] test results for the Fedora '''14 Alpha Test Compose 2''' release. ...be kept on the server during the TC2 test period. Please use these images. Testing for all four major desktop environments is required for each test point. De

This page records [[QA:Desktop_validation_testing|desktop validation testing]] test results for the Fedora '''17 Beta RC4''' release. .../releases/test/17-Beta/Live/ live image] for the desktop you wish to test. Testing for all four major desktop environments is required for each test point. [[

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= F21 RC1 - AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

..._plan]]. This page provides guidance on arranging and announcing a release validation test event. For any concerns, please contact the [[QA]] group. ...s process. This SOP can still be followed in any unusual case where manual validation event creation is still required.}}

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

...Release_validation_test_plan|release validation testing process]], and for testing updates. On this page you can find more information about openQA, how Fedor openQA is an automated test system designed around operating system-level testing. Its key feature is that it interacts with the system under test much like

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

...k|This page describes '''experimental''' and unofficial module for unbound server!}} The testing build of unbound server with the mixed-mode module can be found in the [http://copr-fe.cloud.fedora

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

= AARCH64 Release Validation = ! Milestone !! Test Case !! Server

...tended to record installation [[QA:Release_validation_test_plan|validation testing]] test results for the '''Fedora 21 Alpha TC5''' milestone. ...ority is available in [[QA:Release_validation_test_plan#anchor|the release validation test plan]].

...tended to record installation [[QA:Release_validation_test_plan|validation testing]] test results for the '''Fedora 21 Alpha TC7''' milestone. ...ority is available in [[QA:Release_validation_test_plan#anchor|the release validation test plan]].

...included on this page because all the same tests are present on the Cloud validation page.}} ! Milestone !! Test Case !! Workstation !! Server !! KDE

= Framework for Server Role Deployment = A new D-Bus service, and associated command-line tools, to deploy and manage Server Roles.

...erly. The root zone provides a global trust anchor that in turn allows for validation of DNS records in signed zones. Other trust anchors can be configured to ex ...e local validating resolver which reports name resolution failure whenever validation of a DNS record fails. On the other hand, applications that know about DNSS

...tended to record installation [[QA:Release_validation_test_plan|validation testing]] test results for the '''Fedora 21 Alpha TC6''' milestone. ...ority is available in [[QA:Release_validation_test_plan#anchor|the release validation test plan]].

...tended to record installation [[QA:Release_validation_test_plan|validation testing]] test results for the '''Fedora 21 Alpha TC1''' milestone. ...ority is available in [[QA:Release_validation_test_plan#anchor|the release validation test plan]].

...tended to record installation [[QA:Release_validation_test_plan|validation testing]] test results for the '''Fedora 21 Alpha RC1''' milestone. ...ority is available in [[QA:Release_validation_test_plan#anchor|the release validation test plan]].

records usually from a DNSSEC-compliant recursive DNS server. The validator recursive DNS server is needed.

...S. Built on standard web protocols, WebHDFS decouples the HDFS client and server and is language- and operating system-agnostic. WebHDFS makes it easy to in ...proach. This will be done by designing or adopting an API, implementing a server, and validating correctness and evaluating performance under various use ca

...S. Built on standard web protocols, WebHDFS decouples the HDFS client and server and is language- and operating system-agnostic. WebHDFS makes it easy to in ...proach. This will be done by designing or adopting an API, implementing a server, and validating correctness and evaluating performance under various use ca

...change is to promote Fedora CoreOS to Edition status alongside Cloud, IoT, Server and Workstation. ...change is to promote Fedora CoreOS to Edition status alongside Cloud, IoT, Server and Workstation.

...tended to record installation [[QA:Release_validation_test_plan|validation testing]] test results for the ''' Fedora 21 PPC''' milestone. ...ority is available in [[QA:Release_validation_test_plan#anchor|the release validation test plan]].

...calable compose''' to enable CI/CD operations; we need to '''automate more testing and quality measures'''; and we need to '''update our delivery tools and pr We need faster composes, to enable more continuous testing/integration/delivery. In a continuous process, changes are checked not just

...a graphical mechanism for deploying a FreeIPA Domain Controller on Fedora Server through the Cockpit administrative console. * Email: server@lists.fedoraproject.org

server administration team, the SAN administration team, and others (network, etc.) not relevant to this discussion. Within the server

...e AD flag to calling applications. This tricks applications into believing validation results of random servers received through DHCP and other means, which are * Trusted and untrusted for DNSSEC validation servers cannot be mixed.

...ain) version 9.10 is the latest stable major update of the widely used DNS server. Besides new features, some settings defaults have changed since the previo ...y if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks)

...epo heirarchies do something like that already kde-unstable depends on kde-testing depends on kde-stable ...r packages against this. Bob shares his gtk2newness koper with others for validation of the new GTK2

...cycle. The Artwork Team brings us news on the Fedora 14 artwork efforts, testing the new Fedora branding Fonts recently developed, and a mockup for the new ...omewhere around Fedora 9. It just seemed the distribution that served as a testing ground for Red Hat Enterprise Linux was too much work to get stable and too

...s goes well, we'll use it for F36. [https://ask.fedoraproject.org/t/we-are-testing-a-new-common-issues-category-and-process/18916 Your feedback] is welcome! {{Common bugs update testing|FEDORA-2021-f7d19c8901}}

...13 website banner designs, work on a LiveCD icon, and a call for help with testing the Fedora 13 Alpha backgrounds. This issue finishes off with a quiet week ...validation. In the mean time builds will continue to be pushed to updates-testing for 13, and even to 13 stable, however critical path packages might not be

...politique de mise à jour —, migrent du dépôt [[#updates-testing|''updates-testing'']] vers ce dépôt. ...itique de mise à jour]] migrent du dépôt [[#updates-testing|the ''updates-testing'']] vers ce dépôt. Cette différence d’avec "Branched" résulte de la n

...er packages against this. Bob shares his gtk2newness copr with others for validation of the new GTK2 ...ber of other packages with this rpm. Jill shares her rpm copr for further testing of the rpm change.

| image = [[File:Echo-testing-48px.png|link=QA/Fedora_22_test_days]] ...| If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, fi

| image = [[File:Echo-testing-48px.png|link=QA/Fedora_21_test_days]] ...| If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, fi

Enable the use of fsverity for installed RPM files validation. ...oes not appear to meaningfully slow down package installs during empirical testing. Once generated, the Merkle tree will use up some disk space for its storag

...de-redhat, and the availability of KDE SC 4.4rc2 live images available for testing. That rounds out FWN 212 -- read on! ...ture for the release are '''significantly''' "feature complete", ready for testing, and have a current status.<ref>https://fedoraproject.org/wiki/Feature_Free

'''Testing and Expected Results''' ** Issue different types of certificates like user certs, server certs

FreeIPA with integrated DNS server will support serving of DNSSEC secured zones and automatic DNSSEC key maint DNS server integrated to FreeIPA in Fedora 20 is not able to serve signed DNS zones. N

...the date? | If you come to this page after the test day is completed, your testing is still valuable, and you can use the information on this page to test, fi The following cast of characters will be available testing, workarounds, bug fixes, and general discussion:

* Live CD testing was introduced in [[QA/TestResults/Fedora9LiveCD/FinalRelease]] (and droppe * The ''Cloud'' and ''Server'' test types first appeared in [[:Category:Fedora_21_Alpha_Test_Results|Fed

...6 Alpha prep, oVirt node spin review and testing, and Instalatron anaconda testing framework details, to name but a few items. Security Advisories brings us ==== Outage: Server reboots - 2011-08-01 14:00 UTC ====

...h of the files and do your work there. Then after you've done appropriate testing, you can merge those changes into the branch you retrieved and send them to ...ges you made to the Release Notes produce a fully working document. Run a validation test to check (this example is using the original "en-US" language):

...ent in Greece. In Quality Assurance news, details on the latest Fedora 13 testing processes and results, and reports on two Test Days on Preupgrade Kit and X 2.6.35/2.6.36 kernel, GCC 4.5, and X.Org Server 1.9."

== AutoQA initscripts test validation == * jlaska - set up testing instance of autotest-server

...on with the Fedora QA Team for help with the Fedora Localization Project's testing events, and an announcement of new team members for French, Arabic and Russ ...n tests as possible. James noted that he planned to bring the installation testing SOP<ref>http://fedoraproject.org/wiki/User:Liam/Draft_Install_Test_SOP</ref

* Storage validation * There was a SNAFU with fedup on release day: fedup 0.8 was still in updates-testing for F18 and F19 on the day of release, and it turned out upgrades to F20 wi

...lity Assurance reports on the latest Test Day on World IPv6, Security spin testing, and lots of other projects ongoing with Fedora 15 and 16. Security Adviso that are interested in testing this in advance, we have already updated

...ectures/ARM/qa-machines]] lists remotely-accessible machines available for testing purposes ...with running autotest on ARM hosts on Fedora 18: we agreed that automated testing on ARM should not blocker primary arch elevation as we are not enforcing th

...has completed. From the wiki pages, there were 26 bugs identified during testing. Alpha RC#1 is available for testing. Instructions for downloading and providing feedback available at:

...esign beat, updated details on Fedora 13 artwork including wallpapers, and testing results of the new Design Suite spin. Security Advisories provides last we The CVS server will not accept connections so that we can mass-branch for Fedora 13.

...i upgraded to 1.14.0. [https://pagure.io/modularity/issue/60, #60] Modular server replicated to mirrors correctly. [https://pagure.io/releng/issue/7056, #705 ...//pagure.io/fedora-infrastructure/issue/6182, #6182] The On Demand Compose Server (ODCS) needs to be deployed. Once the changes to the OSBS components (atomi

Validation of install media must work correctly for all release-blocking images. ...eased Fedora or other operating system and hence irrelevant to the release validation process.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

Validation of install media must work correctly for all release-blocking images. ...eased Fedora or other operating system and hence irrelevant to the release validation process.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

...ery important, and we need your help. The Live image for CD and USB makes testing easy and painless, and improvements in virtualization make a full installat ...g a solid Fedora 11 release. You can make the Fedora 11 release better by testing the Beta release and reporting your findings.

...te, both sections are meant for users of Fedora variants like Workstation, Server, or KDE Plasma Desktop; in case you are using a Fedora Atomic Desktop like ...BIOS Setup or through a process initiated through <code>mokutil --disable-validation</code>; that's required, as your firmware will otherwise reject booting ker

== Fedora 16 - Rawhide acceptance testing == # twu agreed to lead Rawhide Acceptance Tests for Fedora 16, will be testing and posting a matrix for review starting this week

...03#comment-618750]), QA team is not responsible for physical optical media testing. However, if any bug is found, it'll be considered to be a blocker.|header Validation of install media must work correctly for all release-blocking images.

Validation of install media must work correctly for all release-blocking images. ...eased Fedora or other operating system and hence irrelevant to the release validation process.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

Validation of install media must work correctly for all release-blocking images. ...eased Fedora or other operating system and hence irrelevant to the release validation process.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

Validation of install media must work correctly for all release-blocking images. ...eased Fedora or other operating system and hence irrelevant to the release validation process.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

Validation of install media must work correctly for all release-blocking images. ...eased Fedora or other operating system and hence irrelevant to the release validation process.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

...of my progress. I will also be pushing my commits once a week on a remote server specified, sometimes even earlier when I feel major works have been complet * Validation of constraints:

...to set up a virtual equivalent ASAP, but no one can remember how that old server is configured? People will sell you very expensive software to solve this p ...<ref>http://mairin.wordpress.com/2009/10/17/open-source-portable-usability-testing-lab-part-2-the-parts/</ref> the complete part list to the Fedora portable u

* ''pschindl to send out karma/testing request for not-yet-stable updates in RC2'' - this was likely done, by the ...ke sure some cloud testing is getting done'' - this was done, tim did some testing on RC4 AMIs

Validation of install media must work correctly for all release-blocking images. ...eased Fedora or other operating system and hence irrelevant to the release validation process.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

...l of Fedora Workstation to be more in line with the base install of Fedora Server. ...to ensure that someone is on board to do any process development work and testing and that all changes make it into the pipeline; a bullet point in a change

...03#comment-618750]), QA team is not responsible for physical optical media testing. However, if any bug is found, it'll be considered to be a blocker.|header Validation of install media must work correctly for all release-blocking images.

...03#comment-618750]), QA team is not responsible for physical optical media testing. However, if any bug is found, it'll be considered to be a blocker.|header Validation of install media must work correctly for all release-blocking images.

...ill want to do some best-effort testing on it and try and work it into the validation process somehow for F17 * Before that, they will start providing test images as soon as external testing will actually be of use to them, with instructions

...03#comment-618750]), QA team is not responsible for physical optical media testing. However, if any bug is found, it'll be considered to be a blocker.|header Validation of install media must work correctly for all release-blocking images.

...03#comment-618750]), QA team is not responsible for physical optical media testing. However, if any bug is found, it'll be considered to be a blocker.|header Validation of install media must work correctly for all release-blocking images.

Validation of install media must work correctly for all release-blocking images. ...eased Fedora or other operating system and hence irrelevant to the release validation process.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

Validation of install media must work correctly for all release-blocking images. ...eased Fedora or other operating system and hence irrelevant to the release validation process.|headerstyle=background:#e5e5e5|fw1=normal|ta1=left}}

...03#comment-618750]), QA team is not responsible for physical optical media testing. However, if any bug is found, it'll be considered to be a blocker.|header Validation of install media must work correctly for all release-blocking images.

...graphics drivers, as well as a wrap up report of Fedora 13 Beta validation testing, and several other items. Translation includes reports of activity around ...icipants engage in to help sustain the community (e.g., to what extent is 'testing' a collaborative activity across the Fedora Project?)''', and

== Release criteria & validation test update round-up == * Re-jigged the level of quite a lot of test cases in the validation matrix to properly reflect the criteria

...03#comment-618750]), QA team is not responsible for physical optical media testing. However, if any bug is found, it'll be considered to be a blocker.|header Validation of install media must work correctly for all release-blocking images.

...03#comment-618750]), QA team is not responsible for physical optical media testing. However, if any bug is found, it'll be considered to be a blocker.|header Validation of install media must work correctly for all release-blocking images.

...tests. It is important to cleanly separate implementation details of the ''testing system'' from the ''test suite'' and its framework. It is also important to # The ''testing system'' SHOULD stage the tests on Fedora operating system appropriate for

...03#comment-618750]), QA team is not responsible for physical optical media testing. However, if any bug is found, it'll be considered to be a blocker.|header Validation of install media must work correctly for all release-blocking images.

...event wiki is ready and determined that a nightly live ISO would work for testing | style="color: #8c4a4a" | jlaska: i'll have to think about it if the server content isn't self-explanatory

...eMySQLwithMariaDB]] looks significant but we do not currently have planned testing for MySQL * [[Features/KScreen]] may impact KDE validation in a small way

...03#comment-618750]), QA team is not responsible for physical optical media testing. However, if any bug is found, it'll be considered to be a blocker.|header Validation of install media must work correctly for all release-blocking images.

...ill be used as a basis for identifying areas for improvement for Fedora 14 testing. Any thoughts, big or small, are valuable. If someone already provided fe ...that have been reviewed and accepted by key stake holders really expedites testing by improving bug escalation time and uncertainty regarding user impact. In

...ted. Quality Assurance brings news on QA statistics efforts, localization testing using Nitrate, and work on the F14 boot menu and bootloader. In Design Tea ...s scripts and third party applications that use the XMLRPC API at the test server to make sure they continue to function properly.

...ch for autotest to automatically transfer all autoqa config files from the server to the client : Continue testing and merging of new koji-watcher

...greatly asssists in the process of filing feedback on packages in updates-testing via Bodhi. Translation reviews the upcoming Fedora 13 tasks in that area, ...validation. In the mean time builds will continue to be pushed to updates-testing for 13, and even to 13 stable, however critical path packages might not be

* signing server * signing server

...of the weekly QA team meetings, increasing grub timeout, and X.org server testing. Our issue finishes with Security Advisories for Fedora 11 and 12. We hope .../ref>. He also said he was planning a release sprint to revise the release validation test plans for the new release criteria.

...of the weekly QA team meetings, increasing grub timeout, and X.org server testing. Our issue finishes with Security Advisories for Fedora 11 and 12. We hope .../ref>. He also said he was planning a release sprint to revise the release validation test plans for the new release criteria.

# Finish testing [[Releases/30/ChangeSet| Fedora 30 Changes]] ...ug expected to violate this criterion is "the default environment is Cloud Server instead of Workstation", that sort of thing.

# Finish testing [[Releases/31/ChangeSet| Fedora 31 Changes]] ...ug expected to violate this criterion is "the default environment is Cloud Server instead of Workstation", that sort of thing.

# Finish testing [[Releases/32/ChangeSet| Fedora 32 Changes]] ...ug expected to violate this criterion is "the default environment is Cloud Server instead of Workstation", that sort of thing.

# Finish testing [[Releases/33/ChangeSet| Fedora 33 Changes]] ...ug expected to violate this criterion is "the default environment is Cloud Server instead of Workstation", that sort of thing.

# Finish testing [[Releases/33/ChangeSet| Fedora 33 Changes]] ...ug expected to violate this criterion is "the default environment is Cloud Server instead of Workstation", that sort of thing.

...y if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks) ...and ensure that someone is on board to do any process development work and testing; don't just assume that a bullet point in a change puts someone else on the

| style="color: #818144" | other than bracing myself for final testing, nothing from me :) ...ion. we could move it up yet further just to make us all even more sick of validation. but it might be better, i guess, to look at that after we do one blocker r

# Finish testing [[Releases/36/ChangeSet| Fedora 36 Changes]] ...ug expected to violate this criterion is "the default environment is Cloud Server instead of Workstation", that sort of thing.

# Finish testing [[Releases/37/ChangeSet| Fedora 37 Changes]] ...ug expected to violate this criterion is "the default environment is Cloud Server instead of Workstation", that sort of thing.

# Finish testing [[Releases/38/ChangeSet| Fedora 38 Changes]] ...ug expected to violate this criterion is "the default environment is Cloud Server instead of Workstation", that sort of thing.

# Finish testing [[Releases/34/ChangeSet| Fedora 34 Changes]] ...ug expected to violate this criterion is "the default environment is Cloud Server instead of Workstation", that sort of thing.

# Finish testing [[Releases/35/ChangeSet| Fedora 35 Changes]] ...ug expected to violate this criterion is "the default environment is Cloud Server instead of Workstation", that sort of thing.

#* sigul--signing server needs work and connection with koji #* more tooling around releng tasks and tree validation

...clean way of enabling these steps on your local system (for, e.g., maximum testing), but to have them disabled when actually run through the buildsys/mock. == Tests require X11 server ==

...recommend freezing for Beta as new upgrade tool is still not available for testing: we would pass this recommendation to FESCo but recognize FESCo may go agai * TC6 seemed a decent build, we would continue with the validation testing

# Finish testing [[Releases/39/ChangeSet| Fedora 39 Changes]] ...ug expected to violate this criterion is "the default environment is Cloud Server instead of Workstation", that sort of thing.

# Finish testing [[Releases/40/ChangeSet| Fedora 40 Changes]] ...ug expected to violate this criterion is "the default environment is Cloud Server instead of Workstation", that sort of thing.

...sider both for an easy-to-use desktop and for a basic home or small-office server. The user interface and security features are first-class, and the rest of JesseKeating responded[3] that this code path had been left out of the validation tests and that Oliver's diagnosis of a Pungi bug in ConfigParser was correc

...oud integration, as well as details on Fedora 15 beta prep and Sugar build testing. This issue rounds out with security advisories for Fedora 13, 14 and 15 t Fedora 15 a solid release by downloading, testing, and providing

# Finish testing [[Releases/41/ChangeSet| Fedora 41 Changes]] ...ug expected to violate this criterion is "the default environment is Cloud Server instead of Workstation", that sort of thing.

...g/erroring out on wheels with such versions as well. The stricter metadata validation helps pip's dependency resolver's logic, along with helping the broader eco ...l of Fedora Workstation to be more in line with the base install of Fedora Server.

...ha stable updates push had not yet happened due to issues with the signing server ...aral: it has been already, we just had a bunch of trouble with our signing server over the weekend.

...anyone have a minute to look at the draft yet? robatino, you're the sanity testing guy? | style="color: #407a40" | #topic Testing

...the meeting, final freeze was the following day. Final TC2 was undergoing testing, and TC3 was expected soon. The blocker list was quite long, and TC2 test c ...ts, seems to make sense to consider checking all of those part of 'release validation'

==== evolution-data-server's libcamel soname version bump in Fedora 16/rawhide for 3.1.90 next week = Just after 3.1.5 release of evolution-data-server was added an API change in libcamel, thus the next week, when 3.1.90 will b

I'll be hanging around at least two hours, and can let the server run as recommend server settings, please speak up in the pregame meet up.

form that anyone can help test. This testing, guided by the Fedora QA ...rt of the anti-VMware Open Virtualization Alliance it launched in May with server heavyweights and aspiring cloud providers Hewlett-Packard and IBM.

...y if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks) When we added the metapackages for these extras in our testing Copr, no new broken requires on Python extras were generated. In other word

...of this week. Details also on the ongoing Fedora 13 beta candidate build testing, and discussion about the possibility of BugZapping classes. In Translatio ...t</ref>. This feature is very useful to those who use accounts on a remote server which may not always be accessible from their system. A small group of dedi

Project server. Remote coredump retracing avoids users having to quality reports. The retrace server can generate good backtraces with

...on OpenSCAP, and next week's Test Day on preupgrade, results on Fedora 14 testing and other F14 activity. In Design news, discussion on improving the Plymou ...ns all the features of Fedora 14 in a form that anyone can help test. This testing, guided by the Fedora QA team, helps us target and identify bugs. When thes

...yle="color: #407a40" | adamw - check in with tflink about alpha/beta/final validation results and ensuring bugs are correctly marked as blockers ...yle="color: #407a40" | adamw - check in with tflink about alpha/beta/final validation results and ensuring bugs are correctly marked as blockers

...t. We include a discussion in Developments of the need for "More and Wider Testing". Translation shares that "Release Announcements in Local Languages" are no === More and Wider Testing ===

* <s>[http://javaserverfaces.java.net Mojarra Java Server Faces]</s> |bean-validation-api

# All autoqa config files are now copied from the server to the client when executing tests | style="color: #97974f" | 1. All autoqa config files are now copied from the server to the client when executing tests. That will allow us to use "private" con

If a build which may fix the problem is made available via updates-testing, add this boilerplate paragraph (appropriately customized for the issue) to ...To test the update, run this command: <pre>su -c 'yum --enablerepo=updates-testing update --advisory=(advisory)'</pre>}}

us get the testing matrix completed by testing. ...s/RetraceServer</ref>. This allows you to submit crash reports to a remote server which will generate the backtrace - avoiding the need for you to download a

...FAIK, the bugzilla and FAS changes should be in production by the time F19 testing starts up ...do we need to do before ARM can be handled as part of our regular release validation?' topic?

...ive sizes are between 1GB and 32GB.</p><p>MultiWriter may be useful for QA testing, to create a GNOME Live image for a code sprint or to create hundreds of Li ...rectory, and keep the contents of those folders synced with your Nextcloud server. Simply copy a file into the directory and the Nextcloud Client does the

|airlied at redhat dot com||<code>xorg-x11-server</code>||[https://bugzilla.redhat.com/show_bug.cgi?id=278251 278251]||CTRL-A .../show_bug.cgi?id=292111 292111]||glxinfo triggers an assertion fail in X11 server with VIA CLE266