Re: [Test Day] Fedora 30 Upgrade Test Day 2019-04-26

[Yi-Soo An]

The link redirects to previous upgrade test day page.

On 04/23/2019 05:06 AM, Sumantro Mukherjee wrote:

Hi folks!

Fedora 30 Upgrade test day is
happening this Friday (2019-04-26): We'll be testing upgrades from Fedora
28 and 29 to Fedora 30. If you have a bit of time, please do stop by
#fedora-test-day on Freenode IRC and help test. All the information on
how to test and so on is on the Test Day page:

https://fedoraproject.org/wiki/Test_Day:2019-04-26_F30_Upgrade_Test_Day 



Thanks folks!
--
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED 


___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org


___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Fedora 30-20190422.n.1 compose check report

[Fedora compose checker]

Missing expected images:

Atomichost qcow2 x86_64
Atomichost raw-xz x86_64

Failed openQA tests: 2/146 (x86_64), 1/2 (arm)

ID: 389227  Test: x86_64 Server-dvd-iso server_cockpit_default
URL: https://openqa.fedoraproject.org/tests/389227
ID: 389273  Test: x86_64 KDE-live-iso apps_startstop
URL: https://openqa.fedoraproject.org/tests/389273
ID: 389276  Test: arm Minimal-raw_xz-raw.xz 
install_arm_image_deployment_upload
URL: https://openqa.fedoraproject.org/tests/389276

Soft failed openQA tests: 3/24 (i386), 3/146 (x86_64)
(Tests completed, but using a workaround for a known bug)

ID: 389236  Test: i386 Server-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/389236
ID: 389237  Test: i386 Server-dvd-iso install_default
URL: https://openqa.fedoraproject.org/tests/389237
ID: 389246  Test: x86_64 Workstation-live-iso desktop_update_graphical
URL: https://openqa.fedoraproject.org/tests/389246
ID: 389255  Test: x86_64 Workstation-boot-iso memory_check
URL: https://openqa.fedoraproject.org/tests/389255
ID: 389256  Test: x86_64 Workstation-boot-iso memory_check@uefi
URL: https://openqa.fedoraproject.org/tests/389256
ID: 389260  Test: i386 Workstation-boot-iso memory_check
URL: https://openqa.fedoraproject.org/tests/389260

Passed openQA tests: 136/146 (x86_64), 21/24 (i386)

Skipped non-gating openQA tests: 6 of 172
-- 
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Fedora 30 compose report: 20190422.n.1 changes

[Fedora Branched Report]

OLD: Fedora-30-20190421.n.0
NEW: Fedora-30-20190422.n.1

= SUMMARY =
Added images:1
Dropped images:  5
Added packages:  0
Dropped packages:0
Upgraded packages:   7
Downgraded packages: 0

Size of added packages:  0 B
Size of dropped packages:0 B
Size of upgraded packages:   43.26 MiB
Size of downgraded packages: 0 B

Size change of upgraded packages:   102.26 KiB
Size change of downgraded packages: 0 B

= ADDED IMAGES =
Image: Astronomy_KDE live i386
Path: Labs/i386/iso/Fedora-Astronomy_KDE-Live-i386-30-20190422.n.1.iso

= DROPPED IMAGES =
Image: Python_Classroom vagrant-libvirt x86_64
Path: 
Labs/x86_64/images/Fedora-Python-Classroom-Vagrant-30-20190421.n.0.x86_64.vagrant-libvirt.box
Image: Python_Classroom vagrant-virtualbox x86_64
Path: 
Labs/x86_64/images/Fedora-Python-Classroom-Vagrant-30-20190421.n.0.x86_64.vagrant-virtualbox.box
Image: Cinnamon live x86_64
Path: Spins/x86_64/iso/Fedora-Cinnamon-Live-x86_64-30-20190421.n.0.iso
Image: Games live i386
Path: Labs/i386/iso/Fedora-Games-Live-i386-30-20190421.n.0.iso
Image: LXDE raw-xz armhfp
Path: Spins/armhfp/images/Fedora-LXDE-armhfp-30-20190421.n.0-sda.raw.xz

= ADDED PACKAGES =

= DROPPED PACKAGES =

= UPGRADED PACKAGES =
Package:  appstream-data-30-5.fc30
Old package:  appstream-data-30-4.fc30
Summary:  Fedora AppStream metadata
RPMs: appstream-data
Size: 16.92 MiB
Size change:  47.79 KiB
Changelog:
  * Thu Apr 18 2019 Kalev Lember  - 30-5
  - New metadata version


