devel-announce October 2014

devel-announce@lists.fedoraproject.org

5 participants
12 discussions

Fedora 21 Beta status is Go, release on November 4, 2014
by Jaroslav Reznik 30 Oct '14

30 Oct '14

At the Fedora 21 Beta Go/No-Go Meeting #3 that just occurred, it was agreed to Go with the Fedora 21 Beta by Fedora QA, Release Engineering and Development. Fedora 21 Beta will be publicly available on Tuesday, November 04, 2014. Meeting details can be seen here: Minutes: http://bit.ly/1tmPWzw Log: http://bit.ly/1DCMsvi Thanks everyone! Jaroslav

1 0

Announcing the Fedora 21 Alpha for the POWER architecture!
by Peter Robinson 29 Oct '14

29 Oct '14

I'm pleased to announce the arrival of the Fedora Alpha release for the POWER ppc64 and ppc64le architectures. Feel free to take it for a drive [1]. This release of Fedora for POWER focuses on the Fedora Base and Server product with support for existing big endian hardware plarforms as well as new Power 8 platforms on both big and little endian. The Server product on POWER supports all the features of the product that the mainline primary platforms support. We also support the Base product set and the vast majority of the 15K+ source package set of the entire Fedora release are now built. === Fedora 21 Base === Each of the products will build on the "base" set of packages for Fedora. For instance, each product will use the same packages for the kernel, RPM, yum, systemd, Anaconda, and so forth. The Base Working Group develops the standard platform for all Fedora products, which includes the installer, compose tools, and basic platform for the other products. Base is not a full product intended for use on its own, but to be kept as a small, stable platform for other products to build on. === Fedora 21 Server === The Fedora Server product is a common base platform that is meant to run featured application stacks, which are produced, tested, and distributed by the Server Working Group. Want to use Fedora as a Web server, file server, database server, or platform for an Infrastructure-as-a-Service? Fedora 21 Server is for you. == Issues and Details == This is an Alpha release. As such, we expect that you may encounter bugs or missing features. To report issues encountered during testing, contact the Fedora ppc team via the arm mailing list or in #fedora-ppc on freenode. The release can be found on the secondary architecture mirrors [2][3]. [1] https://fedoraproject.org/wiki/Architectures/AArch64/F21_Alpha/Installation [2] https://mirrors.fedoraproject.org/publiclist/Fedora/21-Alpha/ppc64/ [3] https://mirrors.fedoraproject.org/publiclist/Fedora/21-Alpha/ppc64le/

1 0

Fedora 21 Beta to slip by one week
by Jaroslav Reznik 24 Oct '14

24 Oct '14

Today at Go/No-Go meeting it was decided to slip Fedora 21 Beta release by one week due to unresolved blocker bugs [1]. More details in meeting minutes [2]. As a result, ALL MAJOR MILESTONES, and their dependent tasks, will be pushed out by one week [3]. The next Go/No-Go meeting is on Thursday, Oct 30, 17:00 UTC at #fedora-meeting-2 channel on FreeNode. Jaroslav [1] http://qa.fedoraproject.org/blockerbugs/milestone/21/beta/buglist [2] http://meetbot.fedoraproject.org/fedora-meeting-2/2014-10-24/f21_beta_gono-… [3] https://fedoraproject.org/wiki/Releases/21/Schedule

1 0

Fedora 21 Beta to slip
by Jaroslav Reznik 23 Oct '14

23 Oct '14

Today at Go/No-Go meeting it was decided to slip Fedora 21 Beta release as we did not have release candidate (RC) available in time. However we will try one day slip. The next Go/No-Go meeting is on Friday, Oct 24, the same time at #fedora-meeting-2 channel. Any help with release validation once RC is out is very appreciated! [1] http://qa.fedoraproject.org/blockerbugs/milestone/21/beta/buglist [2] http://meetbot.fedoraproject.org/fedora-meeting-2/2014-10-23/f21_beta_gono-… [3] https://fedoraproject.org/wiki/Releases/21/Schedule

1 0

Announcing the Fedora 21 Alpha for the Aarch64 architecture!
by Peter Robinson 22 Oct '14

22 Oct '14

I'm pleased to announce the arrival of the Fedora Alpha release for the ARM aarch64 architecture. Feel free to take it for a drive [1]. The initial release of Fedora for aarch64 focuses on the Fedora Base and Server product with support for hardware plarforms such as the APM Storm platform including devices like the Mustang board, AMD Seattle and ARM Versatile Express64 including the Foundation emulator and the Juno hardware platform. The aarch64 Server product supports all the features of the product that the mainline primary platforms support. We also support the Base product set and the vast majority of the 15K+ source package set of the entire Fedora release are now built. === Fedora 21 Base === Each of the products will build on the "base" set of packages for Fedora. For instance, each product will use the same packages for the kernel, RPM, yum, systemd, Anaconda, and so forth. The Base Working Group develops the standard platform for all Fedora products, which includes the installer, compose tools, and basic platform for the other products. Base is not a full product intended for use on its own, but to be kept as a small, stable platform for other products to build on. === Fedora 21 Server === The Fedora Server product is a common base platform that is meant to run featured application stacks, which are produced, tested, and distributed by the Server Working Group. Want to use Fedora as a Web server, file server, database server, or platform for an Infrastructure-as-a-Service? Fedora 21 Server is for you. == Issues and Details == This is an Alpha release. As such, we expect that you may encounter bugs or missing features. To report issues encountered during testing, contact the Fedora ARM team via the arm mailing list or in #fedora-arm on freenode. The release can be found on the secondary architecture mirrors [2]. [1] https://fedoraproject.org/wiki/Architectures/AArch64/F21_Alpha/Installation [2] https://mirrors.fedoraproject.org/mirrorlist?repo=fedora-server-21&arch=aar…

1 0

Fedora 21 Beta Go/No-Go Meeting, Thursday, October 23 @ 17:00 UTC
by Jaroslav Reznik 21 Oct '14

21 Oct '14

Join us on irc.freenode.net in #fedora-meeting-2 for this important meeting, wherein we shall determine the readiness of the Fedora 21 Beta. Thursday, October 23, 2014 17:00 UTC (1 PM EDT, 10 AM PDT, 19:00 CEST) "Before each public release Development, QA and Release Engineering meet to determine if the release criteria are met for a particular release. This meeting is called the Go/No-Go Meeting." "Verifying that the Release criteria are met is the responsibility of the QA Team." Release Candidate (RC) availability and good QA coverage are prerequisites for the Go/No-Go decision but meeting itself is held in any case. For more details about this meeting see: https://fedoraproject.org/wiki/Go_No_Go_Meeting In the meantime, keep an eye on the Fedora 21 Beta Blocker list: http://qa.fedoraproject.org/blockerbugs/milestone/21/beta/buglist Fedora 21 Beta blocker bug status report by adamw https://lists.fedoraproject.org/pipermail/devel/2014-October/203591.html We have very tight schedule this time to make Fedora 21 release this year, please help us with blocker bugs, testing and other tasks needed for successful release. So far, many reviews says F21 Alpha is the best Fedora ever! Jaroslav

1 0

Fedora 21 Beta Release Readiness Meeting :: Thursday, Oct. 23, 19:00 UTC
by Jaroslav Reznik 21 Oct '14

21 Oct '14

Fedora 21 Beta Release Readiness Meeting. date: 2014-10-23 place: irc.freenode.net in #fedora-meeting-2 time: 19:00 UTC (3 PM EDT, 12 PM PDT, 21:00 CEST) This Thursday, October 23, we will meet to make sure we are coordinated and ready for the Beta release of Fedora 21 on Tuesday, October 28, 2014. Please note that this meeting will occur on October 23 even if the release is delayed at the Go/No-Go meeting on the same day two hours earlier. You may received this message several times, but I was asked to open this meeting to the teams and I'll also hope this will raise awareness and more team representatives will come to this meeting. This meeting works best when we have representatives from all of the teams. Also, there's a Fedora badge for active participants! Jaroslav