Package:  fedora-obsolete-packages-30-40
Old package:  fedora-obsolete-packages-30-35
Summary:  A package to obsolete retired packages
RPMs: fedora-obsolete-packages
Size: 53.49 KiB
Size change:  1.02 KiB
Changelog:
  * Sun Apr 14 2019 Miro Hron??ok  - 30-36
  - Obsolete python2-testify < 0.11.0-13

  * Mon Apr 15 2019 Miro Hron??ok  - 30-37
  - Obsolete python2-cinderclient < 3.5.0-2

  * Mon Apr 15 2019 Kevin Fenzi  - 30-38
  - Obsolete mongodb < 4.0.3-3 (#1700073)

  * Tue Apr 16 2019 Miro Hron??ok  - 30-39
  - Obsolete mongodb, mongodb-server, mongodb-test < 4.0.3-4 (#1700073)
  - Obsolete python2-certbot < 0.31.0-3 and python2-josepy < 1.1.0-7 (#1700045)

  * Tue Apr 16 2019 Orion Poplawski  - 30-40
  - Obsolete python2-envisage (#1700310)


Package:  fedora-release-30-1
Old package:  fedora-release-30-0.26
Summary:  Fedora release files
RPMs: fedora-release fedora-release-cinnamon fedora-release-cloud 
fedora-release-common fedora-release-container fedora-release-coreos 
fedora-release-iot fedora-release-kde fedora-release-matecompiz 
fedora-release-server fedora-release-silverblue fedora-release-snappy 
fedora-release-soas fedora-release-workstation fedora-release-xfce
Size: 173.81 KiB
Size change:  680 B
Changelog:
  * Thu Apr 18 2019 Mohan Boddu  - 30-1
  - Setup for F30 Final


Package:  fedora-repos-30-1
Old package:  fedora-repos-30-0.6
Summary:  Fedora package repositories
RPMs: fedora-gpg-keys fedora-repos fedora-repos-ostree 
fedora-repos-rawhide
Size: 127.54 KiB
Size change:  108 B
Changelog:
  * Thu Apr 18 2019 Mohan Boddu  - 30-1
  - Setup for F30 Final


Package:  gnome-shell-3.32.1-1.fc30
Old package:  gnome-shell-3.32.0-1.fc30
Summary:  Window management and application launching for GNOME
RPMs: gnome-shell
Size: 8.38 MiB
Size change:  9.88 KiB
Changelog:
  * Sat Mar 23 2019 Phil Wyett  - 3.32.0-2
  - Update source URL
  - Add gcc BuildRequires
  - Update versions required for gjs and mutter

  * Wed Apr 17 2019 Adam Williamson  - 3.32.0-3
  - Backport MR #463 and MR #494 to fix a couple of bugs
Resolves: #1696270
Resolves: #1690429

  * Wed Apr 17 2019 Florian M??llner  - 3.32.1-1
  - Update to 3.32.1


Package:  gnome-shell-extensions-3.32.1-1.fc30
Old package:  gnome-shell-extensions-3.32.0-1.fc30
Summary:  Modify and extend GNOME Shell functionality and behavior
RPMs: gnome-classic-session gnome-shell-extension-apps-menu 
gnome-shell-extension-auto-move-windows gnome-shell-extension-common 
gnome-shell-extension-drive-menu gnome-shell-extension-launch-new-instance 
gnome-shell-extension-native-window-placement gnome-shell-extension-places-menu 
gnome-shell-extension-screenshot-window-sizer gnome-shell-extension-user-theme 
gnome-shell-extension-window-list gnome-shell-extension-windowsNavigator 
gnome-shell-extension-workspace-indicator
Size: 326.74 KiB
Size change:  -1.98 KiB
Changelog:
  * Wed Apr 17 2019 Florian M??llner  - 3.32.1-1
  - Update to 3.32.1


Package:  mutter-3.32.1-1.fc30
Old package:  mutter-3.32.0-2.fc30
Summary:  Window and compositing manager based on Clutter
RPMs: mutter mutter-devel mutter-tests
Size: 17.29 MiB
Size change:  44.79 KiB
Changelog:
  * Tue Apr 16 2019 Adam Williamson  - 3.32.0-3
  - Rebuild with Meson fix for #1699099

  * Wed Apr 17 2019 Adam Williamson  - 3.3

[Test Day] Fedora 30 Upgrade Test Day 2019-04-26

[Sumantro Mukherjee]

Hi folks!

Fedora 30 Upgrade test day is
happening this Friday (2019-04-26): We'll be testing upgrades from Fedora
28 and 29 to Fedora 30. If you have a bit of time, please do stop by
#fedora-test-day on Freenode IRC and help test. All the information on
how to test and so on is on the Test Day page:

https://fedoraproject.org/wiki/Test_Day:2019-04-26_F30_Upgrade_Test_Day


Thanks folks!
-- 
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED 
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

[Test-Announce] [Test Day] Fedora 30 Upgrade Test Day 2019-04-26

[Sumantro Mukherjee]

Hi folks!

Fedora 30 Upgrade test day is
happening this Friday (2019-04-26): We'll be testing upgrades from Fedora
28 and 29 to Fedora 30. If you have a bit of time, please do stop by
#fedora-test-day on Freenode IRC and help test. All the information on
how to test and so on is on the Test Day page:

https://fedoraproject.org/wiki/Test_Day:2019-04-26_F30_Upgrade_Test_Day


Thanks folks!
-- 
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED 
___
test-announce mailing list -- test-announce@lists.fedoraproject.org
To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test-announce@lists.fedoraproject.org

Re: New Member introduction request.

[Sumantro Mukherjee]

On Mon, Apr 22, 2019 at 9:52 PM Akash Das  wrote:

> I've applied for it.
> My FAS ID is akashad2519
>

And you are now approved :)


>
> On Mon, Apr 22, 2019, 7:08 PM Sumantro Mukherjee 
> wrote:
>
>> Welcome to Fedora QA, It will be great if you apply for qa FAS group. If
>> you have, I have sponsored you by now. If you haven’t then please apply and
>> send me an email with your FAS ID and I will approve.
>>
>> You can start off by testing updates in [http://bodhi.fedoraproject.org/]
>> for Fedora 28, Fedora 29, and Fedora 30. Update testing is where a tester
>> tests a package and gives out a +1 Karma for PASS and -1 Karma for FAIL.
>> You can go to bodhi.fedoraproject.org where you can sort the packages
>> with Fedora Releases and tags viz “pending” & “testing”. You can read much
>> about update testing here [1]. You can also, use fedora-easy-karma for
>> giving out feedbacks.
>> You can start with Release Validation testing. In Release Validation all
>> you need to do is to check the nightly/TC/RC against certain criteria. For
>> example, let’s take the latest compose (Fedora 30 Branched 20190415.n.2),
>> you can run test cases which are mentioned [2] and submit your results in
>> the test matrix.
>>
>> Note that each of the test cases[3] will have “How to test” section which
>> will have the steps (to be executed sequentially) and if the results match
>> with the expected results you can mark it as pass by editing the wiki page
>> {{result|pass|}}. Always make sure to check for “Associated
>> release criterion” which can be found on the top of test case page, if your
>> test case fails you can mark it fail by editing the wiki page
>> {{result|fail|}} and file a bug at RHBZ [4] under Fedora.
>>
>> You can always find the ‘current’ validation pages using these addresses:
>>
>> https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test
>> https://fedoraproject.org/wiki/Test_Results:Current_Base_Test
>> https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test
>> https://fedoraproject.org/wiki/Test_Results:Current_Server_Test
>> https://fedoraproject.org/wiki/Test_Results:Current_Cloud_Test
>>
>> For Automation, you can start looking at Open QA[
>> https://fedoraproject.org/wiki/OpenQA] its maintained by Adamw.
>>
>> [1] https://fedoraproject.org/wiki/QA:Updates_Testing
>> [2]
>> https://fedoraproject.org/wiki/Test_Results:Fedora_30_Branched_20190415.n.2_Summary?rd=Test_Results:Current_Summary
>> [3] https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc
>> [4] https://bugzilla.redhat.com/
>>
>> Feel free to ping us on IRC if you need any help #fedora-qa@freenode.
>>
>> We have test days coming happening now which is a nice place to start,
>> please stay tuned to the @test list and help us testing!
>> The current test day can be found on
>> https://fedoraproject.org/wiki/Test_Day:Current?redirect=yes
>> Test days schedule can be found on the fedocal
>> https://apps.fedoraproject.org/calendar/list/QA/?subject=Test+Day
>>
>> On Thu, Apr 18, 2019 at 10:41 AM Akash Das 
>> wrote:
>>
>>> Hello,
>>> This is Akash Das here, I would like to request you for letting me work
>>> in your QnA as well as packaging, it'll be a good honour to help the team
>>> and to learn a lot of more things from our community.
>>> I'm having a bit knowledge of Linux administrator and have been working
>>> on Linux since past 1year.
>>>
>>> Thanking you.
>>>
>>> Your's faithfully,
>>> Akash Das
>>>
>>>
>>> ___
>>> test mailing list -- test@lists.fedoraproject.org
>>> To unsubscribe send an email to test-le...@lists.fedoraproject.org
>>> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
>>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>>> List Archives:
>>> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
>>>
>>
>>
>> --
>> //sumantro
>> Fedora QE
>> TRIED AND PERSONALLY TESTED, ERGO TRUSTED 
>> ___
>> test mailing list -- test@lists.fedoraproject.org
>> To unsubscribe send an email to test-le...@lists.fedoraproject.org
>> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives:
>> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
>>
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
>


-- 
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED 
___
test mailing list -- 

Fedora Rawhide-20190422.n.0 compose check report

[Fedora compose checker]

Missing expected images:

Atomichost raw-xz x86_64
Atomichost qcow2 x86_64

Compose FAILS proposed Rawhide gating check!
2 of 47 required tests failed
openQA tests matching unsatisfied gating requirements shown with **GATING** 
below

Failed openQA tests: 8/137 (x86_64), 4/24 (i386), 1/2 (arm)

ID: 388827  Test: x86_64 Server-dvd-iso modularity_tests
URL: https://openqa.fedoraproject.org/tests/388827
ID: 388834  Test: x86_64 Server-dvd-iso realmd_join_sssd **GATING**
URL: https://openqa.fedoraproject.org/tests/388834
ID: 388859  Test: x86_64 Workstation-boot-iso memory_check@uefi
URL: https://openqa.fedoraproject.org/tests/388859
ID: 388860  Test: x86_64 Workstation-boot-iso install_default@uefi 
**GATING**
URL: https://openqa.fedoraproject.org/tests/388860
ID: 388862  Test: i386 Workstation-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/388862
ID: 388863  Test: i386 Workstation-boot-iso memory_check
URL: https://openqa.fedoraproject.org/tests/388863
ID: 388876  Test: x86_64 KDE-live-iso apps_startstop
URL: https://openqa.fedoraproject.org/tests/388876
ID: 388878  Test: i386 KDE-live-iso install_default
URL: https://openqa.fedoraproject.org/tests/388878
ID: 388879  Test: arm Minimal-raw_xz-raw.xz 
install_arm_image_deployment_upload
URL: https://openqa.fedoraproject.org/tests/388879
ID: 388898  Test: x86_64 universal install_updates_img_local
URL: https://openqa.fedoraproject.org/tests/388898
ID: 388942  Test: x86_64 universal install_asian_language
URL: https://openqa.fedoraproject.org/tests/388942
ID: 388947  Test: x86_64 universal install_lvmthin@uefi
URL: https://openqa.fedoraproject.org/tests/388947
ID: 388967  Test: i386 universal install_package_set_kde
URL: https://openqa.fedoraproject.org/tests/388967

Soft failed openQA tests: 2/24 (i386), 8/137 (x86_64)
(Tests completed, but using a workaround for a known bug)

ID: 388839  Test: i386 Server-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/388839
ID: 388840  Test: i386 Server-dvd-iso install_default
URL: https://openqa.fedoraproject.org/tests/388840
ID: 388849  Test: x86_64 Workstation-live-iso desktop_update_graphical
URL: https://openqa.fedoraproject.org/tests/388849
ID: 388858  Test: x86_64 Workstation-boot-iso memory_check
URL: https://openqa.fedoraproject.org/tests/388858
ID: 388890  Test: x86_64 universal upgrade_minimal_64bit
URL: https://openqa.fedoraproject.org/tests/388890
ID: 388892  Test: x86_64 universal upgrade_server_64bit
URL: https://openqa.fedoraproject.org/tests/388892
ID: 388893  Test: x86_64 universal upgrade_server_domain_controller
URL: https://openqa.fedoraproject.org/tests/388893
ID: 388894  Test: x86_64 universal upgrade_realmd_client
URL: https://openqa.fedoraproject.org/tests/388894
ID: 388929  Test: x86_64 universal upgrade_2_server_64bit
URL: https://openqa.fedoraproject.org/tests/388929
ID: 388950  Test: x86_64 universal upgrade_2_minimal_64bit
URL: https://openqa.fedoraproject.org/tests/388950

Passed openQA tests: 121/137 (x86_64), 18/24 (i386)

Skipped non-gating openQA tests: 1 of 163
-- 
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Re: New Member introduction request.

[Akash Das]

I've applied for it.
My FAS ID is akashad2519

On Mon, Apr 22, 2019, 7:08 PM Sumantro Mukherjee 
wrote:

> Welcome to Fedora QA, It will be great if you apply for qa FAS group. If
> you have, I have sponsored you by now. If you haven’t then please apply and
> send me an email with your FAS ID and I will approve.
>
> You can start off by testing updates in [http://bodhi.fedoraproject.org/]
> for Fedora 28, Fedora 29, and Fedora 30. Update testing is where a tester
> tests a package and gives out a +1 Karma for PASS and -1 Karma for FAIL.
> You can go to bodhi.fedoraproject.org where you can sort the packages
> with Fedora Releases and tags viz “pending” & “testing”. You can read much
> about update testing here [1]. You can also, use fedora-easy-karma for
> giving out feedbacks.
> You can start with Release Validation testing. In Release Validation all
> you need to do is to check the nightly/TC/RC against certain criteria. For
> example, let’s take the latest compose (Fedora 30 Branched 20190415.n.2),
> you can run test cases which are mentioned [2] and submit your results in
> the test matrix.
>
> Note that each of the test cases[3] will have “How to test” section which
> will have the steps (to be executed sequentially) and if the results match
> with the expected results you can mark it as pass by editing the wiki page
> {{result|pass|}}. Always make sure to check for “Associated
> release criterion” which can be found on the top of test case page, if your
> test case fails you can mark it fail by editing the wiki page
> {{result|fail|}} and file a bug at RHBZ [4] under Fedora.
>
> You can always find the ‘current’ validation pages using these addresses:
>
> https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test
> https://fedoraproject.org/wiki/Test_Results:Current_Base_Test
> https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test
> https://fedoraproject.org/wiki/Test_Results:Current_Server_Test
> https://fedoraproject.org/wiki/Test_Results:Current_Cloud_Test
>
> For Automation, you can start looking at Open QA[
> https://fedoraproject.org/wiki/OpenQA] its maintained by Adamw.
>
> [1] https://fedoraproject.org/wiki/QA:Updates_Testing
> [2]
> https://fedoraproject.org/wiki/Test_Results:Fedora_30_Branched_20190415.n.2_Summary?rd=Test_Results:Current_Summary
> [3] https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc
> [4] https://bugzilla.redhat.com/
>
> Feel free to ping us on IRC if you need any help #fedora-qa@freenode.
>
> We have test days coming happening now which is a nice place to start,
> please stay tuned to the @test list and help us testing!
> The current test day can be found on
> https://fedoraproject.org/wiki/Test_Day:Current?redirect=yes
> Test days schedule can be found on the fedocal
> https://apps.fedoraproject.org/calendar/list/QA/?subject=Test+Day
>
> On Thu, Apr 18, 2019 at 10:41 AM Akash Das  wrote:
>
>> Hello,
>> This is Akash Das here, I would like to request you for letting me work
>> in your QnA as well as packaging, it'll be a good honour to help the team
>> and to learn a lot of more things from our community.
>> I'm having a bit knowledge of Linux administrator and have been working
>> on Linux since past 1year.
>>
>> Thanking you.
>>
>> Your's faithfully,
>> Akash Das
>>
>>
>> ___
>> test mailing list -- test@lists.fedoraproject.org
>> To unsubscribe send an email to test-le...@lists.fedoraproject.org
>> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives:
>> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
>>
>
>
> --
> //sumantro
> Fedora QE
> TRIED AND PERSONALLY TESTED, ERGO TRUSTED 
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
>
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Fedora rawhide compose report: 20190422.n.0 changes

[Fedora Rawhide Report]

OLD: Fedora-Rawhide-20190421.n.0
NEW: Fedora-Rawhide-20190422.n.0

= SUMMARY =
Added images:3
Dropped images:  5
Added packages:  0
Dropped packages:0
Upgraded packages:   28
Downgraded packages: 0

Size of added packages:  0 B
Size of dropped packages:0 B
Size of upgraded packages:   216.31 MiB
Size of downgraded packages: 0 B

Size change of upgraded packages:   44.58 MiB
Size change of downgraded packages: 0 B

= ADDED IMAGES =
Image: Xfce live i386
Path: Spins/i386/iso/Fedora-Xfce-Live-i386-Rawhide-20190422.n.0.iso
Image: LXQt live i386
Path: Spins/i386/iso/Fedora-LXQt-Live-i386-Rawhide-20190422.n.0.iso
Image: Security live i386
Path: Labs/i386/iso/Fedora-Security-Live-i386-Rawhide-20190422.n.0.iso

= DROPPED IMAGES =
Image: KDE raw-xz armhfp
Path: Spins/armhfp/images/Fedora-KDE-armhfp-Rawhide-20190421.n.0-sda.raw.xz
Image: Python_Classroom vagrant-virtualbox i386
Path: 
Labs/i386/images/Fedora-Python-Classroom-Vagrant-Rawhide-20190421.n.0.i386.vagrant-virtualbox.box
Image: Python_Classroom vagrant-libvirt i386
Path: 
Labs/i386/images/Fedora-Python-Classroom-Vagrant-Rawhide-20190421.n.0.i386.vagrant-libvirt.box
Image: Silverblue dvd-ostree x86_64
Path: 
Silverblue/x86_64/iso/Fedora-Silverblue-ostree-x86_64-Rawhide-20190421.n.0.iso
Image: Cinnamon live i386
Path: Spins/i386/iso/Fedora-Cinnamon-Live-i386-Rawhide-20190421.n.0.iso

= ADDED PACKAGES =

= DROPPED PACKAGES =

= UPGRADED PACKAGES =
Package:  bionetgen-2.4.0-5.fc31
Old package:  bionetgen-2.4.0-4.fc30
Summary:  Software for rule-based modeling of biochemical systems
RPMs: bionetgen bionetgen-perl
Size: 2.07 MiB
Size change:  666.64 KiB
Changelog:
  * Sat Apr 20 2019 Antonio Trande  - 2.4.0-5
  - Ready for MPI (disabled)
  - Bundle Sundials


Package:  cantor-18.12.3-3.fc31
Old package:  cantor-18.12.3-2.fc31
Summary:  KDE Frontend to Mathematical Software
RPMs: cantor cantor-devel cantor-libs python3-cantor
Size: 12.27 MiB
Size change:  519.97 KiB
Changelog:
  * Sun Apr 21 2019 Mukundan Ragavan  - 18.12.3-3
  - rebuild for libqalculate


Package:  cifs-utils-6.9-1.fc31
Old package:  cifs-utils-6.8-4.fc30
Summary:  Utilities for mounting and managing CIFS mounts
RPMs: cifs-utils cifs-utils-devel pam_cifscreds
Size: 747.99 KiB
Size change:  116.88 KiB
Changelog:
  * Sun Apr 21 2019 Jeff Layton - 6.9-1
  - Update to v6.9 release


Package:  dav1d-0.2.2-1.fc31
Old package:  dav1d-0.2.1-3.fc31
Summary:  AV1 cross-platform Decoder
RPMs: dav1d libdav1d libdav1d-devel
Size: 2.84 MiB
Size change:  17.89 KiB
Changelog:
  * Sun Apr 21 2019 Robert-Andr?? Mauchin  - 0.2.2-1
  - Release 0.2.2 (#1701494)


Package:  electrum-3.3.4-2.fc31
Old package:  electrum-3.3.4-1.fc31
Summary:  A lightweight Bitcoin Client
RPMs: electrum
Size: 3.28 MiB
Size change:  -56 B
Changelog:
  * Sun Apr 21 2019 Jonny Heggheim  - 3.3.4-2
  - Allow usage of aiorpcx-0.12


Package:  getdp-3.1.0-1.fc31
Old package:  getdp-2.11.3-9.fc30
Summary:  General Environment for the Treatment of Discrete Problems
RPMs: getdp getdp-devel
Size: 7.07 MiB
Size change:  2.82 MiB
Changelog:
  * Sat Apr 20 2019 Sandro Mani  - 3.1.0-1
  - Update to 3.1.0


Package:  gnome-shell-extension-dash-to-dock-66-1.fc31
Old package:  gnome-shell-extension-dash-to-dock-64-2.fc30
Summary:  Dock for the Gnome Shell by micxgx.gmail.com
RPMs: gnome-shell-extension-dash-to-dock
Size: 144.65 KiB
Size change:  320 B
Changelog:
  * Sun Apr 21 2019 Bj??rn Esser  - 66-1
  - Upgrade to 66 for GNOME 3.32 (f30) compatibility (rhbz#1700690)


Package:  infiniband-diags-2.1.0-3.fc31
Old package:  infiniband-diags-2.1.0-2.fc30
Summary:  OpenFabrics Alliance InfiniBand Diagnostic Tools
RPMs: infiniband-diags infiniband-diags-compat infiniband-diags-devel 
infiniband-diags-devel-static
Size: 2.16 MiB
Size change:  146.11 KiB
Changelog:
  * Sun Apr 21 2019 Honggang Li  - 2.1.0-3
  - Rebuild against latest opensm-3.3.22


Package:  libqalculate-3.1.0-1.fc31
Old package:  libqalculate-3.0.0-1.fc31
Summary:  Multi-purpose calculator library
RPMs: libqalculate libqalculate-devel qalculate
Size: 10.54 MiB
Size change:  217.54 KiB
Changelog:
  * Sat Apr 20 2019 Mukundan Ragavan  - 3.1.0-1
  - Update to 3.1.0


Package:  mediawriter-4.1.3-1.fc31
Old package:  mediawriter-4.1.2-2.fc30
Summary:  Fedora Media Writer
RPMs: mediawriter
Size: 21.79 MiB
Size change:  277.13 KiB
Changelog:
  * Sun Apr 21 2019 Martin Bza  - 4.1.3-1
  - Update to 4.1.3
  - Resolves #1574717


Package:  mingw-mediawriter-4.1.3-1.fc31
Old package:  mingw-mediawriter-4.1.2-2.fc30
Summary:  Fedora Media Writer
RPMs: mingw32-mediawriter mingw64-mediawriter
Size: 7.16 MiB
Size change:  291.98 KiB
Changelog:
  * Sun Apr 21 2019

Re: Introduction

[Sumantro Mukherjee]

Hey Kapil,

Welcome to Fedora QA, It will be great if you apply for qa FAS group. If
you have, I have sponsored you by now. If you haven’t then please apply and
send me an email with your FAS ID and I will approve.

You can start off by testing updates in [http://bodhi.fedoraproject.org/]
for Fedora 28, Fedora 29, and Fedora 30. Update testing is where a tester
tests a package and gives out a +1 Karma for PASS and -1 Karma for FAIL.
You can go to bodhi.fedoraproject.org where you can sort the packages with
Fedora Releases and tags viz “pending” & “testing”. You can read much about
update testing here [1]. You can also, use fedora-easy-karma for giving out
feedbacks.
You can start with Release Validation testing. In Release Validation all
you need to do is to check the nightly/TC/RC against certain criteria. For
example, let’s take the latest compose (Fedora 30 Branched 20190415.n.2),
you can run test cases which are mentioned [2] and submit your results in
the test matrix.

Note that each of the test cases[3] will have “How to test” section which
will have the steps (to be executed sequentially) and if the results match
with the expected results you can mark it as pass by editing the wiki page
{{result|PASS|}}. Always make sure to check for “Associated
release criterion” which can be found on the top of test case page, if your
test case fails you can mark it fail by editing the wiki page
{{result|FAIL|}} and file a bug at RHBZ [4] under Fedora.

You can always find the ‘current’ validation pages using these addresses:

https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test
https://fedoraproject.org/wiki/Test_Results:Current_Base_Test
https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test
https://fedoraproject.org/wiki/Test_Results:Current_Server_Test
https://fedoraproject.org/wiki/Test_Results:Current_Cloud_Test

For Automation, you can start looking at Open QA[
https://fedoraproject.org/wiki/OpenQA] its maintained by Adamw.

[1] https://fedoraproject.org/wiki/QA:Updates_Testing
[2]
https://fedoraproject.org/wiki/Test_Results:Fedora_30_Branched_20190415.n.2_Summary?rd=Test_Results:Current_Summary
[3] https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc
[4] https://bugzilla.redhat.com/

Feel free to ping us on IRC if you need any help #fedora-qa@freenode.

We have test days coming happening now which is a nice place to start,
please stay tuned to the @test list and help us testing!
The current test day can be found on
https://fedoraproject.org/wiki/Test_Day:Current?redirect=yes
Test days schedule can be found on the fedocal
https://apps.fedoraproject.org/calendar/list/QA/?subject=Test+Day

On Sun, Apr 14, 2019 at 2:35 PM Kapil Modi  wrote:

> Hi team,
> My Name is Kapil Modi i am working in Linux since last 4 years. I was
> also  a part of Open Source Summit, Tokyo .
> I am currently working in Dell as a DevOps Engineer. I'm 21 years old and
> live at Jaipur,Rajasthan
>
> So, thanks a lot for some people who accepted me at Fedora Project.
>
> Thanks and Regards,
> Kapil Modi
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
>


-- 
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED 
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Re: New Member Introduction

[Sumantro Mukherjee]

Hey Ajinkya,

Welcome to Fedora QA, It will be great if you apply for qa FAS group. If
you have, I have sponsored you by now. If you haven’t then please apply and
send me an email with your FAS ID and I will approve.

You can start off by testing updates in [http://bodhi.fedoraproject.org/]
for Fedora 28, Fedora 29, and Fedora 30. Update testing is where a tester
tests a package and gives out a +1 Karma for PASS and -1 Karma for FAIL.
You can go to bodhi.fedoraproject.org where you can sort the packages with
Fedora Releases and tags viz “pending” & “testing”. You can read much about
update testing here [1]. You can also, use fedora-easy-karma for giving out
feedbacks.
You can start with Release Validation testing. In Release Validation all
you need to do is to check the nightly/TC/RC against certain criteria. For
example, let’s take the latest compose (Fedora 30 Branched 20190415.n.2),
you can run test cases which are mentioned [2] and submit your results in
the test matrix.

Note that each of the test cases[3] will have “How to test” section which
will have the steps (to be executed sequentially) and if the results match
with the expected results you can mark it as pass by editing the wiki page
{{result|PASS|}}. Always make sure to check for “Associated
release criterion” which can be found on the top of test case page, if your
test case fails you can mark it fail by editing the wiki page
{{result|FAIL|}} and file a bug at RHBZ [4] under Fedora.

You can always find the ‘current’ validation pages using these addresses:

https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test
https://fedoraproject.org/wiki/Test_Results:Current_Base_Test
https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test
https://fedoraproject.org/wiki/Test_Results:Current_Server_Test
https://fedoraproject.org/wiki/Test_Results:Current_Cloud_Test

For Automation, you can start looking at Open QA[
https://fedoraproject.org/wiki/OpenQA] its maintained by Adamw.

[1] https://fedoraproject.org/wiki/QA:Updates_Testing
[2]
https://fedoraproject.org/wiki/Test_Results:Fedora_30_Branched_20190415.n.2_Summary?rd=Test_Results:Current_Summary
[3] https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc
[4] https://bugzilla.redhat.com/

Feel free to ping us on IRC if you need any help #fedora-qa@freenode.

We have test days coming happening now which is a nice place to start,
please stay tuned to the @test list and help us testing!
The current test day can be found on
https://fedoraproject.org/wiki/Test_Day:Current?redirect=yes
Test days schedule can be found on the fedocal
https://apps.fedoraproject.org/calendar/list/QA/?subject=Test+Day

On Sun, Apr 14, 2019 at 2:35 PM Ajinkya Deshpande <
meetajinkya.deshpa...@outlook.com> wrote:

> Hi Team,
>
> Ajinkya Deshpande  here , Currently working in Veritas as Associate
>  software Engg.
>
> I would love to contribute in Fedora , I am a big learner of Unix
> operating system and from last 6 months I am reading UNIX SYSYTEM design by
> Maurice J Bach.
>
> I would love to contribute in Development and Testing domain.
>
>
>
> Thanks,
>
> Ajinkya Deshpande
>
>
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
>


-- 
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED 
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Re: New Member introduction

[Sumantro Mukherjee]

Hey Gourav,

Welcome to Fedora QA, It will be great if you apply for qa FAS group. If
you have, I have sponsored you by now. If you haven’t then please apply and
send me an email with your FAS ID and I will approve.

You can start off by testing updates in [http://bodhi.fedoraproject.org/]
for Fedora 28, Fedora 29, and Fedora 30. Update testing is where a tester
tests a package and gives out a +1 Karma for PASS and -1 Karma for FAIL.
You can go to bodhi.fedoraproject.org where you can sort the packages with
Fedora Releases and tags viz “pending” & “testing”. You can read much about
update testing here [1]. You can also, use fedora-easy-karma for giving out
feedbacks.
You can start with Release Validation testing. In Release Validation all
you need to do is to check the nightly/TC/RC against certain criteria. For
example, let’s take the latest compose (Fedora 30 Branched 20190415.n.2),
you can run test cases which are mentioned [2] and submit your results in
the test matrix.

Note that each of the test cases[3] will have “How to test” section which
will have the steps (to be executed sequentially) and if the results match
with the expected results you can mark it as pass by editing the wiki page
{{result|PASS|}}. Always make sure to check for “Associated
release criterion” which can be found on the top of test case page, if your
test case fails you can mark it fail by editing the wiki page
{{result|FAIL|}} and file a bug at RHBZ [4] under Fedora.

You can always find the ‘current’ validation pages using these addresses:

https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test
https://fedoraproject.org/wiki/Test_Results:Current_Base_Test
https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test
https://fedoraproject.org/wiki/Test_Results:Current_Server_Test
https://fedoraproject.org/wiki/Test_Results:Current_Cloud_Test

For Automation, you can start looking at Open QA[
https://fedoraproject.org/wiki/OpenQA] its maintained by Adamw.

[1] https://fedoraproject.org/wiki/QA:Updates_Testing
[2]
https://fedoraproject.org/wiki/Test_Results:Fedora_30_Branched_20190415.n.2_Summary?rd=Test_Results:Current_Summary
[3] https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc
[4] https://bugzilla.redhat.com/

Feel free to ping us on IRC if you need any help #fedora-qa@freenode.

We have test days coming happening now which is a nice place to start,
please stay tuned to the @test list and help us testing!
The current test day can be found on
https://fedoraproject.org/wiki/Test_Day:Current?redirect=yes
Test days schedule can be found on the fedocal
https://apps.fedoraproject.org/calendar/list/QA/?subject=Test+Day

On Sun, Apr 14, 2019 at 2:36 PM Gourav Sharma  wrote:

> Hi Team,
> Myself  Gourav Sharma, i'm Learning and Development Instructor at REDHAT.
> Currently I'm RHCA-Level6 (cert id - 140-149-584 ) and yes main key domain
> i work in are Platform and DevOps.
> I love to play with Security part of linux and have a keen intrest in
> teaching new techies and learning trends going into market.
> If i have to kill other than mosquitoes then i will kill coding in this
> world.
> but yes someone can help me in learning that i'm happy for that.
>
> Open to teach technologies like ansible, docker, container, puppet, ceph,
> gluster,etc
>
>
> Thanks
> Gourav Sharma
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
>


-- 
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED 
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Re: new member introduction to join team

[Sumantro Mukherjee]

Hey Vipul,

Welcome to Fedora QA, It will be great if you apply for qa FAS group. If
you have, I have sponsored you by now. If you haven’t then please apply and
send me an email with your FAS ID and I will approve.

You can start off by testing updates in [http://bodhi.fedoraproject.org/]
for Fedora 28, Fedora 29, and Fedora 30. Update testing is where a tester
tests a package and gives out a +1 Karma for PASS and -1 Karma for FAIL.
You can go to bodhi.fedoraproject.org where you can sort the packages with
Fedora Releases and tags viz “pending” & “testing”. You can read much about
update testing here [1]. You can also, use fedora-easy-karma for giving out
feedbacks.
You can start with Release Validation testing. In Release Validation all
you need to do is to check the nightly/TC/RC against certain criteria. For
example, let’s take the latest compose (Fedora 30 Branched 20190415.n.2),
you can run test cases which are mentioned [2] and submit your results in
the test matrix.

Note that each of the test cases[3] will have “How to test” section which
will have the steps (to be executed sequentially) and if the results match
with the expected results you can mark it as pass by editing the wiki page
{{result|PASS|}}. Always make sure to check for “Associated
release criterion” which can be found on the top of test case page, if your
test case fails you can mark it fail by editing the wiki page
{{result|FAIL|}} and file a bug at RHBZ [4] under Fedora.

You can always find the ‘current’ validation pages using these addresses:

https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test
https://fedoraproject.org/wiki/Test_Results:Current_Base_Test
https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test
https://fedoraproject.org/wiki/Test_Results:Current_Server_Test
https://fedoraproject.org/wiki/Test_Results:Current_Cloud_Test

For Automation, you can start looking at Open QA[
https://fedoraproject.org/wiki/OpenQA] its maintained by Adamw.

[1] https://fedoraproject.org/wiki/QA:Updates_Testing
[2]
https://fedoraproject.org/wiki/Test_Results:Fedora_30_Branched_20190415.n.2_Summary?rd=Test_Results:Current_Summary
[3] https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc
[4] https://bugzilla.redhat.com/

Feel free to ping us on IRC if you need any help #fedora-qa@freenode.

We have test days coming happening now which is a nice place to start,
please stay tuned to the @test list and help us testing!
The current test day can be found on
https://fedoraproject.org/wiki/Test_Day:Current?redirect=yes
Test days schedule can be found on the fedocal
https://apps.fedoraproject.org/calendar/list/QA/?subject=Test+Day

On Sun, Apr 14, 2019 at 2:37 PM Vipul Jain  wrote:

> Hi Team,
>
> Myself Vipul Jain. I'm very glad to join at Fedora.
>
> I started on Linux from my school time. I am working on RedHat Linux from
> last 6 years.
>
> I am RedHat certified system administrator. i am working in SAP
> It would be my pleasure to join Fedora Community
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
>


-- 
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED 
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Re: intro

[Sumantro Mukherjee]

Hey Rudra,

Welcome to Fedora QA, It will be great if you apply for qa FAS group. If
you have, I have sponsored you by now. If you haven’t then please apply and
send me an email with your FAS ID and I will approve.

You can start off by testing updates in [http://bodhi.fedoraproject.org/]
for Fedora 28, Fedora 29, and Fedora 30. Update testing is where a tester
tests a package and gives out a +1 Karma for PASS and -1 Karma for FAIL.
You can go to bodhi.fedoraproject.org where you can sort the packages with
Fedora Releases and tags viz “pending” & “testing”. You can read much about
update testing here [1]. You can also, use fedora-easy-karma for giving out
feedbacks.
You can start with Release Validation testing. In Release Validation all
you need to do is to check the nightly/TC/RC against certain criteria. For
example, let’s take the latest compose (Fedora 30 Branched 20190415.n.2),
you can run test cases which are mentioned [2] and submit your results in
the test matrix.

Note that each of the test cases[3] will have “How to test” section which
will have the steps (to be executed sequentially) and if the results match
with the expected results you can mark it as pass by editing the wiki page
{{result|PASS|}}. Always make sure to check for “Associated
release criterion” which can be found on the top of test case page, if your
test case fails you can mark it fail by editing the wiki page
{{result|FAIL|}} and file a bug at RHBZ [4] under Fedora.

You can always find the ‘current’ validation pages using these addresses:

https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test
https://fedoraproject.org/wiki/Test_Results:Current_Base_Test
https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test
https://fedoraproject.org/wiki/Test_Results:Current_Server_Test
https://fedoraproject.org/wiki/Test_Results:Current_Cloud_Test

For Automation, you can start looking at Open QA[
https://fedoraproject.org/wiki/OpenQA] its maintained by Adamw.

[1] https://fedoraproject.org/wiki/QA:Updates_Testing
[2]
https://fedoraproject.org/wiki/Test_Results:Fedora_30_Branched_20190415.n.2_Summary?rd=Test_Results:Current_Summary
[3] https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc
[4] https://bugzilla.redhat.com/

Feel free to ping us on IRC if you need any help #fedora-qa@freenode.

We have test days coming happening now which is a nice place to start,
please stay tuned to the @test list and help us testing!
The current test day can be found on
https://fedoraproject.org/wiki/Test_Day:Current?redirect=yes
Test days schedule can be found on the fedocal
https://apps.fedoraproject.org/calendar/list/QA/?subject=Test+Day


P S : Ping me directly and I will help you to get started with other
interests of yours :)

On Sun, Apr 14, 2019 at 2:40 PM RUDRA PRATAP 
wrote:

> Hello sir,
> Myself RUDRA PRATAP from HIT, haldia. I'm pursuing by btech degree from
> hit haldia from cse and I'm in final year.
> Hands on Linux experience from first year only.
> Then i completed some certification from redhat, like RHCSA, RHCE, ANSIBLE
> AUTOMATION, OPENSHIFT, SERVER HARDENING and i have to give two more in the
> month of may, TROUBLESHOOTING and CHEF STORAGE. Beside this i have working
> in dot net and php. Sometimes i used to go through CISCO and ML concepts.
>
>
> I would love to work for fedora community,
>
> Basically i would like to go with
> 1) QUALITY ASSURANCE
> 2) PACKAGING...
>
> Thank you sir
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
>


-- 
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED 
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Re: Introduction Mail

[Sumantro Mukherjee]

Hey Ayush,

Welcome to Fedora QA, It will be great if you apply for qa FAS group. If
you have, I have sponsored you by now. If you haven’t then please apply and
send me an email with your FAS ID and I will approve.

You can start off by testing updates in [http://bodhi.fedoraproject.org/]
for Fedora 28, Fedora 29, and Fedora 30. Update testing is where a tester
tests a package and gives out a +1 Karma for PASS and -1 Karma for FAIL.
You can go to bodhi.fedoraproject.org where you can sort the packages with
Fedora Releases and tags viz “pending” & “testing”. You can read much about
update testing here [1]. You can also, use fedora-easy-karma for giving out
feedbacks.
You can start with Release Validation testing. In Release Validation all
you need to do is to check the nightly/TC/RC against certain criteria. For
example, let’s take the latest compose (Fedora 30 Branched 20190415.n.2),
you can run test cases which are mentioned [2] and submit your results in
the test matrix.

Note that each of the test cases[3] will have “How to test” section which
will have the steps (to be executed sequentially) and if the results match
with the expected results you can mark it as pass by editing the wiki page
{{result|PASS|}}. Always make sure to check for “Associated
release criterion” which can be found on the top of test case page, if your
test case fails you can mark it fail by editing the wiki page
{{result|FAIL|}} and file a bug at RHBZ [4] under Fedora.

You can always find the ‘current’ validation pages using these addresses:

https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test
https://fedoraproject.org/wiki/Test_Results:Current_Base_Test
https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test
https://fedoraproject.org/wiki/Test_Results:Current_Server_Test
https://fedoraproject.org/wiki/Test_Results:Current_Cloud_Test

For Automation, you can start looking at Open QA[
https://fedoraproject.org/wiki/OpenQA] its maintained by Adamw.

[1] https://fedoraproject.org/wiki/QA:Updates_Testing
[2]
https://fedoraproject.org/wiki/Test_Results:Fedora_30_Branched_20190415.n.2_Summary?rd=Test_Results:Current_Summary
[3] https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc
[4] https://bugzilla.redhat.com/

Feel free to ping us on IRC if you need any help #fedora-qa@freenode.

We have test days coming happening now which is a nice place to start,
please stay tuned to the @test list and help us testing!
The current test day can be found on
https://fedoraproject.org/wiki/Test_Day:Current?redirect=yes
Test days schedule can be found on the fedocal
https://apps.fedoraproject.org/calendar/list/QA/?subject=Test+Day

On Sun, Apr 14, 2019 at 2:43 PM Ayush Sharma <69ayushsha...@gmail.com>
wrote:

> Hey Team,
> Ayush [itsayuhs] this side!
> I'm currently working as a Full Stack Python Developer and DevOps Intern
> at ATMECS Technologies, Hyderabad.
> I hold few certifications in technologies like Ansible, OpenShift and I'm
> also a RedHat certified Engineer and System Administrator.
> As a Technology Enthusiast, I have a knack for learning, integrating and
> using new technologies that solve the problem at hand.
>
> Regards,
> itsayushs
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
>


-- 
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED 
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Re: introduction

[Sumantro Mukherjee]

Hey Kanika,

Welcome to Fedora QA, It will be great if you apply for qa FAS group. If
you have, I have sponsored you by now. If you haven’t then please apply and
send me an email with your FAS ID and I will approve.

You can start off by testing updates in [http://bodhi.fedoraproject.org/]
for Fedora 28, Fedora 29, and Fedora 30. Update testing is where a tester
tests a package and gives out a +1 Karma for PASS and -1 Karma for FAIL.
You can go to bodhi.fedoraproject.org where you can sort the packages with
Fedora Releases and tags viz “pending” & “testing”. You can read much about
update testing here [1]. You can also, use fedora-easy-karma for giving out
feedbacks.
You can start with Release Validation testing. In Release Validation all
you need to do is to check the nightly/TC/RC against certain criteria. For
example, let’s take the latest compose (Fedora 30 Branched 20190415.n.2),
you can run test cases which are mentioned [2] and submit your results in
the test matrix.

Note that each of the test cases[3] will have “How to test” section which
will have the steps (to be executed sequentially) and if the results match
with the expected results you can mark it as pass by editing the wiki page
{{result|PASS|}}. Always make sure to check for “Associated
release criterion” which can be found on the top of test case page, if your
test case fails you can mark it fail by editing the wiki page
{{result|FAIL|}} and file a bug at RHBZ [4] under Fedora.

You can always find the ‘current’ validation pages using these addresses:

https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test
https://fedoraproject.org/wiki/Test_Results:Current_Base_Test
https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test
https://fedoraproject.org/wiki/Test_Results:Current_Server_Test
https://fedoraproject.org/wiki/Test_Results:Current_Cloud_Test

For Automation, you can start looking at Open QA[
https://fedoraproject.org/wiki/OpenQA] its maintained by Adamw.

[1] https://fedoraproject.org/wiki/QA:Updates_Testing
[2]
https://fedoraproject.org/wiki/Test_Results:Fedora_30_Branched_20190415.n.2_Summary?rd=Test_Results:Current_Summary
[3] https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc
[4] https://bugzilla.redhat.com/

Feel free to ping us on IRC if you need any help #fedora-qa@freenode.

We have test days coming happening now which is a nice place to start,
please stay tuned to the @test list and help us testing!
The current test day can be found on
https://fedoraproject.org/wiki/Test_Day:Current?redirect=yes
Test days schedule can be found on the fedocal
https://apps.fedoraproject.org/calendar/list/QA/?subject=Test+Day


P. S: For Packaging and Documentation there are different mailing list and
ping me directly I can help you get started.

On Sun, Apr 14, 2019 at 2:44 PM kanika jindal 
wrote:

> Hello sir,
> Myself KANIKA JINDAL from RTU, KOTA. I'm pursuing by btech degree from RTU
> in IT dept and I'm in final year.
> Have some certification from RedHat, like RHCSA, ANSIBLE AUTOMATION etc.
> Beside this i have worked on Linux Platform, CLOUD, HADOOP, etc as well as
> some tools like SPLUNK, CASSANDRA etc.
>
>
> I would love to work for fedora community,
>
> Basically i would like to go with
> 1) QUALITY ASSURANCE
> 2) PACKAGING
> 3) DOCUMENTATION
>
> Thank you sir
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
>


-- 
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED 
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Re: Introduction

[Sumantro Mukherjee]

Hey Amit,

Welcome to Fedora QA, It will be great if you apply for qa FAS group. If
you have, I have sponsored you by now. If you haven’t then please apply and
send me an email with your FAS ID and I will approve.

You can start off by testing updates in [http://bodhi.fedoraproject.org/]
for Fedora 28, Fedora 29, and Fedora 30. Update testing is where a tester
tests a package and gives out a +1 Karma for PASS and -1 Karma for FAIL.
You can go to bodhi.fedoraproject.org where you can sort the packages with
Fedora Releases and tags viz “pending” & “testing”. You can read much about
update testing here [1]. You can also, use fedora-easy-karma for giving out
feedbacks.
You can start with Release Validation testing. In Release Validation all
you need to do is to check the nightly/TC/RC against certain criteria. For
example, let’s take the latest compose (Fedora 30 Branched 20190415.n.2),
you can run test cases which are mentioned [2] and submit your results in
the test matrix.

Note that each of the test cases[3] will have “How to test” section which
will have the steps (to be executed sequentially) and if the results match
with the expected results you can mark it as pass by editing the wiki page
{{result|PASS|}}. Always make sure to check for “Associated
release criterion” which can be found on the top of test case page, if your
test case fails you can mark it fail by editing the wiki page
{{result|FAIL|}} and file a bug at RHBZ [4] under Fedora.

You can always find the ‘current’ validation pages using these addresses:

https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test
https://fedoraproject.org/wiki/Test_Results:Current_Base_Test
https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test
https://fedoraproject.org/wiki/Test_Results:Current_Server_Test
https://fedoraproject.org/wiki/Test_Results:Current_Cloud_Test

For Automation, you can start looking at Open QA[
https://fedoraproject.org/wiki/OpenQA] its maintained by Adamw.

[1] https://fedoraproject.org/wiki/QA:Updates_Testing
[2]
https://fedoraproject.org/wiki/Test_Results:Fedora_30_Branched_20190415.n.2_Summary?rd=Test_Results:Current_Summary
[3] https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc
[4] https://bugzilla.redhat.com/

Feel free to ping us on IRC if you need any help #fedora-qa@freenode.

We have test days coming happening now which is a nice place to start,
please stay tuned to the @test list and help us testing!
The current test day can be found on
https://fedoraproject.org/wiki/Test_Day:Current?redirect=yes
Test days schedule can be found on the fedocal
https://apps.fedoraproject.org/calendar/list/QA/?subject=Test+Day

On Sun, Apr 14, 2019 at 3:05 PM Amit kumar  wrote:

> Hi All,
>
> I am glad to join the Fedora community. My username is singhamit.
> I am working on Linux on from last 5 years and I have a good working
> experience
> on Networking, Cloud, AWS, Hadoop, Hive, etc.
>
> Currently, I am working in Yulu as a Data Engineer from last 2 years and
> handling Yulu architecture.
>
> Thanks
>
> Amit Kumar
>
>
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
>


-- 
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED 
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Re: Introduce as a New Member

[Sumantro Mukherjee]

Hey Himanshu,

Welcome to Fedora QA, It will be great if you apply for qa FAS group. If
you have, I have sponsored you by now. If you haven’t then please apply and
send me an email with your FAS ID and I will approve.

You can start off by testing updates in [http://bodhi.fedoraproject.org/]
for Fedora 28, Fedora 29, and Fedora 30. Update testing is where a tester
tests a package and gives out a +1 Karma for PASS and -1 Karma for FAIL.
You can go to bodhi.fedoraproject.org where you can sort the packages with
Fedora Releases and tags viz “pending” & “testing”. You can read much about
update testing here [1]. You can also, use fedora-easy-karma for giving out
feedbacks.
You can start with Release Validation testing. In Release Validation all
you need to do is to check the nightly/TC/RC against certain criteria. For
example, let’s take the latest compose (Fedora 30 Branched 20190415.n.2),
you can run test cases which are mentioned [2] and submit your results in
the test matrix.

Note that each of the test cases[3] will have “How to test” section which
will have the steps (to be executed sequentially) and if the results match
with the expected results you can mark it as pass by editing the wiki page
{{result|PASS|}}. Always make sure to check for “Associated
release criterion” which can be found on the top of test case page, if your
test case fails you can mark it fail by editing the wiki page
{{result|FAIL|}} and file a bug at RHBZ [4] under Fedora.

You can always find the ‘current’ validation pages using these addresses:

https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test
https://fedoraproject.org/wiki/Test_Results:Current_Base_Test
https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test
https://fedoraproject.org/wiki/Test_Results:Current_Server_Test
https://fedoraproject.org/wiki/Test_Results:Current_Cloud_Test

For Automation, you can start looking at Open QA[
https://fedoraproject.org/wiki/OpenQA] its maintained by Adamw.

[1] https://fedoraproject.org/wiki/QA:Updates_Testing
[2]
https://fedoraproject.org/wiki/Test_Results:Fedora_30_Branched_20190415.n.2_Summary?rd=Test_Results:Current_Summary
[3] https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc
[4] https://bugzilla.redhat.com/

Feel free to ping us on IRC if you need any help #fedora-qa@freenode.

We have test days coming happening now which is a nice place to start,
please stay tuned to the @test list and help us testing!
The current test day can be found on
https://fedoraproject.org/wiki/Test_Day:Current?redirect=yes
Test days schedule can be found on the fedocal
https://apps.fedoraproject.org/calendar/list/QA/?subject=Test+Day

On Sun, Apr 14, 2019 at 3:05 PM Himanshu Tak  wrote:

> Hi team,
> I`m Himanshu Tank, pursuing my B.Tech from Govt. Engineering College,
> Bikaner(final year student). I have done sort of RedHat Courses to gain the
> title of RHCA(Cert ID:- 180-112-880), done with RHCSA and two architect
> level of exam 3 are left for RHCA. I love to learn RedHat technologies and
> work on these technologies. Currently working on Ansible, OpenShift, Ceph,
> Kubernetes, RHEL security and Troubleshoot.
>
> Thank You !!!
> Attachments area
>
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
>


-- 
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED 
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Re: INTRODUCTION

[Sumantro Mukherjee]

Hey Dhiraj,

Welcome to Fedora QA, It will be great if you apply for qa FAS group. If
you have, I have sponsored you by now. If you haven’t then please apply and
send me an email with your FAS ID and I will approve.

You can start off by testing updates in [http://bodhi.fedoraproject.org/]
for Fedora 28, Fedora 29, and Fedora 30. Update testing is where a tester
tests a package and gives out a +1 Karma for PASS and -1 Karma for FAIL.
You can go to bodhi.fedoraproject.org where you can sort the packages with
Fedora Releases and tags viz “pending” & “testing”. You can read much about
update testing here [1]. You can also, use fedora-easy-karma for giving out
feedbacks.
You can start with Release Validation testing. In Release Validation all
you need to do is to check the nightly/TC/RC against certain criteria. For
example, let’s take the latest compose (Fedora 30 Branched 20190415.n.2),
you can run test cases which are mentioned [2] and submit your results in
the test matrix.

Note that each of the test cases[3] will have “How to test” section which
will have the steps (to be executed sequentially) and if the results match
with the expected results you can mark it as pass by editing the wiki page
{{result|PASS|}}. Always make sure to check for “Associated
release criterion” which can be found on the top of test case page, if your
test case fails you can mark it fail by editing the wiki page
{{result|FAIL|}} and file a bug at RHBZ [4] under Fedora.

You can always find the ‘current’ validation pages using these addresses:

https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test
https://fedoraproject.org/wiki/Test_Results:Current_Base_Test
https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test
https://fedoraproject.org/wiki/Test_Results:Current_Server_Test
https://fedoraproject.org/wiki/Test_Results:Current_Cloud_Test

For Automation, you can start looking at Open QA[
https://fedoraproject.org/wiki/OpenQA] its maintained by Adamw.

[1] https://fedoraproject.org/wiki/QA:Updates_Testing
[2]
https://fedoraproject.org/wiki/Test_Results:Fedora_30_Branched_20190415.n.2_Summary?rd=Test_Results:Current_Summary
[3] https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc
[4] https://bugzilla.redhat.com/

Feel free to ping us on IRC if you need any help #fedora-qa@freenode.

We have test days coming happening now which is a nice place to start,
please stay tuned to the @test list and help us testing!
The current test day can be found on
https://fedoraproject.org/wiki/Test_Day:Current?redirect=yes
Test days schedule can be found on the fedocal
https://apps.fedoraproject.org/calendar/list/QA/?subject=Test+Day

On Sun, Apr 14, 2019 at 3:16 PM Dhiraj Kumar 
wrote:

> hello Guys,
>
> This is Dhiraj Yadav  (dhiraj19).
>
> I have been working in Linux for the past year.
> I have different RedHat certificates like for ANSIBLE , OPENSHIFT .
> i have a considerable knowledge at python development as well as in C ,
> C++.
>
> I am a technological enthusiast  adn looking eagerly forward to be workng
> with you guys.
> thankyou,
>
> Dhiraj Yadav
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
>


-- 
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED 
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Re: Introduction: Abhishek Sharma

[Sumantro Mukherjee]

Hey Abhishek,

Welcome to Fedora QA, It will be great if you apply for qa FAS group. If
you have, I have sponsored you by now. If you haven’t then please apply and
send me an email with your FAS ID and I will approve.

You can start off by testing updates in [http://bodhi.fedoraproject.org/]
for Fedora 28, Fedora 29, and Fedora 30. Update testing is where a tester
tests a package and gives out a +1 Karma for PASS and -1 Karma for FAIL.
You can go to bodhi.fedoraproject.org where you can sort the packages with
Fedora Releases and tags viz “pending” & “testing”. You can read much about
update testing here [1]. You can also, use fedora-easy-karma for giving out
feedbacks.
You can start with Release Validation testing. In Release Validation all
you need to do is to check the nightly/TC/RC against certain criteria. For
example, let’s take the latest compose (Fedora 30 Branched 20190415.n.2),
you can run test cases which are mentioned [2] and submit your results in
the test matrix.

Note that each of the test cases[3] will have “How to test” section which
will have the steps (to be executed sequentially) and if the results match
with the expected results you can mark it as pass by editing the wiki page
{{result|PASS|}}. Always make sure to check for “Associated
release criterion” which can be found on the top of test case page, if your
test case fails you can mark it fail by editing the wiki page
{{result|FAIL|}} and file a bug at RHBZ [4] under Fedora.

You can always find the ‘current’ validation pages using these addresses:

https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test
https://fedoraproject.org/wiki/Test_Results:Current_Base_Test
https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test
https://fedoraproject.org/wiki/Test_Results:Current_Server_Test
https://fedoraproject.org/wiki/Test_Results:Current_Cloud_Test

For Automation, you can start looking at Open QA[
https://fedoraproject.org/wiki/OpenQA] its maintained by Adamw.

[1] https://fedoraproject.org/wiki/QA:Updates_Testing
[2]
https://fedoraproject.org/wiki/Test_Results:Fedora_30_Branched_20190415.n.2_Summary?rd=Test_Results:Current_Summary
[3] https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc
[4] https://bugzilla.redhat.com/

Feel free to ping us on IRC if you need any help #fedora-qa@freenode.

We have test days coming happening now which is a nice place to start,
please stay tuned to the @test list and help us testing!
The current test day can be found on
https://fedoraproject.org/wiki/Test_Day:Current?redirect=yes
Test days schedule can be found on the fedocal
https://apps.fedoraproject.org/calendar/list/QA/?subject=Test+Day

On Sun, Apr 14, 2019 at 4:09 PM Abhishek Sharma 
wrote:

> Hi guys,
>
> I'm very glad to join at Fedora Bug Zappers Team. I have worked a lot
> with Fedora and Red Hat Linux since some years ago. So, let's time to
> contribute to the project.
>
> I have some experience like system administrator mainly with Web
>
> So, let me introduce myself.
>
> My name is Abhishek Sharma, I'm 21 years old and live at Ajmer, Rajasthan.
> My first contact with Linux was approximately 3 years ago and
> since that year I have been working only with Linux (sometimes with
> Linux X Windows integrations).
>
> my area of contributing: -
> 1. Fedora Quality Assurance
> 2. Creating RPM packages
>
>
> So, thanks a lot for some people who accepted me at Fedora Project.
>
> At my signature, I'm sending my contacts to feel free if anyone wants to
> contact me.
>
> Bye
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
>


-- 
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED 
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Re: New member introduction

[Sumantro Mukherjee]

Hey Uditanshu,

On Wed, Apr 17, 2019 at 8:12 PM Uditanshu Kumar 
wrote:

> hi team,
> This is Uditanshu Kumar , I'm 19 years old . Currently pursuing Btech in
> Information Technology from Haldia Institute of technology . Presently
> working in the field of Linux and high end technologies like Machine
> learning , Big Data , Cloud computing and Devops tools like Ansible. I want
> to work with QA team and packaging team
>
> Thanks and regards,
> Uditanshu Kumar
>
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
>

Welcome to Fedora QA, It will be great if you apply for qa FAS group. If
you have, I have sponsored you by now. If you haven’t then please apply and
send me an email with your FAS ID and I will approve.

You can start off by testing updates in [http://bodhi.fedoraproject.org/]
for Fedora 28, Fedora 29, and Fedora 30. Update testing is where a tester
tests a package and gives out a +1 Karma for PASS and -1 Karma for FAIL.
You can go to bodhi.fedoraproject.org where you can sort the packages with
Fedora Releases and tags viz “pending” & “testing”. You can read much about
update testing here [1]. You can also, use fedora-easy-karma for giving out
feedbacks.
You can start with Release Validation testing. In Release Validation all
you need to do is to check the nightly/TC/RC against certain criteria. For
example, let’s take the latest compose (Fedora 30 Branched 20190415.n.2),
you can run test cases which are mentioned [2] and submit your results in
the test matrix.

Note that each of the test cases[3] will have “How to test” section which
will have the steps (to be executed sequentially) and if the results match
with the expected results you can mark it as pass by editing the wiki page
{{result|PASS|}}. Always make sure to check for “Associated
release criterion” which can be found on the top of test case page, if your
test case fails you can mark it fail by editing the wiki page
{{result|FAIL|}} and file a bug at RHBZ [4] under Fedora.

You can always find the ‘current’ validation pages using these addresses:

https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test
https://fedoraproject.org/wiki/Test_Results:Current_Base_Test
https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test
https://fedoraproject.org/wiki/Test_Results:Current_Server_Test
https://fedoraproject.org/wiki/Test_Results:Current_Cloud_Test

For Automation, you can start looking at Open QA[
https://fedoraproject.org/wiki/OpenQA] its maintained by Adamw.

[1] https://fedoraproject.org/wiki/QA:Updates_Testing
[2]
https://fedoraproject.org/wiki/Test_Results:Fedora_30_Branched_20190415.n.2_Summary?rd=Test_Results:Current_Summary
[3] https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc
[4] https://bugzilla.redhat.com/

Feel free to ping us on IRC if you need any help #fedora-qa@freenode.

We have test days coming happening now which is a nice place to start,
please stay tuned to the @test list and help us testing!
The current test day can be found on
https://fedoraproject.org/wiki/Test_Day:Current?redirect=yes
Test days schedule can be found on the fedocal
https://apps.fedoraproject.org/calendar/list/QA/?subject=Test+Day

-- 
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED 
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Re: New member introduction

[Sumantro Mukherjee]

Hey Pallavi,

Welcome to Fedora QA, It will be great if you apply for qa FAS group. If
you have, I have sponsored you by now. If you haven’t then please apply and
send me an email with your FAS ID and I will approve.

You can start off by testing updates in [http://bodhi.fedoraproject.org/]
for Fedora 28, Fedora 29, and Fedora 30. Update testing is where a tester
tests a package and gives out a +1 Karma for PASS and -1 Karma for FAIL.
You can go to bodhi.fedoraproject.org where you can sort the packages with
Fedora Releases and tags viz “pending” & “testing”. You can read much about
update testing here [1]. You can also, use fedora-easy-karma for giving out
feedbacks.
You can start with Release Validation testing. In Release Validation all
you need to do is to check the nightly/TC/RC against certain criteria. For
example, let’s take the latest compose (Fedora 30 Branched 20190415.n.2),
you can run test cases which are mentioned [2] and submit your results in
the test matrix.

Note that each of the test cases[3] will have “How to test” section which
will have the steps (to be executed sequentially) and if the results match
with the expected results you can mark it as pass by editing the wiki page
{{result|PASS|}}. Always make sure to check for “Associated
release criterion” which can be found on the top of test case page, if your
test case fails you can mark it fail by editing the wiki page
{{result|FAIL|}} and file a bug at RHBZ [4] under Fedora.

You can always find the ‘current’ validation pages using these addresses:

https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test
https://fedoraproject.org/wiki/Test_Results:Current_Base_Test
https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test
https://fedoraproject.org/wiki/Test_Results:Current_Server_Test
https://fedoraproject.org/wiki/Test_Results:Current_Cloud_Test

For Automation, you can start looking at Open QA[
https://fedoraproject.org/wiki/OpenQA] its maintained by Adamw.

[1] https://fedoraproject.org/wiki/QA:Updates_Testing
[2]
https://fedoraproject.org/wiki/Test_Results:Fedora_30_Branched_20190415.n.2_Summary?rd=Test_Results:Current_Summary
[3] https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc
[4] https://bugzilla.redhat.com/

Feel free to ping us on IRC if you need any help #fedora-qa@freenode.

We have test days coming happening now which is a nice place to start,
please stay tuned to the @test list and help us testing!
The current test day can be found on
https://fedoraproject.org/wiki/Test_Day:Current?redirect=yes
Test days schedule can be found on the fedocal
https://apps.fedoraproject.org/calendar/list/QA/?subject=Test+Day

On Thu, Apr 18, 2019 at 8:45 AM Pallavi Kumari 
wrote:

> hi team,
> This is Pallavi Kumari . I am 19 years old . Working on Linux from last 1
> year . Want to work with fedora QA and packaging team.
>
> Thanks and regards,
> Pallavi Kumari
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
>


-- 
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED 
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org

Re: New Member introduction request.

[Sumantro Mukherjee]

Welcome to Fedora QA, It will be great if you apply for qa FAS group. If
you have, I have sponsored you by now. If you haven’t then please apply and
send me an email with your FAS ID and I will approve.

You can start off by testing updates in [http://bodhi.fedoraproject.org/]
for Fedora 28, Fedora 29, and Fedora 30. Update testing is where a tester
tests a package and gives out a +1 Karma for PASS and -1 Karma for FAIL.
You can go to bodhi.fedoraproject.org where you can sort the packages with
Fedora Releases and tags viz “pending” & “testing”. You can read much about
update testing here [1]. You can also, use fedora-easy-karma for giving out
feedbacks.
You can start with Release Validation testing. In Release Validation all
you need to do is to check the nightly/TC/RC against certain criteria. For
example, let’s take the latest compose (Fedora 30 Branched 20190415.n.2),
you can run test cases which are mentioned [2] and submit your results in
the test matrix.

Note that each of the test cases[3] will have “How to test” section which
will have the steps (to be executed sequentially) and if the results match
with the expected results you can mark it as pass by editing the wiki page
{{result|pass|}}. Always make sure to check for “Associated
release criterion” which can be found on the top of test case page, if your
test case fails you can mark it fail by editing the wiki page
{{result|fail|}} and file a bug at RHBZ [4] under Fedora.

You can always find the ‘current’ validation pages using these addresses:

https://fedoraproject.org/wiki/Test_Results:Current_Installation_Test
https://fedoraproject.org/wiki/Test_Results:Current_Base_Test
https://fedoraproject.org/wiki/Test_Results:Current_Desktop_Test
https://fedoraproject.org/wiki/Test_Results:Current_Server_Test
https://fedoraproject.org/wiki/Test_Results:Current_Cloud_Test

For Automation, you can start looking at Open QA[
https://fedoraproject.org/wiki/OpenQA] its maintained by Adamw.

[1] https://fedoraproject.org/wiki/QA:Updates_Testing
[2]
https://fedoraproject.org/wiki/Test_Results:Fedora_30_Branched_20190415.n.2_Summary?rd=Test_Results:Current_Summary
[3] https://fedoraproject.org/wiki/QA:Testcase_USB_stick_Live_luc
[4] https://bugzilla.redhat.com/

Feel free to ping us on IRC if you need any help #fedora-qa@freenode.

We have test days coming happening now which is a nice place to start,
please stay tuned to the @test list and help us testing!
The current test day can be found on
https://fedoraproject.org/wiki/Test_Day:Current?redirect=yes
Test days schedule can be found on the fedocal
https://apps.fedoraproject.org/calendar/list/QA/?subject=Test+Day

On Thu, Apr 18, 2019 at 10:41 AM Akash Das  wrote:

> Hello,
> This is Akash Das here, I would like to request you for letting me work in
> your QnA as well as packaging, it'll be a good honour to help the team and
> to learn a lot of more things from our community.
> I'm having a bit knowledge of Linux administrator and have been working on
> Linux since past 1year.
>
> Thanking you.
>
> Your's faithfully,
> Akash Das
>
>
> ___
> test mailing list -- test@lists.fedoraproject.org
> To unsubscribe send an email to test-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
>


-- 
//sumantro
Fedora QE
TRIED AND PERSONALLY TESTED, ERGO TRUSTED 
___
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org