1 0

Nominations for Engineering representative to the Fedora Council
by Dennis Gilmore 16 Oct '14

16 Oct '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi All, As you are likely aware, we are undergoing some changes in governance[1] for Fedora On behalf of FESCo I am writing to you all to ask for nominations. preferably people will self nominate, however we will accept nominations from others as longa s the nominated person agrees to be considered. In order to submit your nomination please notify FESCo via the currently open ticket[2] in trac requesting a FESCo appointee. you have until Tuesday October 21 @ 23:59 UTC to get nominations in. FESCo will choose a representive in next weeks meeting. Thank you Dennis [1] https://fedoraproject.org/wiki/Council [2] https://fedorahosted.org/fesco/ticket/1355 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBAgAGBQJUP1+IAAoJEH7ltONmPFDRfb4P/1xvmQpyqMuECBQEBoQi3d5l 6FGJCV2ckbfxzFhqzuunbOWM7/k/e6J3F4zmJvL3QoefV9svUs/uNtCVM5ZNfgEZ W87Qf8K9Zar0dXyhhu2X6NFvKNnKMVCZZ4k7izfAAD/Kh8esutx9wujzaPXJYBBe uLscNfUG8fUAfBCmMjqlAyYgongOaOg7c27M3rRG7Q28Dmo5O17UdCvX1Kz4cdzX Pusblj3JSiIBnNtrug+d8OzQIrP8M0tITy/yxFi0m40lMOEH/zve85gg8nrF/yf5 F61IKeh8B39pp5iZkZdOSQ3AVR63sUbpNW3YM1KKQ8YMZ3RSA+sfK95v0cIgfGKM mikySeEJgALh1tDl6J5ROoIItZRzhsO5ZdleMYTEMDMBg0jVZGeGVht1E4iVn05l VDGh41oAXOfvyo5SDW8nYzogeawW/bLIV1ie8q4GTZRObOCckQjJ6bePEVMkByFt 0T7y4HBmHd7RodPpEn8luDLE0neju+vFwvkQQGaA9F+uHwdq4m4+Anfw/IEflYj1 GcngtzDAMKAqokJf66btqbRrXzjqKnfPGpQOc0LcVQ2BX6q9t3AHCOdff0m1h433 c/5JGSmBHhcOA/X5dZn+lF6HEM7IvA2ITZEdDsRLSNzvNUASUqEVlBpvXrKY4Kx0 pjUQFWFe9yoqCz3DNvqZ =CNA+ -----END PGP SIGNATURE-----

1 0

Fedora 21 Beta Change Freeze
by Dennis Gilmore 14 Oct '14

14 Oct '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, as the Fedora 21 schedule[1] states the Beta change freeze is upon us. As of now all Beta freeze only accepted exceptions[2] will be allowed in. we are at the beta stage of release, so the Beta_to_Pre_Release[3] stage of the updates policy applies. Regards Dennis [1] http://fedorapeople.org/groups/schedule/f-21/f-21-devel-tasks.html [2] http://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process [3] http://fedoraproject.org/wiki/Updates_Policy#Beta_to_Pre_Release -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBAgAGBQJUPLDQAAoJEH7ltONmPFDR7bwQANK1a6zC3DPtVKU64+PlvWh1 ZEMY5oawUTLhBeo+AmzHvIhrhtlIIezVDWRiAkxgetczPgcjvgVmImUncQ5sL7N7 AXRdW6RURPovSRk7t1i+KV08T+1SR8V9iogqbUsfywqVL+AUjks6tzcLwfd2+RwI vMufCwgEYFTdic2ynzVJc5MlCoICFA23k6PRhJgb42WANgFLs/Gr73Mh0GVnRPZm 7QDpJpHqhVn41brUaZf15D5S8bg9t+NG1FxuTkQJiJcVKeL0qXMFSSF8Jl1Xwl7X +JebLmEQ8nlsSzfUOBHqVv2j0sAMYfDBuDxc7BYSPl2IqodVFdB9fTxPxsU1loBG cx0vJ672WtHnA5eQK66+X9aBmtLNN1/9jjsjmAcS3kPW4wXD6CTZqxvu8Uyn5RN6 vbt530HdsLM1865owTdD2w1g/sHZIOafzrqtreEL4s/DjPEB69epBLBcvisekzua AB3g1aO9bwxOqYSQAYUOvJ864f2oSkFrTkIlur2AlCKQQCFw+NTN49cnwpssMFdh Ibt8PzsnWH9TELuR9UsTnuKYPoddHhemJQbXZrcKYPSZx/Wl5RS/V8aXTS5FbwQx /hkCK9msELIlVPsET3Z26BxN6gzT0VvOqLyB1Ke50cMy5XaoC10SXP51bsChumYq pFSSm+dc1O10iEBYz3eC =zU5Z -----END PGP SIGNATURE-----

1 0

Engineering Representiatve for the new Fedora Council
by Matthew Miller 10 Oct '14

10 Oct '14

Hey all Fedora distribution developers, engineers, builders, and infrastructure people! As I hope you've seen by now, we're creating a new Fedora Council as a top-level project leadership and governance body. (If you missed it, see inode0's general announcement to the community <https://lists.fedoraproject.org/pipermail/announce/2014-October/003234.html> and the new charter at <https://fedoraproject.org/wiki/Council>.) One seat of the new Council is selected by FESCo to represent all of the groups that logically fall under that committee — not in the ruleship sense, but in the sense that it makes a natural place for coordination and representation of the technical concerns. We have a FESCo ticket <https://fedorahosted.org/fesco/ticket/1355> for selecting this representative, but the conversation is larger than just the members of FESCo, so I'm bringing it here. Help FESCo decide who can best represent you, your groups, and your work in the project. -- Matthew Miller <mattdm(a)fedoraproject.org> Fedora Project Leader

1 0

[pkgdb] Call for beta-testers for group maintainership
by Pierre-Yves Chibon 06 Oct '14

06 Oct '14

Dear all, A long desired and awaited feature for pkgdb2 is the possibility to have FAS groups maintain packages. The idea is the following: - You have a FAS group - People are members of this group - This group can be given commit or even be made point of contact of packages on pkgdb - If the group has commit, members of the group will have commits (so you don't need anymore to ask for ACL in pkgdb, you can just ask to be added in the group in FAS). After some preliminary testing with positive results, I would like to call for more testers. Ideally, if we could get a few groups of not too many people (ie: not the perl-sig group) that would be good. The idea is to make sure that the process works well and that people in the group are getting the correct notifications about actions happening on the packages (git commit, bodhi update, koji builds...) which is of course harder to do on a group that involves many people and packages. I put together some instructions on the requirements and steps: http://pkgdb2.readthedocs.org/en/latest/groups.html Thanks for your attention, Best regards, Pierre On behalf of the Fedora Infrastructure team

1 0

Fedora 21 Accepted Changes 100% Complete Deadline in two weeks
by Jaroslav Reznik 01 Oct '14

01 Oct '14

Greetings! This time I'm sending "Accepted Changes 100% Complete" reminder a bit earlier than usually as we still have quite a lot of work to do on Changes and it's going to help other teams to participate in Changes process earlier (aka Docs team etc.). 2014-10-14 Accepted Changes 100% Complete Expected bug state is ON_QA - Change has to be code completed and can be tested in the Beta release (optionally by Fedora QA). Please make sure to update state of yours Change(s) bug(s) on time. In case of any problems, let me know, we will try to find solution. http://fedoraproject.org/wiki/Releases/21/Schedule Expect more nagging in Change bug(s) between now and Beta Freeze ;-). Thanks Jaroslav -- Your friendly Change Wrangler

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

devel-announce October 2014