From Fedora Project Wiki
Page title matches
- 32 bytes (2 words) - 18:39, 12 July 2017
- #REDIRECT [[Community Platform Engineering]]44 bytes (4 words) - 16:58, 15 February 2018
- 32 bytes (2 words) - 18:39, 12 July 2017
- Category for Release Engineering SOPs23 members (1 subcategory, 0 files) - 18:18, 14 February 2009
- {{admon/important|This page is deprecated| All Fedora Release Engineering Documentation has moved [https://docs.pagure.org/releng/ here] with source This page documents the Standard Operating Procedures for Fedora Release Engineering.33 members (0 subcategories, 0 files) - 17:48, 3 November 2015
- Community Platform Engineering is a team within Red Hat that has the following mission: The Community Platform Engineering Team are responsible for the infrastructure and services that support artif3 KB (439 words) - 14:43, 14 July 2021
- = Fedora Engineering Services = ...t volunteers are generally unable or unwilling to do. That's where Fedora Engineering Services(FES) fits in. Team members have promised a certain number of hour3 KB (426 words) - 15:51, 13 August 2010
- 30 bytes (5 words) - 19:15, 10 August 2010
- #REDIRECT [[Community Platform Engineering/Flock]]50 bytes (5 words) - 16:58, 15 February 2018
- 4 KB (710 words) - 14:28, 4 February 2019
- 32 bytes (4 words) - 18:55, 10 June 2009
- 34 bytes (4 words) - 18:55, 10 June 2009
- #REDIRECT [[Community Platform Engineering/FY13 Plan]]54 bytes (6 words) - 16:58, 15 February 2018
- 30 bytes (4 words) - 18:57, 10 June 2009
- #REDIRECT [[Community Platform Engineering/FY14 Plan]]54 bytes (6 words) - 16:58, 15 February 2018
- ...good communication skills. Below is the process for selecting the Council Engineering representative. ...ESCo members. It is recommended that they should be members of one of the engineering focused groups in FAS.3 KB (486 words) - 12:09, 29 September 2018
- 395 bytes (59 words) - 17:07, 4 January 2019
- #REDIRECT [[Community Platform Engineering/FY15 Plan]]54 bytes (6 words) - 16:58, 15 February 2018
- Potential [[Fedora Engineering Services]] members must meet each of the below descriptions:1 KB (192 words) - 15:34, 13 August 2010
- #REDIRECT [[Community Platform Engineering/FY16 Plan]]54 bytes (6 words) - 16:58, 15 February 2018
- 594 bytes (98 words) - 20:16, 20 February 2010
- 36 bytes (4 words) - 18:55, 10 June 2009
- #REDIRECT [[Community Platform Engineering/FY17 Plan]]54 bytes (6 words) - 16:58, 15 February 2018
- 2 KB (274 words) - 16:58, 15 February 2018
- 35 bytes (4 words) - 18:55, 10 June 2009
- #REDIRECT [[Community Platform Engineering/FY18 Plan]]54 bytes (6 words) - 16:58, 15 February 2018
- This is a summary of important goals for the [[Fedora Engineering|Fedora Engineering team]] for Red Hat Fiscal Year 2018 (March 2017 - February 2018). ...r of a '''lead person''' shows accountability for whatever work the Fedora Engineering team has committed to. It may not be the same as a person leading an overa5 KB (709 words) - 14:50, 31 August 2018
- 4 KB (707 words) - 12:06, 29 September 2018
- This is a summary of important goals for the [[Fedora Engineering|Fedora Engineering team]] for Red Hat Fiscal Year 2015 (March 2014 - February 2015).6 KB (946 words) - 16:58, 15 February 2018
- This document is Fedora Engineering's "working plan" for FY13. In FY13, Red Hat hopes to hire people to fill the following full-time Fedora Engineering positions:10 KB (1,632 words) - 16:58, 15 February 2018
- 38 bytes (5 words) - 18:54, 10 June 2009
- This document is Fedora Engineering's "working plan" for FY14. Fedora Engineering is constantly working on any number of initiatives, but for FY14, our focus12 KB (1,909 words) - 16:58, 15 February 2018
- This is a summary of important goals for the [[Fedora Engineering|Fedora Engineering team]] for Red Hat Fiscal Year 2016 (March 2015 - February 2016). ...r of a '''lead person''' shows accountability for whatever work the Fedora Engineering team has committed to. It may not be the same as a person leading an overa8 KB (1,118 words) - 16:58, 15 February 2018
- This is a summary of important goals for the [[Fedora Engineering|Fedora Engineering team]] for Red Hat Fiscal Year 2017 (March 2016 - February 2017). ...r of a '''lead person''' shows accountability for whatever work the Fedora Engineering team has committed to. It may not be the same as a person leading an overa7 KB (1,006 words) - 16:58, 15 February 2018
- FESCo is the Fedora Engineering Steering Committee. It is a fully community elected body and represents th4 KB (583 words) - 12:05, 29 September 2018
- 951 bytes (139 words) - 12:13, 29 September 2018
- =Previous Fedora Engineering Steering Committee Members=10 KB (1,294 words) - 12:12, 29 September 2018
- #REDIRECT [[Archive:Release Engineering Release Tickets]]57 bytes (6 words) - 12:54, 8 August 2014
Page text matches
- The [https://docs.pagure.org/releng/ Fedora Release Engineering documentation] is maintained in [https://pagure.io/releng/blob/main/f/docs [[Category: Release Engineering]]205 bytes (28 words) - 04:35, 10 October 2021
- == Fedora Engineering Steering Committee (FESCo) == L'amministrazione tecnica di Fedora è organizzata dal Fedora Engineering Steering Committee (FESCo).580 bytes (62 words) - 12:14, 9 March 2009
- ...ting Procedure] in the new [https://docs.pagure.org/releng/ Fedora Release Engineering Documentation] for the current documentation}} [[Category:Release Engineering SOPs]]317 bytes (43 words) - 21:53, 10 August 2018
- .../docs.pagure.org/releng/sop_pushing_updates.html here]| All Fedora Release Engineering Documentation has moved [https://docs.pagure.org/releng/ here] with source [[Category:Release Engineering SOPs]]336 bytes (49 words) - 16:29, 4 April 2016
- ...re.org/releng/sop_adding_side_build_targets.html here]| All Fedora Release Engineering Documentation has moved [https://docs.pagure.org/releng/ here] with source [[Category:Release Engineering SOPs]]346 bytes (51 words) - 20:25, 31 March 2016
- ...cs.pagure.org/releng/sop_sigul_client_setup.html here]| All Fedora Release Engineering Documentation has moved [https://docs.pagure.org/releng/ here] with source [[Category:Release Engineering SOPs]]337 bytes (50 words) - 20:23, 31 March 2016
- {{admon/important|This page is deprecated| All Fedora Release Engineering Documentation has moved [https://docs.pagure.org/releng/sop_mass_branching. [[Category:Release Engineering SOPs]]339 bytes (48 words) - 10:22, 14 June 2016
- '''The College of Engineering, University of the Philippines Campus, Diliman, Quezon City, Philippines''' * To create awareness about Open Source, Linux, and Fedora Project among UP Engineering students.560 bytes (65 words) - 09:10, 17 November 2009
- = Menu Category Proposal for Engineering software = | Engineering || Engineering software, e.g. CAD programs ||2 KB (187 words) - 13:47, 24 December 2008
- * B.Sc Computer Engineering * Ms Computer Control Engineering336 bytes (38 words) - 13:03, 5 March 2009
- I am a second year undergraduate student at Delhi College of Engineering, Delhi, India. I am currently pursuing my Bachelor of Engineering in Information Technology at the institute.884 bytes (160 words) - 16:33, 24 May 2008
- I work with Oracle India pvt ltd. for the Application platform engineering group. I have been involved in porting Oracle Applications developed in bas I hold my Bachelors in Engineering from Madras University and currently pursuing MS from Birla Institute of Te689 bytes (103 words) - 16:34, 24 May 2008
- Category for Release Engineering SOPs23 members (1 subcategory, 0 files) - 18:18, 14 February 2009
- #REDIRECT [[Community Platform Engineering]]44 bytes (4 words) - 14:43, 30 January 2019
- #REDIRECT [[Community Platform Engineering]]44 bytes (4 words) - 16:58, 15 February 2018
- #REDIRECT [[:Category:Release Engineering SOPs]]48 bytes (5 words) - 18:52, 10 June 2009
- Members of the [[FES|Fedora Engineering Service]].28 members (0 subcategories, 0 files) - 10:33, 17 February 2010
- #REDIRECT [[Fedora Engineering Steering Committee]]51 bytes (5 words) - 21:45, 1 February 2010
- #REDIRECT [[Community Platform Engineering/Flock]]50 bytes (5 words) - 16:58, 15 February 2018
- # Re-confirm that release day is on track with release engineering. # Confirm execution of ''rawhide rebase'' with Red Hat Engineering Operations967 bytes (140 words) - 19:26, 2 June 2009
- #REDIRECT [[Community Platform Engineering/FY13 Plan]]54 bytes (6 words) - 16:58, 15 February 2018
- #REDIRECT [[Community Platform Engineering/FY14 Plan]]54 bytes (6 words) - 16:58, 15 February 2018
- #REDIRECT [[Community Platform Engineering/FY15 Plan]]54 bytes (6 words) - 16:58, 15 February 2018
- #REDIRECT [[Community Platform Engineering/FY16 Plan]]54 bytes (6 words) - 16:58, 15 February 2018
- #REDIRECT [[Community Platform Engineering/FY17 Plan]]54 bytes (6 words) - 16:58, 15 February 2018
- #REDIRECT [[Community Platform Engineering/FY18 Plan]]54 bytes (6 words) - 16:58, 15 February 2018
- #REDIRECT [[Previous Fedora Engineering Steering Committee Members]]68 bytes (7 words) - 21:00, 13 September 2017
- {{admon/important|This page is deprecated| All Fedora Release Engineering Documentation has moved [https://docs.pagure.org/releng/ here] with source Release Engineering is often asked by maintainers to remove branches in dist-git by maintainers857 bytes (122 words) - 17:56, 3 November 2015
- # Confirm ''End-of-life'' date with Fedora Release Engineering ...licable date for running of ''End of Life'' auto-close ticket with Red Hat Engineering Operations833 bytes (119 words) - 02:01, 24 February 2009
- {{admon/important|This page is deprecated| All Fedora Release Engineering Documentation has moved [https://docs.pagure.org/releng/ here] with source Release Engineering is responsible for producing the final .ISO and torrent files for custom sp906 bytes (134 words) - 17:52, 3 November 2015
- [[Category: Release Engineering]]204 bytes (20 words) - 12:29, 21 March 2019
- ...ty of South Florida for a double major in Nuclear Engineering and Computer Engineering. I have a stable job at DataComm Networks Inc. A Network Security Company l917 bytes (139 words) - 21:20, 10 March 2009
- # Draft ticket for Red Hat Engineering Operations requesting the rebase of rawhide bugs # Draft ticket for Red Hat Engineering Operations requesting ''End of Life'' warning added to applicable bugs426 bytes (56 words) - 21:31, 17 September 2016
- ''2th National Meeting of Engineering Students'' ...for Engineering Students. There will be on talk about Fedora and tools for Engineering, like Fedora Electronic Labs.2 KB (287 words) - 03:44, 5 June 2011
- ...a member of Red Hat's localisation team in June 2006, more responsible for Engineering Operations now, however, hope to combine both areas. More via http://ttrink195 bytes (29 words) - 16:26, 24 May 2008
- ''STIX scientific and engineering fonts'' ...preparation of a comprehensive set of fonts that serve the scientific and engineering community in the process from manuscript creation through final publication1 KB (162 words) - 20:34, 15 July 2008
- {{admon/important|This page is deprecated| All Fedora Release Engineering Documentation has moved [https://docs.pagure.org/releng/ here] with source This page documents the Standard Operating Procedures for Fedora Release Engineering.33 members (0 subcategories, 0 files) - 17:48, 3 November 2015
- === Tool Improvement / Engineering ===1 KB (153 words) - 19:33, 3 June 2008
- ...must be guaranteed for a 'rotating' spin as well. For example, if Release Engineering decided to make the dvd sized Developer Spin a permanent spin, then we must ...ire to use this option by the deadline, then the option lapses and Release Engineering no longer has to reserve the space in its decision making process.2 KB (346 words) - 16:37, 24 May 2008
- {{admon/important|This page is deprecated| All Fedora Release Engineering Documentation has moved [https://docs.pagure.org/releng/ here] with source 2. Update the release engineering ticket with the url:1 KB (155 words) - 17:52, 3 November 2015
- == Release Engineering == ...ora Release Engineering group. See the [[ReleaseEngineering|Fedora Release Engineering page]] for more information.2 KB (269 words) - 19:55, 6 January 2022
- = Fedora Events: August Penguin 2011 - Shenkar College of Art Design and Engineering, Ramat Gan, Israel = * Shenkar College of Art Design and Engineering, Ramat Gan, Israel648 bytes (102 words) - 10:50, 27 June 2011
- #REDIRECT [[Archive:Release Engineering Release Tickets]]57 bytes (6 words) - 12:54, 8 August 2014
- === Release Engineering ===2 KB (179 words) - 09:33, 8 March 2009
- Hi all, I am an Engineer from Bharati Vidyapeeth College of Engineering Pune (India) ...to pursue a higher Masters degree in US with a specialisation in Software Engineering.1 KB (220 words) - 11:58, 9 March 2009
- ...taka, India. I am pursuing Bachelor of Engineering in Computer Science and Engineering. My first linux experience came on Mandrake distro around 2 years back (as1 KB (154 words) - 19:05, 10 July 2008
- ...p://en.wikipedia.org/wiki/Durgapur Durgapur] studying Computer Science and Engineering. I am from a small town named [http://en.wikipedia.org/wiki/Malbazar Malbaz2 KB (263 words) - 07:01, 18 November 2008
- [[Category:Release Engineering SOPs]]236 bytes (37 words) - 17:36, 19 July 2016
- Hi , this is Jaydeep Rathava. I am graduate in mechanical engineering from M.S.University, Gujarat.284 bytes (37 words) - 16:31, 24 May 2008
- # File a ticket with Red Hat Engineering Operations requesting the rebase of rawhide bugs on release day # File a ticket with Red Hat Engineering Operations requesting that qualifying bugs receiving an ''End of Life'' war1 KB (154 words) - 23:41, 11 November 2008
- Chemical Engineering and Technology (coal chemical industry) 08 th Class 1 Chemical Engineering and Technology939 bytes (105 words) - 14:11, 23 August 2010
- ...ttps://www.redhat.com/archives/fedora-docs-list/2006-July/msg00151.html re-engineering the default browser homepage in Fedora Core] to something differnent than324 bytes (47 words) - 16:38, 24 May 2008
- = Fedora Engineering Services = ...t volunteers are generally unable or unwilling to do. That's where Fedora Engineering Services(FES) fits in. Team members have promised a certain number of hour3 KB (426 words) - 15:51, 13 August 2010
- |Student of Computing Engineering at University of Pernambuco [http://www.upe.br UPE]452 bytes (63 words) - 16:36, 24 May 2008
- {{admon/important|This page is deprecated| All Fedora Release Engineering Documentation has moved [https://docs.pagure.org/releng/ here] with source [[Category:Release Engineering SOPs]]892 bytes (128 words) - 17:53, 3 November 2015
- === Fedora Engineering Steering Committee Meeting 2008-04-10 === === Fedora Release Engineering Meeting 2008-04-07 ===2 KB (160 words) - 21:35, 20 September 2016
- ...aproject.org/updates Bodhi]. They do not require an exception from Release Engineering, but they should use the established Bodhi peer-review, karma system. ...on request by filing a [https://fedorahosted.org/rel-eng/newticket Release Engineering Ticket], or by running <code>make tag-request</code> in your package module3 KB (463 words) - 22:27, 25 September 2014
- ...on request by filing a [https://fedorahosted.org/rel-eng/newticket Release Engineering Ticket], or by running <code>make tag-request</code> in your package module The [[ReleaseEngineering| Release Engineering team]] will evaluate your request and provide feedback.2 KB (342 words) - 20:44, 15 January 2010
- This table shows reserved funds for Fedora Engineering team members for [http://flocktofedora.org Flock 2015] airfares. Please try See also the [[Fedora Engineering/Flock | lodging + planning page]].1 KB (149 words) - 21:20, 14 July 2015
- I am Ballout Merouen ,student in Moroccan School For Science Engineering;Linux and especially fedora get me a feeling to be free and use it free ,213 bytes (37 words) - 16:29, 24 May 2008
- ...timelines associated with the established Fedora Feature process. Release Engineering is tasked with reviewing each proposed spin for release, and documenting an While Release Engineering has a broad mandate on developing their own technical release criteria, the6 KB (909 words) - 16:36, 24 May 2008
- ...ersity. Then I have done my post-graduation (M.Tech) in Computer Science & Engineering from Nirma University, India. I have done my dissertation at Physical Resea1 KB (169 words) - 11:53, 12 June 2009
- ...ized in association with the Maharastra Institute of Technology College of Engineering (MIT COE), one of the premier engineering colleges in Pune, at their Campus.2 KB (346 words) - 11:11, 4 February 2015
- ...part of the Fedora Ambassador team. I'm also involved with Fedora release engineering, and general troubleshooting that needs doing. On top of all of that, I'm l1 KB (184 words) - 18:27, 8 May 2009
- Kalyani Govt. Engineering College( KGEC) has quite a large base of students interested in linux . Thi * Location: Kalyani Govt. Engineering College, India2 KB (206 words) - 06:33, 24 February 2009
- {{admon/important|This page is deprecated| All Fedora Release Engineering Documentation has moved [https://docs.pagure.org/releng/ here] with source ...view, or for existing packages that need a new branch (e.g. EPEL). Release Engineering has written a script to automate this process.1 KB (179 words) - 17:50, 3 November 2015
- Technical fonts include coverage of technical unicode blocks (math, engineering and other non-text blocks).22 members (0 subcategories, 0 files) - 19:28, 27 June 2008
- I've got some experience with the development, documentation end quality engineering for open source projects. I am keen to help here and there with fedora docs535 bytes (93 words) - 16:33, 24 May 2008
- {{admon/important|This page is deprecated| All Fedora Release Engineering Documentation has moved [https://docs.pagure.org/releng/ here] with source [[Category:Release Engineering SOPs]]1 KB (166 words) - 17:50, 3 November 2015
- My name is Kharrat Zied; I'm a Computer Engineering and working in tunis.410 bytes (52 words) - 10:54, 12 October 2008
- Community Platform Engineering is a team within Red Hat that has the following mission: The Community Platform Engineering Team are responsible for the infrastructure and services that support artif3 KB (439 words) - 14:43, 14 July 2021
- {{admon/important|This page is deprecated| All Fedora Release Engineering Documentation has moved [https://docs.pagure.org/releng/ here] with source ...summary of all the freezes, dates, and exception handling, or the release engineering [https://fedorapeople.org/groups/schedule/f-{{FedoraVersionNumber|next}}/f-2 KB (239 words) - 17:51, 3 November 2015
- == Release Engineering == # Fedora Engineering Manager -- Tom "Spot" Callaway2 KB (293 words) - 17:06, 16 June 2009
- === Release Engineering ===2 KB (258 words) - 18:54, 8 November 2011
- I am a Computer Engineering Students loves Open Source and here for Supporting fedora424 bytes (51 words) - 13:27, 26 April 2009
- ...p an architecture without the overhead of the primary architecture release engineering process # The Fedora infrastructure and release engineering teams must indicate an ability and willingness to support the port.3 KB (501 words) - 18:57, 23 April 2012
- ....speedpartner.de/ SpeedPartner GmbH] in consulting/development as well as engineering. He is active in the Open Source/Linux/PHP-field for several years, also be667 bytes (102 words) - 16:33, 24 May 2008
- ...iversity of California, Davis in the department of Electrical and Computer Engineering. He is a member of the [http://www.ece.ucdavis.edu/vcl VLSI Computing Labor578 bytes (89 words) - 12:11, 6 March 2009
- * From Jaipur, India currently pursuing Computer Engineering from Pune University. ...meddling with a lot of frameworks like flask , django etc. Worked on data engineering for 5 to 6 months.1 KB (179 words) - 21:54, 6 March 2018
- I am Kulbir Saini, a Computer Science Engineering graduate from IIIT Hyderabad, India. Read more about me at [http://saini.co572 bytes (71 words) - 07:37, 17 March 2011
- ...o all Fedora package maintainers.And then the image is composed by Release Engineering and presented to Fedora Language Testing Group (FLTG). During this QA activ ...ing. This task is called as "Compose of Live Image" and appears in Release Engineering Schedule, which can be found in [[Schedule#Detailed_Schedules| Detailed Sch2 KB (247 words) - 06:22, 6 October 2016
- ...ring Graduate, working at BESU Shibpur (Proposed IIEST), one of the oldest engineering college in India. * '''Office Address''': Computer Centre, 2nd floor(A.K.Sil Hall), Bengal Engineering and Science Univ. Shibpur, Post Office: B. Garden, Howrah, PIN - 711103, We2 KB (273 words) - 04:27, 1 September 2009
- ...good communication skills. Below is the process for selecting the Council Engineering representative. ...ESCo members. It is recommended that they should be members of one of the engineering focused groups in FAS.3 KB (486 words) - 12:09, 29 September 2018
- ...requirements, and now gives groups such as QA, Spins, Design, and Release Engineering the responsibility to set their own criteria for each new image produced. === Produced by Release Engineering ===3 KB (527 words) - 11:25, 12 June 2011
- === Release Engineering ===3 KB (320 words) - 18:58, 8 November 2011
- * Add packages (Package Maintainer requests this. Release Engineering approves the request.) == Release Engineering & Security Team ==3 KB (437 words) - 22:00, 8 January 2010
- {{admon/important|This page is deprecated| All Fedora Release Engineering Documentation has moved [https://docs.pagure.org/releng/ here] with source For each of Fedora's public releases (Alpha, Beta, and Final) it is Release Engineering's responsibility to sign all packages with Fedora's GPG key. This provides2 KB (402 words) - 17:56, 3 November 2015
- = Drupal Workshop at College of Engineering, Pune [CoEP]= College of Engineering, Pune1 KB (179 words) - 16:56, 20 July 2010
- * [[Development/SteeringCommittee/Nominations|FESCo (Engineering)]] (four seats) == [[Development/SteeringCommittee/Nominations|Fedora Engineering Steering Committee (FESCo)]] ==3 KB (415 words) - 17:10, 14 January 2014
- Profession: Student in Electrical and Electronic Engineering1 KB (145 words) - 16:32, 24 May 2008
- {{admon/important|This page is deprecated| All Fedora Release Engineering Documentation has moved [https://docs.pagure.org/releng/ here] with source [[Category:Release Engineering SOPs]]1 KB (199 words) - 09:58, 28 March 2016
- * Organizing a seminar for engineering students. * Engineering students(from all branches mainly CSE, IT and ICT ).1 KB (186 words) - 17:03, 23 August 2009
- ...Germany for System Z. In the last 2 years he also took up the lead of the engineering team in Germany. Recently he stepped up to lead an effort to improve power2 KB (274 words) - 08:50, 30 May 2009
- [[Development/SteeringCommittee/Meetings| Fedora Engineering Steering Committee (FESCo)]] [[ReleaseEngineering| Release Engineering]]2 KB (201 words) - 16:33, 24 May 2008
- ...e Fedora-run CVS and infrastructure. We talked with members of the Release Engineering Team and the plan is to move all elvis-hosted development to <code>cvs.fedo * Any support needed by release engineering3 KB (379 words) - 22:13, 8 January 2010
- || [https://fedorahosted.org/rel-eng/newticket File tag request with Release Engineering] ...[https://fedorahosted.org/rel-eng/newticket File tag request with Release Engineering]3 KB (435 words) - 22:30, 2 August 2010
- || [https://fedorahosted.org/rel-eng/newticket File tag request with Release Engineering] ...[https://fedorahosted.org/rel-eng/newticket File tag request with Release Engineering]3 KB (435 words) - 14:10, 10 April 2011
- {{admon/important|This page is deprecated| All Fedora Release Engineering Documentation has moved [https://docs.pagure.org/releng/ here] with source [[Category:Release Engineering SOPs]]1 KB (182 words) - 17:57, 3 November 2015
- ...now. If there's an applicable [[:Category:Release_Engineering_SOPs|Release Engineering SOP]], familiarize yourself with it. If there's not and you think there sho2 KB (284 words) - 13:40, 7 September 2014
- PhDstudent at the Computer Engineering & Informatics Department (CEID) of Patras.459 bytes (50 words) - 14:52, 18 September 2016
- # Docs, Engineering, Design, Ambassadors regular linking # Make use of new Fedora Engineering Services Queue2 KB (246 words) - 17:32, 13 March 2010
- == Fedora Engineering Steering Committee (FESCo) ==448 bytes (53 words) - 08:25, 22 February 2018
- === Fedora Engineering Steering Committee (FESCo) === Fedora technical management is organized by the Fedora Engineering Steering Committee (FESCo).4 KB (456 words) - 16:27, 23 December 2009
- |style="background-color: lightblue;" |'''Group:''' Quality Engineering564 bytes (72 words) - 16:33, 24 May 2008
- I am Gaurang Aggarwal , a Engineering student ( Infomation Technology ) in senior year .450 bytes (76 words) - 17:23, 22 July 2011
- * [http://abes.ac.in/ ABES Engineering College] * ABES Engineering College,Campus-1, Ghaziabad, Uttar Pradesh 2010092 KB (332 words) - 05:48, 18 September 2016
- {{admon/caution|Out of Date Material | Release Engineering sets meeting agendas based on tickets in the Trac instance. This page is n = Fedora Release Engineering Meeting Agenda =3 KB (396 words) - 23:44, 14 August 2009
- ...use or not have been updated for many years and refer to obsolete release engineering or development processes or packages. Some may still be potentially useful10 members (0 subcategories, 0 files) - 09:47, 6 August 2014
- universities and Engineering schools. had mostly students from the Engineering schools asking a lot of3 KB (451 words) - 11:32, 12 December 2010
- ...raproject.org/pipermail/rel-eng/2008-August/001627.html here]. The release engineering team can be reached in #fedora-devel (irc.freenode.org) or emailed [mailto: # {{check}} Release engineering obtains the security team's approval to the plan shown below.3 KB (425 words) - 21:08, 20 October 2008
- Hi , this is Jaydeep Rathava. I am graduate in mechanical engineering from M.S.University, Gujarat. now a days i am working as a design engineer871 bytes (127 words) - 19:17, 31 May 2008
- We will be organizing a Fedora 26 Release Party Event at Amrita School of Engineering, Coimbatore. The aim of this event is to introduce Fedora and Linux in gene Amrita School of Engineering, Coimbatore.1 KB (178 words) - 09:13, 7 September 2017
- In the creation and delivery of a new spin, Fedora Release Engineering will provide several services ...ure the quality of the spin. Prior to submission to the Board and Release Engineering, it is expected that the submitter has done at least the following minimal4 KB (735 words) - 16:31, 24 May 2008
- = Fedora Release Engineering Meeting :: Monday 2008-12-08 = * Growing the release engineering team14 KB (1,859 words) - 19:11, 8 December 2008
- ...hat we did here as a model for future similar types of endeavors. Release Engineering thought that it was quite useful.529 bytes (85 words) - 16:31, 24 May 2008
- I'm HE Qichen, student at School of Computer Engineering and443 bytes (60 words) - 17:22, 17 April 2009
- # Ticket filed with Red Hat Engineering Operations -- '''DONE''' # Ticket filed with Red Hat Engineering Operations --'''DONE'''4 KB (639 words) - 22:29, 12 September 2008
- [http://www.kgec.edu.in/ Kalyani Govt. Engineering College(KGEC)] has a large base of students interested in linux . This work ...ikimapia.org/#lat=22.9908518&lon=88.4487337&z=18&l=0&m=a&v=2 Kalyani Govt. Engineering College], India1 KB (225 words) - 21:45, 17 September 2016
- Professionaly, i run a web engineering company VinayRas Infotech in Nagpur, Maharashtra, India, specializes in PHP631 bytes (92 words) - 02:39, 13 January 2009
- * [[Development/SteeringCommittee/Nominations|FESCo (Engineering)]] (4 seats) ...collected questions for nominees to [[Development/SteeringCommittee|FESCo (Engineering)]], [[Council|Fedora Council]] and [[Mindshare|Mindshare]] teams, top 3 que7 KB (955 words) - 13:15, 22 October 2019
- === '''Release Engineering Automation''' === ...identify and breakdown the work needed to automate most of Fedora Release engineering.2 KB (364 words) - 08:54, 7 February 2019
- ...refer to trigger building our own spins, and then hand one over to Release Engineering, that can be released. Let's talk about this at our meeting.3 KB (404 words) - 17:55, 10 June 2008
- * [[Development/SteeringCommittee/Nominations|FESCo (Engineering)]] (five seats) == [[FAmSCo_election_2012_F18_nominations|Fedora Engineering Steering Committee (FESCo)]] ==4 KB (620 words) - 20:10, 23 May 2012
- Make Fedora and CentOS a pleasant platform for Data Engineering. Data Engineering ecosystem heavily consist of software that would not go well with Fedora Pa3 KB (394 words) - 09:59, 8 February 2021
- We will be organizing a Fedora 27 Release Party Event at Amrita School of Engineering, Coimbatore. The aim of this event is to introduce Fedora and Linux in gene Amrita School of Engineering, Coimbatore.1 KB (191 words) - 04:32, 20 February 2018
- # Draft EOL closing ticket with Red Hat Engineering Operations (Bugzilla Management). Ticket includes:871 bytes (117 words) - 23:44, 27 January 2015
- {{admon/important|This page is deprecated| All Fedora Release Engineering Documentation has moved [https://docs.pagure.org/releng/ here] with source Every release prior to the [[Schedule|Feature Freeze/Branching]] Release Engineering retires [https://docs.fedoraproject.org/en-US/package-maintainers/Package_O3 KB (483 words) - 20:28, 2 October 2021
- ...y College of Engineering[A],Visakhapatnam;pursuing III year MS in Software Engineering;most of the time I gig with my responsibilities in our campus and work on m2 KB (249 words) - 14:52, 18 September 2016
- 7th Electronic Engineering Conference ...The forum is for students and professionals who are related to Electronic Engineering. There are talks about education, industry and research.2 KB (329 words) - 03:47, 5 June 2011
- ...lease Engineering uses for various tasks related to the day to day release engineering tasks for Fedora.2 KB (311 words) - 09:24, 29 October 2008
- Key: '''FE''' = Fedora Engineering; '''CA''' = Community Architecture. Hotel costs are expressed as $600 for 3 ...s really doesn't raise the budget for FUDCon to >$25K. Because the Fedora Engineering team is using standard travel budget in Q2 and Q3, along with a set-aside i2 KB (287 words) - 21:28, 14 December 2010
- ...stitute of Technology College of Engineering (MIT COE), one of the premier engineering colleges in Pune, at their Campus from the 26th to the 28th of June, 2015. ...6th to 28th of June 2015 at Maharashtra Institute of Technology College of Engineering (MIT COE), Pune.3 KB (405 words) - 13:21, 29 April 2015
- systems engineering, to networking. I'm pretty familiar with the writing and markup tools, but1 KB (184 words) - 16:27, 24 May 2008
- * [https://pagure.io/releng/issue/6815 Release Engineering ticket #6815] on reviewing the abovementioned change proposal * <del>[https://pagure.io/releng/issue/6791 Release Engineering ticket #6791] on having the new bootstrap tag created is currently blocking2 KB (236 words) - 11:54, 19 June 2017
- I am part of the Red Hat Internationalization Engineering team.574 bytes (81 words) - 13:07, 15 January 2014
- {{admon/important|This page is deprecated| All Fedora Release Engineering Documentation has moved [https://docs.pagure.org/releng/ here] with source ...requests a TC or RC they do so by filing or reopening a ticket in Release Engineering trac. There is one trac ticket per milestone.3 KB (459 words) - 17:51, 3 November 2015
- * [[User:pknirsch | Phil Knirsch]]: Representing Red Hat BaseOS Engineering * [[User:Ausil | Dennis Gilmore]]: Representing Release Engineering3 KB (419 words) - 09:35, 26 February 2014
- Release Engineer for Identity Management Engineering at Red Hat, Inc.1,023 bytes (138 words) - 16:35, 24 May 2008
- ...7, and has been a Red Hat employee since 2001. Currently, he is the Fedora Engineering Manager. In addition to that, he is the chair of the Fedora Packaging Commi1,009 bytes (172 words) - 20:04, 9 April 2009
- * Fedora Release Engineering967 bytes (135 words) - 16:29, 24 May 2008
- ...ll be held at the Auditorium of Science, located at National University of Engineering (UNI). ...cience among the schools of Chemical, Physics, Maths, different careers of Engineering.2 KB (216 words) - 23:47, 18 March 2017
- ...rom this effort that we now have a number of students, mostly from various engineering colleges across India, contributing to different sub-projects of Fedora.2 KB (277 words) - 08:14, 18 September 2016
- Before each public release Development, QA, and Release Engineering meet to determine if the release criteria are met for a particular release. # At the start of the meeting representatives from Development, Release Engineering, and Quality Assurance should be clearly identified3 KB (446 words) - 20:38, 12 October 2017
- = Fedora Release Engineering Meeting :: Monday 2008-10-06 = * (spins for Fedora 9) - Fedora Release Engineering - Trac - https://fedorahosted.org/rel-eng/ticket/2420 KB (2,749 words) - 23:10, 7 October 2008
- == Fedora Engineering Steering Committee == The [[FESCo|Fedora Engineering Steering Committee]] (FESCo) is a community-elected body empowered by the C4 KB (530 words) - 20:27, 12 January 2023
- {{admon/important|This page is deprecated| All Fedora Release Engineering Documentation has moved [https://docs.pagure.org/releng/ here] with source People volunteer (or get assigned) to doing Fedora release engineering from time to time. This SOP seeks to describe the process to add a new rel5 KB (752 words) - 17:49, 3 November 2015
- "JohnPoelstra posted details of the Release Engineering Meeting[1] . ThorstenLeemhuis was against one of the decisions made in the "JohnPoelstra posted details of the Release Engineering Meeting[1] . These included a note that a mass rebuild of all packages arou2 KB (293 words) - 10:24, 14 April 2009
- I am currently pursuing my B.Tech degree in Computer Science and Engineering (5th Sem)1 KB (150 words) - 12:50, 9 March 2009
- ...lone program, but capable of easy integration into pungi and other release engineering tools. Image contents should be configurable at runtime and not require a * Release engineering would have the flexibility to tweak install image contents without dependin2 KB (343 words) - 08:22, 8 August 2018
- # Send an email to the release-engineering team with the ticket number mentioned in step 2, with a request to prepare # Follow up with the release engineering team on the ticket for ISO.5 KB (772 words) - 01:40, 4 July 2014
- # Ticket filed with Red Hat Engineering Operations: '''Done by poelcat on 2008-11-11''' # Mass change operation run: '''Done by RHT Engineering Operations/poelcat 2008-11-26'''8 KB (1,179 words) - 18:51, 10 December 2008
- ...The goal is to provide single point of information for Fedora QE, release engineering and other teams. Mostly to avoid late surprises during Fedora release compo * release engineering knows what's going to be produced for upcoming release ahead of time (we ad2 KB (276 words) - 13:04, 16 September 2019
- Schedule for Tuesday's Release Engineering Meeting ({{#time:Y-m-d|tuesday}}) ...he agenda post. Rename the subject to: Summary/Minutes for today's release engineering meeting ({{#time:Y-m-d|tuesday}})3 KB (512 words) - 15:05, 19 April 2022
- ...ibute Fedora LiveCDs to all newcomer students of both computer science and engineering courses. Thus, the number of CDs we are requesting is bigger than the numb ...f medias/CDs requested''': 150 (50 computer science students, 100 computer engineering students)2 KB (324 words) - 04:19, 8 December 2012
- ...with Engineering representative to plan, coordinate, and schedule release engineering and infrastructure changes in advance of the F22 and F23 alpha releases.2 KB (272 words) - 14:07, 7 February 2024
- ...for all of the mass changes automatically performed in bugzilla by Red Hat Engineering Operations at the request of the bug triage team. # Ticket filed with Red Hat Engineering Operations -- '''CHANGEME'''5 KB (739 words) - 15:18, 5 March 2010
- ...s a brief note about myself. I have studied electronics and communications engineering at Ain Shams University, Cairo, Egypt. I have worked as an analog hardware1 KB (204 words) - 16:25, 24 May 2008
- * '''Bio:''' Chitlesh Goorah holds a Master degree in Micro-Nano Electronics engineering. He explores different opensource methodologies which can benefit the EDA c826 bytes (114 words) - 18:53, 8 June 2009
- {{admon/important|This page is deprecated| All Fedora Release Engineering Documentation has moved [https://docs.pagure.org/releng/ here] with source [[Category:Release Engineering SOPs]]2 KB (321 words) - 17:57, 3 November 2015
- * [[Development/SteeringCommittee/Nominations|FESCo (Engineering)]] (4 seats) == [[Development/SteeringCommittee/Nominations|FESCo (Engineering)]] ==5 KB (772 words) - 21:12, 29 April 2020
- *Where:Mansoura University, Faculty of Engineering, Rashad-Albadrawy's hall, Mansoura, Egypt697 bytes (90 words) - 07:51, 19 August 2010
- ...ard became the first RHCE. Richard has a Masters Degree in Digital Systems Engineering from RMIT and has worked for over twenty years as systems engineer, softwar833 bytes (121 words) - 05:17, 26 February 2009
- ''' Academic Education :''' BSc In Electrical And Electronics Engineering From [http://www.buet.ac.bd/eee BUET]1 KB (195 words) - 16:03, 30 May 2008
- ...ents in Red Hat Enterprise Linux and Fedora and he was involved in several engineering projects. Recently he stepped up to lead an effort to improve boot time red726 bytes (120 words) - 09:42, 26 May 2009
- {{admon/important|This page is deprecated| All Fedora Release Engineering Documentation has moved [https://docs.pagure.org/releng/ here] with source Release Engineering is responsible for producing the final .ISO files for custom spins that are3 KB (448 words) - 17:54, 3 November 2015
- * Take a proactive role in Fedora release engineering907 bytes (141 words) - 15:11, 16 March 2010
- Create a space/section for fedora-i18n engineering efforts at https://docs.fedoraproject.org/en-US/docs/803 bytes (102 words) - 10:56, 17 February 2023
- During the past months, Fedora is investing heavily in re-engineering its translation workflow. By supporting more than 5 different version contr ...lization on Advanced Information Systems. He loves anything to do with web engineering, open source community development, design, and digital rights, and in his3 KB (427 words) - 16:34, 24 May 2008
- # release engineering process ...and procedures as outlined above. Will also assist with changes to release engineering.5 KB (689 words) - 13:16, 20 October 2014
- I am a student of computer engineering, and I am new user to Fedora since 2013. I'm starting to work with the comm552 bytes (80 words) - 21:13, 2 May 2017
- schedules, Release Engineering will be ready to start scripted rebuilds Release Engineering has created two scripts. One is to initiate the builds, and the other is t4 KB (587 words) - 03:57, 5 June 2014
- [[Category:Release Engineering]]899 bytes (129 words) - 06:00, 2 September 2013
- ...ng with Django for the development of the college website of NetajiSubhash engineering College.https://github.com/debjeet-sarkar/dooby</li> <li>Conducted workshop on python and php in Netaji Subhash engineering5 KB (770 words) - 18:56, 20 March 2014
- ...The goal is to provide single point of information for Fedora QE, release engineering and other teams. Mostly to avoid late surprises during Fedora release compo * release engineering knows what's going to be produced for upcoming release ahead of time (we ad2 KB (335 words) - 12:24, 27 April 2020
- ...The goal is to provide single point of information for Fedora QE, release engineering and other teams. Mostly to avoid late surprises during Fedora release compo * release engineering knows what's going to be produced for upcoming release ahead of time (we ad2 KB (335 words) - 12:39, 29 April 2021
- ...The goal is to provide single point of information for Fedora QE, release engineering and other teams. Mostly to avoid late surprises during Fedora release compo * release engineering knows what's going to be produced for upcoming release ahead of time (we ad2 KB (335 words) - 18:16, 7 December 2020
- ...The goal is to provide single point of information for Fedora QE, release engineering and other teams. Mostly to avoid late surprises during Fedora release compo * release engineering knows what's going to be produced for upcoming release ahead of time (we ad2 KB (335 words) - 16:38, 25 August 2020
- ...ng with Django for the development of the college website of NetajiSubhash engineering College.https://github.com/debjeet-sarkar/dooby</li> <li>Conducted workshop on python and php in Netaji Subhash engineering5 KB (774 words) - 19:06, 20 March 2014
- RHCE. Richard has a Masters Degree in Digital Systems Engineering from RMIT and has worked for over twenty years as systems engineer, softwar972 bytes (158 words) - 05:15, 26 February 2009
- ...or opportunities to become familiar with technical vocabulary and merge my engineering background with the language.699 bytes (107 words) - 17:06, 4 July 2011
- *Profession or Student status: Junior majoring in Communication Engineering676 bytes (106 words) - 15:36, 15 January 2014
- * See [http://www.esprit.tn/ ESPRIT, Higher Private School of Engineering and Technology Tunisia ]800 bytes (102 words) - 22:44, 10 December 2014
- engineering in a competent2 KB (224 words) - 05:02, 4 July 2010
- schedules, Release Engineering will be ready to start scripted rebuilds Release Engineering has created two scripts. One is to initiate the builds, and the other is t4 KB (632 words) - 16:50, 13 February 2013
- * [[ReleaseEngineering|Fedora Release Engineering Team]] (Eventually)1 KB (101 words) - 21:04, 19 September 2016
- schedules, Release Engineering will be ready to start scripted rebuilds Release Engineering has created two scripts. One is to initiate the builds, and the other is t3 KB (502 words) - 22:09, 23 August 2022
- * Fri Jan 13 2012 Fedora Release Engineering <rel-eng@lists.fedoraproject.org> - 2.7-31 KB (113 words) - 10:34, 21 February 2012
- schedules, Release Engineering will be ready to start scripted rebuilds Release Engineering has created two scripts. One is to initiate the builds, and the other is t3 KB (501 words) - 16:12, 19 January 2022
- ...different topics where it was partly unclear if the Board or FESCo (Fedora Engineering Steering Committee) was responsible or the first to act to make a decision. FESCo as Fedora Engineering Steering Committee integrates what was up to Fedora 7 known as "Core Cabal"4 KB (689 words) - 16:28, 24 May 2008
- schedules, Release Engineering will be ready to start scripted rebuilds Release Engineering has created two scripts. One is to initiate the builds, and the other is t4 KB (654 words) - 12:19, 18 July 2012
- * '''Future Plans:''' Get Fedora Engineering services busy making Fedora better. Get updates process working better. Hel ...and stability. Stressing the balance of new features with QA and release engineering to make Fedora releases both innovative and high quality.5 KB (746 words) - 15:30, 26 October 2010
- * open area at Faculty of Engineering, Mansoura University , Mansoura Governorate ...ora 21 release party we named it I love fedora. the meet was in faculty of Engineering mansoura University. we decided to make it in the open garden of the facult3 KB (417 words) - 13:04, 17 February 2015
- * FESCo approved a proposal to give Release Engineering final say in acking spins for a release based on the Feature criteria. If2 KB (204 words) - 19:47, 30 July 2008
- schedules, Release Engineering will be ready to start scripted rebuilds Release Engineering has created two scripts. One is to initiate the builds, and the other is t3 KB (518 words) - 15:04, 12 January 2023
- | '''Company:''' ( [http://www.eng.it Engineering S.p.A.] )1 KB (197 words) - 14:42, 18 September 2016
- schedules, Release Engineering will be ready to start scripted rebuilds Release Engineering has created two scripts. One is to initiate the builds, and the other is t3 KB (516 words) - 21:22, 15 January 2024
- schedules, Release Engineering will be ready to start scripted rebuilds Release Engineering has created two scripts. One is to initiate the builds, and the other is t4 KB (658 words) - 05:49, 3 August 2013
- It was used to capture the experience that the Infrastructure / Release Engineering team has with using Taiga to track work for OSBS deployment and 2 week Atom961 bytes (150 words) - 23:22, 16 July 2020
- schedules, Release Engineering will be ready to start scripted rebuilds Release Engineering has created two scripts. One is to initiate the builds, and the other is t4 KB (678 words) - 20:57, 27 January 2012
- schedules, Release Engineering will be ready to start scripted rebuilds Release Engineering has created two scripts. One is to initiate the builds, and the other is t3 KB (517 words) - 17:59, 25 January 2021
- l'ENSEEIHT (an engineering school), Toulouse1 KB (129 words) - 18:51, 13 October 2014
- schedules, Release Engineering will be ready to start scripted rebuilds Release Engineering has created two scripts. One is to initiate the builds, and the other is t3 KB (517 words) - 08:42, 27 July 2020
- * Uriel Rodolfo Olascoaga Gómez, President of the Computer Systems Engineering student chapter. ...arrez Santiago, President of the Information and Communications Technology Engineering student chapter.2 KB (312 words) - 01:52, 13 May 2018
- schedules, Release Engineering will be ready to start scripted rebuilds Release Engineering has given maintainers the ability to7 KB (1,106 words) - 23:17, 6 March 2009
- schedules, Release Engineering will be ready to start scripted rebuilds Release Engineering has created two scripts. One is to initiate the builds, and the other is t3 KB (521 words) - 15:56, 30 July 2021
- * See [http://www.esprit.ens.tn/ ESPRIT, Higher Private School of Engineering and Technology Tunisia ]910 bytes (118 words) - 13:06, 30 January 2014
- {{admon/important|This page is deprecated| All Fedora Release Engineering Documentation has moved [https://docs.pagure.org/releng/ here] with source [[Category:Release Engineering SOPs]]2 KB (330 words) - 17:57, 3 November 2015
- This document concerns requirements from Fedora infrastructure, release engineering, and other community teams for a CI implementation in Fedora. It exists to ...and to provide a reasonable on-ramp for community, since one of the Fedora Engineering team’s goals is to promote growth of the “farm team” of new community5 KB (726 words) - 15:07, 18 July 2017
- {{admon/note|Open source, all the way up the stack|Join the software engineering and developer community to explore what's new in open source languages, too745 bytes (107 words) - 17:35, 4 April 2017
- === Fedora Engineering Steering Committee (FESCo) === ...isches Management wird vom [[Fedora_Engineering_Steering_Committee |Fedora Engineering Steering Committee (FESCo)]] organisiert.0 members (0 subcategories, 0 files) - 21:13, 17 September 2016
- = Fedora Release Engineering Meeting :: Monday 2007-10-15 = ...="2">{{Template:Tip}} f13 changed the topic of #fedora-meeting to: Release Engineering Meeting</td><td>13:00</td></tr>6 KB (1,049 words) - 16:14, 14 February 2014
- ...ng my programming skills I know C, C++, Python and PHP. I've done Computer Engineering, and a lot of kernel programming for my projects. Till this date I haven't957 bytes (169 words) - 16:21, 13 July 2009
- schedules, Release Engineering will be ready to start scripted rebuilds Release Engineering has created two scripts. One is to initiate the builds, and the other is t4 KB (561 words) - 10:29, 3 February 2016
- schedules, Release Engineering will be ready to start scripted rebuilds Release Engineering has created two scripts. One is to initiate the builds, and the other is t4 KB (568 words) - 21:23, 16 June 2015
- ...ages to work on completing, and FESCo needs to get tangible buy-in from RH engineering mgnt.2 KB (204 words) - 16:30, 24 May 2008
- schedules, Release Engineering will be ready to start scripted rebuilds Release Engineering has created two scripts. One is to initiate the builds, and the other is t5 KB (731 words) - 12:33, 9 February 2011
- ...http://www.hardware.no/artikler/tom_spot_callaway_english/66947 The Fedora Engineering Manager, Tom "spot" Callaway] || English3 KB (317 words) - 23:24, 20 March 2009
- [[Category:Engineering]]1 KB (170 words) - 22:36, 19 August 2013
- ...community. It is also a opportunity for students of Department of Computer Engineering to learn about Fedora and open-source principles and how can they get invol * Middle East Technical University / Computer Engineering Department / BMB-3 Classroom2 KB (356 words) - 14:16, 17 March 2019
- * '''Building:''' [http://ecst.calstatela.edu College of Engineering, Computer Science, and Technology]2 KB (241 words) - 08:24, 3 March 2009
- ...presentation from the previous Environments & Stacks and Base WGs, Release Engineering, Infrastructure, Quality Assurance, and the Security Team. ...PEL founder, Former Board Member, Contributor and owner of all the release engineering tools. I want to make how we build and ship Fedora more flexible and dynami4 KB (682 words) - 12:51, 23 January 2019
- schedules, Release Engineering will be ready to start scripted rebuilds Release Engineering has created two scripts. One is to initiate the builds, and the other is t4 KB (577 words) - 10:11, 31 January 2019
- In conjunction with Release Engineering and the Fedora Infrastructure teams, the total size of all spins cannot exc In conjunction with Release Engineering and the Quality Assurance teams, the total number of spins cannot exceed Y.3 KB (532 words) - 13:56, 30 June 2013
- schedules, Release Engineering will be ready to start scripted rebuilds Release Engineering has created two scripts. One is to initiate the builds, and the other is t4 KB (585 words) - 03:11, 16 May 2017
- schedules, Release Engineering will be ready to start scripted rebuilds Release Engineering has created two scripts. One is to initiate the builds, and the other is t4 KB (579 words) - 00:06, 10 February 2017
- At The Thrid Space Coffee House, Qihang Center Of Activity, Harbin Engineering University.1 KB (115 words) - 02:44, 18 August 2014
- schedules, Release Engineering will be ready to start scripted rebuilds Release Engineering has created two scripts. One is to initiate the builds, and the other is t4 KB (579 words) - 15:38, 27 January 2020
- #**# FESCo / Release Engineering #** FESCo / Release Engineering needs presence at the Spin SIG meetings in order to chime in on concerns in4 KB (569 words) - 22:14, 14 January 2009
- schedules, Release Engineering will be ready to start scripted rebuilds Release Engineering has created two scripts. One is to initiate the builds, and the other is t4 KB (567 words) - 20:05, 24 July 2023
- schedules, Release Engineering will be ready to start scripted rebuilds Release Engineering has given maintainers the ability to6 KB (940 words) - 20:42, 20 July 2009
- ...in All India ranking after the IIT's and few NIT's. It is one of the best Engineering colleges in Maharashtra and best in Pune. COEP has a large auditorium with College of Engineering, Pune5 KB (775 words) - 20:50, 19 September 2016
- schedules, Release Engineering will be ready to start scripted rebuilds Release Engineering has created two scripts. One is to initiate the builds, and the other is t4 KB (616 words) - 13:40, 28 April 2018
- * Fri Jan 13 2012 Fedora Release Engineering <rel-eng@lists.fedoraproject.org> - 3.04-3b1 KB (137 words) - 11:17, 21 February 2012
- schedules, Release Engineering will be ready to start scripted rebuilds Release Engineering has created two scripts. One is to initiate the builds, and the other is t4 KB (617 words) - 03:14, 16 May 2017
- schedules, Release Engineering will be ready to start scripted rebuilds Release Engineering has created two scripts. One is to initiate the builds, and the other is t4 KB (611 words) - 13:22, 3 August 2017
- * Location : [http://www.pdn.ac.lk/eng Faculty of Engineering, University of Peradeniya, Kandy], Sri Lanka.841 bytes (112 words) - 02:23, 28 April 2012
- ...ensource.com/index.php/Textbook_Release_0.8 Practical Open Source Software Engineering], a textbook-in-progress for CS professors * Engineering Manager, [http://www.redhat.com/red_hat_network/ Red Hat Network], 2001-2005 KB (655 words) - 14:29, 13 April 2017
- ...uildroot. It takes waiting. Furthermore, before sending request to release engineering one must get some assurance that all builds will succeed and and will not c4 KB (633 words) - 17:20, 7 February 2013
- Potential [[Fedora Engineering Services]] members must meet each of the below descriptions:1 KB (192 words) - 15:34, 13 August 2010
- {{admon/important|This page is deprecated| All Fedora Release Engineering Documentation has moved [https://docs.pagure.org/releng/ here] with source [[Category:Release Engineering SOPs]]3 KB (450 words) - 17:50, 3 November 2015
- === Fedora Engineering Steering Committee (FESCo) === ...gement is organized by the [[Fedora_Engineering_Steering_Committee |Fedora Engineering Steering Committee (FESCo)]].0 members (0 subcategories, 0 files) - 12:47, 7 April 2021
- schedules, Release Engineering will be ready to start scripted rebuilds Release Engineering has created two scripts. One is to initiate the builds, and the other is t4 KB (602 words) - 13:41, 24 July 2019
- * FESCo approved the schedule for F9 proposed by the Release Engineering Team. http://poelstra.fedorapeople.org/schedules/f9/f9-milestones.html1 KB (187 words) - 16:28, 24 May 2008
- [[Category:Release Engineering]]2 KB (342 words) - 19:10, 14 February 2009
- I am an honors graduate inElectrical engineering . I m an open source enthusiast and developer. Currently I am a researcher1,003 bytes (143 words) - 09:40, 18 October 2013
- schedules, Release Engineering will be ready to start scripted rebuilds Release Engineering has created two scripts. One is to initiate the builds, and the other is t4 KB (612 words) - 13:14, 26 July 2017
- Olivier Cleynen is originally from the aerospace engineering and product design sector. He is passionate about advocacy for free softwar2 KB (234 words) - 16:28, 24 May 2008
- schedules, Release Engineering will be ready to start scripted rebuilds Release Engineering has created two scripts. One is to initiate the builds, and the other is t4 KB (650 words) - 10:15, 14 July 2018
- * Bachelor + 1 Mechanical Engineering1 KB (154 words) - 13:20, 12 May 2009
- This is a summary of important goals for the [[Fedora Engineering|Fedora Engineering team]] for Red Hat Fiscal Year 2018 (March 2017 - February 2018). ...r of a '''lead person''' shows accountability for whatever work the Fedora Engineering team has committed to. It may not be the same as a person leading an overa5 KB (709 words) - 14:50, 31 August 2018
- | Red Hat VP of Linux Engineering Tim Burke describes how Red Hat's contributions to Fedora form a mutually b1 KB (197 words) - 20:03, 26 October 2010
- * A lot scientific packages available from many areas (Mathematics, Physics, engineering)1 KB (149 words) - 14:08, 7 February 2024
- = Fedora Release Engineering Meeting :: Monday 2007-09-17 =854 bytes (138 words) - 15:37, 18 February 2014
- * Where: [http://kkwagh.edu.in/ KKW College of Engineering Nashik]1 KB (147 words) - 15:37, 8 December 2014
- ...nual national-level Technical Festival organised by students of Dr.B.C.Roy Engineering College, Durgapur.1 KB (140 words) - 14:12, 18 September 2016
- * Location: Gaziosmanpasa University, Faculty of Natural Sciences and Engineering1 KB (146 words) - 19:38, 5 April 2012
- ...7, and has been a Red Hat employee since 2001. Currently, he is the Fedora Engineering Manager. In addition to that, he is the chair of the Fedora Packaging Commi1 KB (216 words) - 14:17, 15 April 2009
- ...ill make sure that we have buy-in for this goal from RedHat management for engineering time.1 KB (184 words) - 16:29, 24 May 2008
- * Fedora Engineering (Paul Frields & Tom Callaway): $4,000 in Q4 * Travel for the following remotees from the Fedora Engineering team ($5.1K)4 KB (432 words) - 09:28, 30 November 2009
- * Location: Gaziosmanpasa University, Faculty of Natural Sciences and Engineering1 KB (146 words) - 19:19, 4 April 2012
- {{admon/important|This page is deprecated| All Fedora Release Engineering Documentation has moved [https://docs.pagure.org/releng/ here] with source = Fedora Release Engineering =8 KB (1,273 words) - 17:48, 3 November 2015
- ...th the Fedora Packaging Committee and with the (currently inactive) Fedora Engineering Services group. They will be tasked with both creating policies and guidel == Release Engineering ==8 KB (1,320 words) - 18:55, 6 September 2013
- {{admon/important|This page is deprecated| All Fedora Release Engineering Documentation has moved [https://docs.pagure.org/releng/ here] with source ...age had been orphaned and now has a new owner. When this happens, release engineering needs to "unblock" the package from koji tags.5 KB (674 words) - 17:55, 3 November 2015
- * Submit the guidelines for review (Board, Release Engineering, Infrastructure)2 KB (246 words) - 16:34, 24 May 2008
- Fedora Release Engineering uses a number of tools that are loosely coupled with one another in order t2 KB (247 words) - 20:01, 21 April 2015
- ...ering story - upstream commitment from Red Hat into this feature, a lot of engineering work by folks at OLPC (which is Fedora's biggest downstream deployment), an3 KB (460 words) - 16:08, 23 April 2018
- = Fedora Release Engineering Meeting :: Monday 2008-10-27 = ...e="color: #8c4a4a" | f13: #843 (Draft Fedora 11 Schedule) - Fedora Release Engineering - Trac - https://fedorahosted.org/rel-eng/ticket/84310 KB (1,272 words) - 01:51, 29 October 2008
- * FESCo approved a proposal from Release Engineering (rel-eng) to delay F10 by three weeks. The revised schedule can be found h1 KB (151 words) - 08:02, 18 September 2016
- ...ith students in the School of Computing, Informatics, and Decision Systems Engineering. A third day of hackfests will be held in the ASU Memorial Union, ASU's new3 KB (480 words) - 19:37, 4 October 2010
- ...and stability. Stressing the balance of new features with QA and release engineering to make Fedora releases both innovative and high quality. ...at for more than a decade in various roles including technical support and engineering. I'm one of the anaconda maintainers as well as the maintainer of (thankful7 KB (1,040 words) - 21:27, 16 June 2011
- * Faculty of Electrical and Computer Engineering, University of Prishtina.1 KB (144 words) - 18:22, 15 September 2010
- = Fedora Release Engineering Meeting :: Monday 2009-02-23 = ...span="2" | -!- f13 changed the topic of #fedora-meeting to: Fedora Release Engineering - Mass Rebuild15 KB (1,982 words) - 00:40, 24 February 2009
- ..., which will function as an independent subcommittee of FESCo, (the Fedora Engineering Steering Committee). FESCo will resolve issues which impact multiple workin ...m other major areas of Fedora - Quality Assurance, Infrastructure, Release Engineering, Documentation, Design, Websites, Ambassadors, Feature Wrangler, Marketing.4 KB (590 words) - 19:22, 11 September 2013
- ...medias/DVDs requested''': 150 (couting with Computer Science and Computer Engineering Students)1 KB (164 words) - 17:08, 23 May 2013
- ...ring: [https://pagure.io/releng/issues] (a check of an impact with Release Engineering is needed) --> <!-- REQUIRED FOR SYSTEM-WIDE AS WELL AS FOR SELF CONTAINED3 KB (464 words) - 19:06, 9 January 2023
- The benefit to Release Engineering should be self-evident: less tools, hosts, and services to maintain. This o * Release engineering: This feature does require coordination with release engineering (e.g. changes to installer image generation or update package delivery.)4 KB (658 words) - 14:24, 6 September 2016
- * Release Engineering lead was on out on 2010-07-09 * Build up the Release Engineering team so that alternate team members can compose releases10 KB (1,638 words) - 19:01, 24 November 2010
- === Fedora Engineering Steering Committee (FESCo) === ...gement is organized by the [[Fedora_Engineering_Steering_Committee |Fedora Engineering Steering Committee (FESCo)]].0 members (0 subcategories, 0 files) - 03:03, 14 August 2019
- # Ticket filed with Red Hat Engineering Operations: '''DONE by poelcat on 2009-05-18''' Ticket #: 41344 # Ticket filed with Red Hat Engineering Operations --'''DONE''' Ticket# 413458 KB (1,220 words) - 17:52, 14 July 2009
- * Release Engineering1 KB (173 words) - 15:48, 5 November 2010
- {{admon/important|This page is deprecated| All Fedora Release Engineering Documentation has moved [https://docs.pagure.org/releng/ here] with source ...ts official images for testing (boot images only, no full media). Release Engineering is responsible for creating them.4 KB (662 words) - 17:51, 3 November 2015
- *Where: Deogiri Institute of Engineering and Management Studies,Aurangabad1 KB (123 words) - 13:18, 12 September 2017
- [[Category: Release Engineering]]1 KB (178 words) - 13:49, 7 October 2016
- = List of scientific and engineering packages = == Electrical engineering ==11 KB (1,604 words) - 15:19, 22 June 2022
- * Location : Faculty of engineering , Alexandria , Egypt2 KB (198 words) - 18:01, 14 September 2012
- The benefit to Release Engineering should be self-evident: less tools, hosts, and services to maintain. This o * Release engineering: This feature does require coordination with release engineering (e.g. changes to installer image generation or update package delivery.)4 KB (682 words) - 13:56, 10 December 2015
- ...tute of Technology, Aurangabad. I am in Third Year of Computer Science And Engineering. I am Opensource enthusiastic girl. I love to promote opensource.1 KB (179 words) - 16:54, 11 January 2020
- = Fedora Release Engineering Meeting :: Monday 2009-03-09 = | colspan="2" | ---f13 has changed the topic to: Fedora Release Engineering Meeting - Roll Call38 KB (4,326 words) - 19:27, 9 March 2009
- ...mary : Primary driver of CVS package administration, Member FESCO, Release Engineering team, Pidgin and Spamassassin maintainer * Mission Statement : My goal is to work to help guide the overall engineering direction in the Fedora distribution.12 KB (1,817 words) - 16:26, 24 May 2008
- * providing alternative to all release engineering tools (repoquery, bodhi etc.) from yum-utils (ongoing) * Release engineering: Release engineering tools that are internal to the releng teams and not part of yum-utils will7 KB (1,134 words) - 17:21, 27 May 2015
- * Release engineering: No action from release engineering is needed for this change (libcurl ABI is kept), releng review requested at3 KB (422 words) - 15:07, 2 March 2018
- <!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? I ...ps://pagure.io/releng/issue/7256 #7256] (a check of an impact with Release Engineering is needed)5 KB (701 words) - 14:56, 2 March 2018
- [[Category:Release Engineering]]3 KB (434 words) - 19:07, 14 February 2009
- ...ps://pagure.io/releng/issue/7647 #7647] (a check of an impact with Release Engineering is needed) --> <!-- REQUIRED FOR SYSTEM-WIDE AS WELL AS FOR SELF CONTAINED3 KB (463 words) - 20:37, 15 January 2021
- = Fedora Release Engineering Meeting :: Monday 2008-12-15 = ...span="2" | -!- f13 changed the topic of #fedora-meeting to: Fedora Release Engineering - open floor10 KB (1,341 words) - 00:10, 17 December 2008
- ...ould be put to much better use if it were stored in a database. The entire engineering department could benefit from this data. Thus, I suggested to implement a w7 KB (1,239 words) - 16:25, 24 May 2008
- * Release Engineering processes1 KB (215 words) - 17:41, 13 June 2009
- * [http://www.impscet.net IMPS College of Engineering & Technology], Nityanandapur, P.O. - Chandipur (Kazigram), Malda, West Beng1 KB (188 words) - 09:15, 22 October 2009
- ...release, "Fedora Electronic Lab" targets mainly the Micro-Nano Electronic Engineering field. * A complete VLSI Simulation Kit Electronic Engineering ensuring Interoperability.7 KB (961 words) - 08:37, 19 August 2008
- ...proposed by the Release Engineering team and ratified by [[FESCo | Fedora Engineering Steering Committee (FESCo)]]. FESCo is responsible for overseeing the tech ...o this standard must be approved by the community-elected [[FESCo | Fedora Engineering Steering Committee (FESCo)]].7 KB (1,015 words) - 11:48, 13 January 2015
- = Fedora Release Engineering Meeting :: Monday 2008-06-30 = ...span="2" | -!- f13 changed the topic of #fedora-meeting to: Fedora Release Engineering Meeting - Roll Call29 KB (3,718 words) - 18:16, 2 July 2008
- === Fedora Engineering Steering Committee (FESCo) === ...o Fedora é organizada pelo [[Fedora_Engineering_Steering_Committee |Fedora Engineering Steering Committee (FESCo).]]0 members (0 subcategories, 0 files) - 10:56, 29 November 2016
- [[Category:Release Engineering]]2 KB (235 words) - 19:09, 14 February 2009
- ...any official policy would likely come through Fedora Legal and the Fedora Engineering Steering Committee. The substitution of Gnote for Tomboy on the Desktop Liv1 KB (237 words) - 18:49, 15 June 2009
- [[Category:Release Engineering]]1 KB (214 words) - 20:31, 19 September 2016
- # [[Summer Coding 2010 proposal - Kde usability inspector]] [Red Hat Engineering Brno funded - read note in the funding section] - Michal Luscon2 KB (245 words) - 04:26, 18 March 2011
- ...ps://pagure.io/releng/issue/7239 #7239] (a check of an impact with Release Engineering is needed) <!-- REQUIRED FOR SYSTEM WIDE AS WELL AS FOR SELF CONTAINED CHAN <!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? I5 KB (724 words) - 07:28, 30 May 2018
- ...in the language allowing it to remain relevant while the ethos of software engineering has matured. Details of the Python language throughout these stages of dev1 KB (227 words) - 15:51, 11 December 2015
- ...to hand code these bindings from scratch. As is the case with all Red Hat engineering efforts the result is being contributed to the community as an open source4 KB (568 words) - 18:24, 30 September 2010
- === Fedora Engineering Steering Committee (FESCo) === ...i Fedora è organizzata dal [[Fedora_Engineering_Steering_Committee |Fedora Engineering Steering Committee (FESCo)]].0 members (0 subcategories, 0 files) - 10:48, 24 February 2016
- = Fedora Release Engineering Meeting :: Monday 2008-05-19 = * Thereafter create a ''real'' release engineering mailing list20 KB (3,265 words) - 16:35, 13 February 2015
- Faculty of Electrical Engineering and Computing (FER), Zagreb, Croatia.1 KB (180 words) - 08:49, 13 June 2017
- ...pour le Développement de l'Informatique Libre) and kindly hosted by CPE an engineering college.2 KB (218 words) - 20:05, 5 March 2010
- Group: Red Hat Engineering1 KB (226 words) - 22:16, 8 January 2010
- ...: [https://pagure.io/releng/issue/7579] (a check of an impact with Release Engineering is needed)4 KB (539 words) - 13:33, 8 August 2019
- ...ps://pagure.io/releng/issue/9384 #9384] (a check of an impact with Release Engineering is needed) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> <!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? I5 KB (761 words) - 16:19, 21 July 2020
- ...and workshops on a wide variety of topics related to computer science and engineering.1 KB (173 words) - 22:57, 13 November 2017
- Target Audience: JIIT engineering students and Faculty2 KB (292 words) - 11:44, 17 November 2008
- <ul><li> I am also the first year of studying engineering in college Uninorte in my city. I hope to be a Good Engineer.1 KB (250 words) - 18:55, 6 July 2009
- ...: [https://pagure.io/releng/issue/6881] (a check of an impact with Release Engineering is needed)3 KB (501 words) - 15:59, 25 July 2017
- === Руководящий комитет Fedora Engineering (FESCo) === ...яется [[Fedora_Engineering_Steering_Committee|Руководящим комитетом Fedora Engineering (FESCo)]].1 member (0 subcategories, 0 files) - 12:41, 22 December 2015
- {{admon/important|This page is deprecated| All Fedora Release Engineering Documentation has moved [https://docs.pagure.org/releng/ here] with source == Fedora Release Engineering Philosophy ==7 KB (1,163 words) - 17:48, 3 November 2015
- * FESCo had no objections to the adjustment(1) proposed by the Release Engineering team.1 KB (172 words) - 08:00, 18 September 2016
- particularly ones without development/engineering experience as I think a3 KB (456 words) - 10:56, 2 June 2008
- === Philippines - University of the Philippines Engineering Week ( 7-11 December 2009 ) === '''Where:''' College of Engineering, University of the Philippines, Diliman, Quezon City, Philippines6 KB (915 words) - 10:03, 30 November 2009
- ...e coordination within the distribution (for example mass rebuilds, release engineering or other teams effort etc.) * Release engineering: Impact check [https://pagure.io/releng/issue/11299]5 KB (817 words) - 17:46, 21 August 2023
- ...e coordination within the distribution (for example mass rebuilds, release engineering or other teams effort etc.) * Release engineering: Impact check [https://pagure.io/releng/issue/10637]5 KB (819 words) - 15:26, 2 March 2022
- = Fedora Release Engineering Meeting Minutes = [[Category:Release Engineering]]6 KB (428 words) - 23:16, 29 July 2015
- ...t package builds and get information about the buildsystem. Fedora Release Engineering uses koji to tag builds and coordinate updates/releases.2 KB (358 words) - 21:12, 25 May 2008
- ...ekend to work the booth and answer questions. || en, es || No || No || Non-engineering aspects of Fedora community ...1-3 hours at the booth and answer questions. || en, es || No || No || Non-engineering aspects of Fedora community6 KB (791 words) - 18:21, 20 January 2021
- ...of Patras, Greece. My research interests include Data Structures, Software Engineering, Development Processes, Design Patterns and Code Refactoring.5 KB (867 words) - 16:31, 24 May 2008
- * Fedora Release Engineering Overview by [[User:Tuanta|Truong Anh Tuan]] - Fedora Ambassador, FAmSCo mem2 KB (230 words) - 03:36, 25 August 2013
- * Release Engineering1 KB (170 words) - 07:59, 18 September 2016
- ...e coordination within the distribution (for example mass rebuilds, release engineering or other teams effort etc.) * Release engineering: Impact check [https://pagure.io/releng/issue/10174]5 KB (825 words) - 15:59, 8 July 2021
- ...lease engineering: #Releng issue number (a check of an impact with Release Engineering is needed)4 KB (599 words) - 17:09, 13 October 2018
- ...ps://pagure.io/releng/issue/6854 #6854] (a check of an impact with Release Engineering is needed) <!-- REQUIRED FOR SYSTEM WIDE AS WELL AS FOR SELF CONTAINED CHAN <!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? I6 KB (884 words) - 19:18, 3 November 2017
- ...got.tce.edu'''||'''L.Guruprasad'''||'''L.Guruprasad,Thiagarajar College of Engineering, Madurai,Tamil Nadu, India, PIN: 625015, Phone:+919994834868,email: lgp1711 ...|'''Jain Basil Aliyas'''||'''Jain Basil Aliyas, Chandra Villa, Movie Road, Engineering College PO, Pallimoola, Trichur District, Kerala, India, PIN:680009,Phone:4 KB (554 words) - 17:46, 30 May 2009
- ...Lab nor its spin. During my post-graduate studies in Micro-Nano Electronic Engineering, I needed VLSI simulation tools. I started packaging the VLSI simulation to ...ou have plans for expanding this post F8, perhaps targeting other areas of engineering?'''9 KB (1,509 words) - 16:26, 24 May 2008
- ...e coordination within the distribution (for example mass rebuilds, release engineering or other teams effort etc.) * Release engineering: Impact check [https://pagure.io/releng/issue/10257]6 KB (843 words) - 12:00, 25 August 2021
- * FESCo approved the schedule for Fedora 10 presented by Release Engineering.1 KB (202 words) - 08:01, 18 September 2016
- ...e coordination within the distribution (for example mass rebuilds, release engineering or other teams effort etc.) * Release engineering: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->7 KB (1,134 words) - 10:03, 31 March 2015
- = Fedora Release Engineering Meeting :: Monday 2008-07-14 = ...span="2" | -!- f13 changed the topic of #fedora-meeting to: Fedora Release Engineering - roll call28 KB (3,620 words) - 22:09, 14 July 2008
- ...Lab nor its spin. During my post-graduate studies in Micro-Nano Electronic Engineering, I needed VLSI simulation tools. I started packaging the VLSI simulation to ...ou have plans for expanding this post F8, perhaps targeting other areas of engineering?'''10 KB (1,509 words) - 00:27, 8 June 2008
- ...e coordination within the distribution (for example mass rebuilds, release engineering or other teams effort etc.) * Release engineering: Impact check [https://pagure.io/releng/issue/9903]6 KB (836 words) - 16:45, 7 January 2021
- ...ps://pagure.io/releng/issue/7647 #7647] (a check of an impact with Release Engineering is needed) --> <!-- REQUIRED FOR SYSTEM-WIDE AS WELL AS FOR SELF CONTAINED4 KB (549 words) - 20:04, 14 August 2019
- ...avaScript, JQuery and Android Studio. I have made a Mobile Application for Engineering Student as a mini project in this year.4 KB (561 words) - 07:26, 24 March 2016
- * Release engineering: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> <!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? I4 KB (632 words) - 12:24, 15 January 2015
- ...ages in the docker index, but we'd like them to really come out of release engineering. Release Engineering approval/intervention would be needed at some point (details still TBD)10 KB (1,632 words) - 18:06, 27 June 2014
- # Ticket filed with Red Hat Engineering Operations: '''Done by poelcat--ticket# 53658'''; scheduled for 2009-11-16 # Ticket filed with Red Hat Engineering Operations -- '''done by poelcat--ticket# 53659''' scheduled for 2009-11-188 KB (1,212 words) - 15:27, 18 November 2009
- *Where: Deogiri Engineering College, Aurangabad1 KB (157 words) - 15:31, 31 August 2016
- ...e coordination within the distribution (for example mass rebuilds, release engineering or other teams effort etc.) * Release engineering: Impact check [https://pagure.io/releng/issues/8340]6 KB (878 words) - 15:23, 28 May 2019
- ...e coordination within the distribution (for example mass rebuilds, release engineering or other teams effort etc.) * Release engineering: Impact check [https://pagure.io/releng/issue/9253]6 KB (867 words) - 18:39, 7 April 2020
- ...ow up the world. I guess the policy is as stated, except that the release engineering team (with Board approval or something like that) can choose to make except ...chnical steering committee which combines members from Fedora Core release engineering team, FESCo and the packaging committee in the future. ''[See above... sayi7 KB (1,090 words) - 10:06, 18 September 2016
- ...ps://pagure.io/releng/issue/7647 #7647] (a check of an impact with Release Engineering is needed) <!-- REQUIRED FOR SYSTEM-WIDE AS WELL AS FOR SELF CONTAINED CHAN4 KB (563 words) - 23:17, 9 August 2018
- ...: [https://pagure.io/releng/issue/8024] (a check of an impact with Release Engineering is needed)4 KB (582 words) - 04:37, 14 September 2019
- Red Hat Bangalore Engineering Office1 KB (209 words) - 05:13, 5 November 2019
- * Release engineering: No action from release engineering is needed for this change (libcurl ABI is kept).4 KB (586 words) - 12:21, 4 November 2017
- ...of tools suitable for users who are involved in the Micro-Nano Electronic Engineering field. It is an installable image available for x86 systems and is very su3 KB (524 words) - 16:36, 24 May 2008
- = Fedora Release Engineering Meeting :: Monday 2008-01-07 = ...olspan="2">-!- f13 changed the topic of #fedora-meeting to: Fedora Release Engineering Meeting</td><td>13:06</td></tr>26 KB (4,402 words) - 17:33, 13 February 2015
- [[Category:Release Engineering]]2 KB (318 words) - 18:25, 7 February 2011
- ...part of the Fedora Ambassador team. I'm also involved with Fedora release engineering, and general troubleshooting that needs doing. I'm coordinating efforts on4 KB (695 words) - 21:18, 26 October 2009
- = Fedora Release Engineering Meeting :: Monday 2008-06-23 = | colspan="3" | < zodbot> f13: #23 (Fedora 10 Naming) - Fedora Release Engineering - Trac - https://fedorahosted.org/projects/rel-eng/ticket/2313 KB (2,173 words) - 23:16, 27 June 2008
- === Release Engineering ===7 KB (1,171 words) - 13:58, 17 June 2012
- ...'' [http://en.wikipedia.org/wiki/MIT_College_of_Engineering MIT College of Engineering], Pune, India * India is one of Red Hat's largest engineering centers in the world. A lot of the engineers play a very active role in th9 KB (1,282 words) - 22:37, 11 February 2015
- ...e coordination within the distribution (for example mass rebuilds, release engineering or other teams effort etc.) ...ps://pagure.io/releng/issue/7249 #7249] (a check of an impact with Release Engineering is needed) <!-- REQUIRED FOR SYSTEM WIDE AS WELL AS FOR SELF CONTAINED CHAN7 KB (1,029 words) - 14:52, 2 March 2018
- ...tps://fedorapeople.org/groups/schedule/f-21/f-21-releng-tasks.html Release Engineering]3 KB (361 words) - 03:42, 7 December 2014
- ...ttp://openstreetmap.org/?mlat=23.54494&mlon=87.34217&zoom=13 Dr. B. C. Roy Engineering College], Durgapur, India2 KB (283 words) - 16:50, 3 August 2009
- [[Category:Release Engineering]]2 KB (352 words) - 23:23, 13 August 2009
- ...roposal for the build system bits to remain the same, but the QA & Release Engineering processes will be done by the PPC team.2 KB (308 words) - 16:27, 24 May 2008
- ...://poelstra.fedorapeople.org/schedules/f-12/f-12-releng-tasks.html Release Engineering]3 KB (362 words) - 18:50, 8 November 2011
- At the milestone freeze, ''pushes''<ref>A ''push'' is a release engineering term for moving a package into a particular repository of packages.</ref> f [[Category:Release Engineering SOPs]]5 KB (767 words) - 00:13, 12 October 2017
- ...e coordination within the distribution (for example mass rebuilds, release engineering or other teams effort etc.) = Release Engineering Automation Workflow Engine =18 KB (2,360 words) - 20:02, 17 August 2016
- === What are the most pressing issues facing Fedora today (from engineering POV)? What should we do about them? === Release engineering. We need a systematic review of our releng7 KB (1,146 words) - 11:42, 3 February 2015
- * Release Engineering ticket: https://pagure.io/releng/issue/8783 * Release engineering: (a check of an impact with Release Engineering is needed) <!-- REQUIRED FOR SYSTEM WIDE AS WELL AS FOR SELF CONTAINED CHAN8 KB (1,181 words) - 15:25, 29 March 2020
- ...[https://pagure.io/releng/issues/9329] (a check of an impact with Release Engineering is needed) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> <!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? I6 KB (846 words) - 18:43, 7 April 2020
- {{admon/important|This page is deprecated| All Fedora Release Engineering Documentation has moved [https://docs.pagure.org/releng/ here] with source [[Category:Release Engineering SOPs]]5 KB (729 words) - 17:52, 3 November 2015
- === What are the most pressing issues facing Fedora today (from engineering POV)? What should we do about them? === The second one is a problem of resources or really clever engineering if we figure ways to solve it7 KB (1,262 words) - 11:55, 3 February 2015
- = Release Engineering Meeting :: Monday 2007-12-04 = ...olspan="2">-!- f13 changed the topic of #fedora-meeting to: Fedora Release Engineering Meeting</td><td>13:00</td></tr>23 KB (3,794 words) - 17:41, 13 February 2015
- scale by focusing engineering efforts on supplying a base disk images, rpms, and ...group member may act as a coordinator for quality assurance or for release engineering.6 KB (961 words) - 21:03, 1 November 2022
- # Ticket filed with Red Hat Engineering Operations: '''done [[User:Poelstra|poelcat]] 17:54, 8 March 2010 (UTC)''' # Ticket filed with Red Hat Engineering Operations --'''Done by poelstra''' Ticket #632388 KB (1,278 words) - 20:09, 8 July 2010
- ...kage maintainers, signed and pushed out to testing repositories by release engineering, and made available to test by package testers. The [ http://fedoraproject.2 KB (302 words) - 17:44, 19 October 2011
- Red Hat Bangalore Engineering Office2 KB (229 words) - 09:57, 19 November 2018
- Red Hat Bangalore Engineering Office2 KB (230 words) - 12:42, 18 June 2019
- ...: [https://pagure.io/releng/issue/6880] (a check of an impact with Release Engineering is needed)4 KB (619 words) - 12:56, 2 March 2018
- This is a summary of important goals for the [[Fedora Engineering|Fedora Engineering team]] for Red Hat Fiscal Year 2017 (March 2016 - February 2017). ...r of a '''lead person''' shows accountability for whatever work the Fedora Engineering team has committed to. It may not be the same as a person leading an overa7 KB (1,006 words) - 16:58, 15 February 2018
- * Engineering/CS student who needs a personal system for software classwork and personal We want to focus on engineering practices that ensures that the core product offered is of the highest qual9 KB (1,420 words) - 22:23, 2 September 2014
- * Release engineering: [https://pagure.io/releng/issues #Releng issue number] <!-- REQUIRED FOR S <!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? I4 KB (616 words) - 14:47, 11 November 2021
- Having the Fedora ecosystem (from users to release engineering) maintain tooling that operates on all three of "container images", RPMs, a * Release engineering: https://pagure.io/releng/issue/103997 KB (990 words) - 14:12, 25 February 2022
- ...s a highly curated program around three topics: architecture, culture, and engineering.4 KB (499 words) - 14:26, 4 December 2017
- Applications/Engineering2 KB (261 words) - 19:37, 11 February 2017
- ...: [https://pagure.io/releng/issue/6879] (a check of an impact with Release Engineering is needed)4 KB (660 words) - 11:25, 21 August 2017
- ...ag (and secondary architecture building) will need assistance from release-engineering. <!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? I7 KB (1,043 words) - 17:42, 11 September 2016
- * Germany - [http://www.aum-engineering.com/ AUM Engineering] , email5 KB (672 words) - 16:33, 24 May 2008
- Group: Applications/Engineering Group: Applications/Engineering6 KB (813 words) - 17:06, 8 March 2014
- ...t. An alternative venue is available in the form of meeting room(s) at the Engineering office of Red Hat at Raycom, see [[#raycom|Alternative venue]] ...). This option is considered due to the good relationship with the Red Hat Engineering office in Beijing. Discussions about renting classrooms or other co-operati15 KB (2,229 words) - 03:50, 29 September 2011
- ...esentation about Fedora the distribution and the project at ENISo, a local Engineering school in Sousse, Tunisia.2 KB (331 words) - 21:58, 9 May 2012
- * Faculty of electronic engineering, Menouf City , Menoufya Governorate2 KB (294 words) - 15:44, 12 July 2010
- ...e current status of the feature by the following milestones on the Release Engineering schedule:2 KB (336 words) - 15:33, 9 December 2011
- * Release engineering: [https://pagure.io/releng/issue/10169 #10169] <!-- REQUIRED FOR SYSTEM WID <!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? I5 KB (674 words) - 15:05, 6 July 2021
- ...iversidad de Jaen like associate professor in the Department of Electronic Engineering and Automatic. Arturo writes technical articles for magazines like ''Todo L2 KB (321 words) - 07:39, 22 March 2010
- === Release engineering === ...gure.io/releng/issue/7227 Ticket #7227] (a check of an impact with Release Engineering is needed)11 KB (1,780 words) - 14:35, 2 March 2018
- * No reverse engineering, decompilation, or disassembly of this software2 KB (342 words) - 20:22, 11 May 2009
- * Get buy in from the Red Hat engineering folks. Most of this is for naught if we get reviewers but the maintainers5 KB (741 words) - 16:32, 24 May 2008
- Target Audience: release engineering2 KB (276 words) - 22:09, 8 January 2010
- ...ng/issue/7486 Releng issue number 7486] (a check of an impact with Release Engineering is needed) <!-- REQUIRED FOR SYSTEM WIDE AS WELL AS FOR SELF CONTAINED CHAN <!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? I7 KB (1,033 words) - 15:59, 19 February 2020
- ...ttp://fedorapeople.org/groups/schedule/f-22/f-22-releng-tasks.html Release Engineering]3 KB (346 words) - 06:28, 26 February 2015
- The elected positions cover Fedora's subprojects not under the engineering or outreach banners (Documentation, Translation, etc.), and the community a2 KB (295 words) - 11:17, 10 December 2023
- * Release engineering tracker: [https://pagure.io/releng/issue/8061 #8061] ...: [https://pagure.io/releng/issue/7595] (a check of an impact with Release Engineering is needed)7 KB (1,047 words) - 17:52, 25 January 2019
- = Fedora Release Engineering Meeting :: Monday 2008-03-31 = ...olspan="2">-!- f13 changed the topic of #fedora-meeting to: Fedora Release Engineering Meeting - Roll Call</td><td>13:07</td></tr>25 KB (4,067 words) - 16:56, 13 February 2015
- = Fedora Release Engineering Meeting :: Monday 2008-01-21 = ...olspan="2">-!- f13 changed the topic of #fedora-meeting to: Fedora Release Engineering Meeting</td><td>13:02</td></tr>25 KB (4,065 words) - 17:29, 13 February 2015
- ...e the "Fedora for Developers" live image and will work with Fedora release engineering on propagation / distribution.2 KB (359 words) - 13:23, 9 October 2009
- ....io/releng/issues #Releng issue number] (a check of an impact with Release Engineering is needed) <!-- REQUIRED FOR SYSTEM WIDE AS WELL AS FOR SELF CONTAINED CHAN <!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? I7 KB (1,138 words) - 18:37, 5 August 2020
- ...the goal is to provide single point of information for Fedora QE, release engineering and other teams. Mostly to avoid late surprises during Fedora release compo * release engineering knows what's going to be produced for upcoming release ahead of time (we ad8 KB (1,070 words) - 14:53, 31 January 2017
- ...e coordination within the distribution (for example mass rebuilds, release engineering or other teams effort etc.) ...ps://pagure.io/releng/issue/8551 #8551] (a check of an impact with Release Engineering is needed) <!-- REQUIRED FOR SYSTEM WIDE AS WELL AS FOR SELF CONTAINED CHAN9 KB (1,401 words) - 02:56, 12 August 2019
- * FESCo approved the schedule proposed by Release-Engineering after a long discussion. https://www.redhat.com/archives/fedora-advisory-b2 KB (274 words) - 08:01, 18 September 2016
- = Fedora Release Engineering Meeting :: Monday 2008-07-07 = * spins for Fedora 9 - Fedora Release Engineering - Trac - https://fedorahosted.org/projects/rel-eng/ticket/2442 KB (5,525 words) - 19:32, 11 July 2008
- ...://poelstra.fedorapeople.org/schedules/f-13/f-13-releng-tasks.html Release Engineering]3 KB (416 words) - 18:48, 8 November 2011
- = Fedora Release Engineering Meeting :: Monday 2008-03-24 = ...ass="text" style="color: #407a40">has changed the topic to: Fedora Release Engineering Meeting - Roll Call</td><td class="time">13:01</td></tr>28 KB (4,837 words) - 16:57, 13 February 2015
- ...e coordination within the distribution (for example mass rebuilds, release engineering or other teams effort etc.) ...oint of this change is to modify the existing compose tool used by Release Engineering (pungi) so that it can consume content for a new variant from the MBS.10 KB (1,539 words) - 16:58, 12 December 2016
- ...e coordination within the distribution (for example mass rebuilds, release engineering or other teams effort etc.) * Release engineering: [https://pagure.io/releng/issue/6911 #6911]5 KB (748 words) - 08:43, 8 August 2017
- ...e coordination within the distribution (for example mass rebuilds, release engineering or other teams effort etc.) * Release engineering: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->8 KB (1,311 words) - 08:46, 10 April 2014
- * Release engineering: (a check of an impact with Release Engineering is needed) <!-- REQUIRED FOR SYSTEM WIDE AS WELL AS FOR SELF CONTAINED CHAN <!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? I7 KB (1,100 words) - 19:18, 10 February 2020
- '''Where''': [http://www.jmi.nic.in/Fengg/FoEngg.htm Faculty of Engineering and Technology ], JMI University, New Delhi, India [http://maps.google.com/3 KB (391 words) - 13:14, 18 March 2011
- ...the goal is to provide single point of information for Fedora QE, release engineering and other teams. Mostly to avoid late surprises during Fedora release compo * release engineering knows what's going to be produced for upcoming release ahead of time (we ad9 KB (1,183 words) - 14:49, 31 January 2017
- ...e coordination within the distribution (for example mass rebuilds, release engineering or other teams effort etc.) * Release engineering: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->9 KB (1,454 words) - 11:25, 15 May 2014
- ....io/releng/issues #Releng issue number] (a check of an impact with Release Engineering is needed) <!-- REQUIRED FOR SYSTEM WIDE AS WELL AS FOR SELF CONTAINED CHAN <!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? I8 KB (1,269 words) - 09:30, 25 August 2017
- * Release engineering: N/A <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> <!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? I5 KB (799 words) - 21:53, 31 March 2015
- ...ps://pagure.io/releng/issue/9772 #9772] (a check of an impact with Release Engineering is needed)5 KB (744 words) - 16:40, 19 December 2023
- ...all developers and consumers of Fedora would be affected by this change. Engineering schedules will need to be adjusted for the new freezes and dates, IS/IT/Mir [[Category:Release Engineering]]8 KB (1,334 words) - 18:29, 14 February 2009
- == Release Engineering ==8 KB (1,200 words) - 17:48, 10 December 2013
- * I’m a Engineering student at Khaja Bande Nawaz College of Engineering, Gulbarga majoring in Electronics and Communication.6 KB (976 words) - 12:42, 21 March 2014
- === Fedora Engineering Steering Committee Meeting 2008-04-10 === === Fedora Release Engineering Meeting 2008-04-07 ===12 KB (1,594 words) - 21:10, 20 September 2016
- ...workshop || [http://www.shakthimaan.com/Mambo/gallery/album54 Government Engineering College, Barton Hill, Thiruvananthapuram, Kerala, India] || [[User:shakthim ...8, 2009 || [[FedoraEvents/KGEC_LUG|Fedora Workshop]] || Kalyani Government Engineering College, India || [[User:rohit01|Rohit Gupta]] || Workshop on administratin15 KB (1,758 words) - 21:14, 19 September 2016
- ...the goal is to provide single point of information for Fedora QE, release engineering and other teams. Mostly to avoid late surprises during Fedora release compo * release engineering knows what's going to be produced for upcoming release ahead of time (we ad9 KB (1,217 words) - 14:51, 31 January 2017
- {{admon/important|This page is deprecated| All Fedora Release Engineering Documentation has moved [https://docs.pagure.org/releng/ here] with source [[Category:Release Engineering SOPs]]5 KB (808 words) - 17:53, 3 November 2015
- ...e coordination within the distribution (for example mass rebuilds, release engineering or other teams effort etc.) ...est, https://github.com/intel/thermal_daemon/pull/224). Should the reverse engineering effort be merged, or if the user installs dptfxtract, then they can expect10 KB (1,580 words) - 19:00, 28 July 2020
- ...t, etc. are actually implemented while I was learning them as a part of my Engineering Curriculum. I feel very grateful to Fedora and the Fedora Community with wh ...achine Learning and Image Processing Courses during the degree in Computer Engineering(Language- Python 3).7 KB (1,145 words) - 06:36, 25 March 2016
- ...hnical fonts » for a font with coverage of technical unicode blocks (math, engineering, music and other non-text blocks).2 KB (339 words) - 05:52, 21 January 2015
- ...hnical fonts » for a font with coverage of technical unicode blocks (math, engineering, music and other non-text blocks).2 KB (339 words) - 10:46, 21 January 2015
- ...hnical fonts » for a font with coverage of technical unicode blocks (math, engineering, music and other non-text blocks).2 KB (339 words) - 15:23, 13 October 2014
- ...hnical fonts » for a font with coverage of technical unicode blocks (math, engineering, music and other non-text blocks).2 KB (339 words) - 06:23, 28 January 2015
- ...hnical fonts » for a font with coverage of technical unicode blocks (math, engineering, music and other non-text blocks).2 KB (339 words) - 05:53, 21 January 2015
- ...hnical fonts » for a font with coverage of technical unicode blocks (math, engineering, music and other non-text blocks).2 KB (339 words) - 06:27, 28 January 2015
- ...hnical fonts » for a font with coverage of technical unicode blocks (math, engineering, music and other non-text blocks).2 KB (339 words) - 05:54, 21 January 2015
- ...hnical fonts » for a font with coverage of technical unicode blocks (math, engineering, music and other non-text blocks).2 KB (339 words) - 06:26, 28 January 2015
- ...hnical fonts » for a font with coverage of technical unicode blocks (math, engineering, music and other non-text blocks).2 KB (339 words) - 05:54, 21 January 2015
- ...e coordination within the distribution (for example mass rebuilds, release engineering or other teams effort etc.) * Release engineering: [https://pagure.io/releng/issue/6912 #6912]5 KB (731 words) - 08:46, 8 August 2017
- ...e coordination within the distribution (for example mass rebuilds, release engineering or other teams effort etc.) ...ps://pagure.io/releng/issue/8003 #8003] (a check of an impact with Release Engineering is needed) <!-- REQUIRED FOR SYSTEM WIDE AS WELL AS FOR SELF CONTAINED CHAN9 KB (1,458 words) - 01:50, 17 January 2019
- ...ugh the development process by the [[Fedora_Engineering_Steering_Committee|engineering steering committee]]. ...s]]に従って制御されます。いわゆる''変更''が提案されると、最初に[[Fedora_Engineering_Steering_Committee|engineering steering committee]]が、レビューし、開発工程は、進捗管理�22 KB (1,936 words) - 22:32, 1 April 2019
- * Release engineering: [https://pagure.io/releng/issue/9390 Releng issue #9390] If compat package <!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? I5 KB (789 words) - 21:00, 3 March 2022
- ...hnical fonts » for a font with coverage of technical unicode blocks (math, engineering, music and other non-text blocks).2 KB (341 words) - 06:28, 28 January 2015
- ...osed (using the guidelines described elsewhere) and accepted by the Fedora Engineering Steering Committee (FESCo) up until the ''Feature Submission Deadline'':2 KB (376 words) - 22:21, 25 September 2014
- ...hnical fonts » for a font with coverage of technical unicode blocks (math, engineering, music and other non-text blocks).2 KB (343 words) - 15:25, 13 October 2014
- ...hnical fonts » for a font with coverage of technical unicode blocks (math, engineering, music and other non-text blocks).2 KB (343 words) - 15:23, 13 October 2014
- ...e coordination within the distribution (for example mass rebuilds, release engineering or other teams effort etc.) * Release engineering: N/A (not a System Wide Change)5 KB (723 words) - 12:10, 27 February 2017
- * Release engineering: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> <!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? I6 KB (995 words) - 14:28, 5 November 2013
- ...ps://pagure.io/releng/issue/9632 #9632] (a check of an impact with Release Engineering is needed)5 KB (728 words) - 10:26, 18 April 2021
- * TomCallaway (Fedora Engineering Manager) - Fedora Project Booth3 KB (423 words) - 16:06, 30 August 2009
- ...://poelstra.fedorapeople.org/schedules/f-14/f-14-releng-tasks.html Release Engineering]3 KB (415 words) - 22:26, 13 December 2011
- ...e coordination within the distribution (for example mass rebuilds, release engineering or other teams effort etc.) ...ead of Alpha releases from the cycle frees up release engineering, quality engineering, development and project management resources for other work. It potentiall9 KB (1,420 words) - 02:38, 14 November 2017
- Release engineering asked if FESCo objected to repodata signing, or continued work on deltarpm2 KB (230 words) - 08:04, 18 September 2016
- * Release engineering: This change does not require coordination with or impact release engineering and does not require a mass rebuild.5 KB (775 words) - 20:35, 15 January 2021
- ...full capacity. If given a chance, I would love to be a part of the Release Engineering team, and the Fonts SIG.2 KB (305 words) - 08:17, 19 March 2014
- ...hnical fonts » for a font with coverage of technical unicode blocks (math, engineering, music and other non-text blocks).2 KB (351 words) - 15:27, 13 October 2014
- {{Admon/note | This feature idea is under requirements engineering stages}}3 KB (463 words) - 19:03, 1 August 2008
- Red Hat has a large office in Pune with many members from Engineering, L10N, I18N and support services who are Fedora community members and acti2 KB (418 words) - 09:04, 16 July 2011
- ...thanks to the welcoming and co-operative nature of the Spins SIG, release engineering and the Fedora design and websites team.2 KB (364 words) - 23:30, 3 April 2012
- students from many colleges (engineering + computer & IT)..2 KB (270 words) - 20:18, 19 September 2016
- * Number of participants: 14 (50% people from trivago engineering team + 50% external guests)2 KB (296 words) - 13:06, 1 June 2018
- * Release engineering: Side tag creation (unless there is a mass rebuild, then no assistance). If we rely on a mass rebuild, we would have to unwind the damage--Release Engineering would untag what succeeded; pmachata would revert Boost rebase; pmachata wo6 KB (845 words) - 12:58, 20 August 2013
- ...e. Also a standardized package name will have to be discussed with release engineering team.2 KB (397 words) - 11:56, 16 November 2011
- * Release engineering: [https://pagure.io/releng/issue/10387 Releng issue #10387] Disable a bunch <!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? I5 KB (723 words) - 16:20, 1 December 2021
- ...et involved me into Fedora. I am interested in working with Fedora Release Engineering team.2 KB (326 words) - 16:56, 3 May 2013
- * Release engineering: This feature doesn't require coordination with release engineering.5 KB (784 words) - 13:35, 25 August 2015
- ...e coordination within the distribution (for example mass rebuilds, release engineering or other teams effort etc.) * Release engineering: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->10 KB (1,623 words) - 09:50, 17 December 2013
- ...ttp://fedorapeople.org/groups/schedule/f-22/f-22-releng-tasks.html Release Engineering]3 KB (426 words) - 19:04, 9 April 2015
- = Fedora Release Engineering Meeting :: Monday 2008-01-14 = * Release Engineering Schedule: http://poelstra.fedorapeople.org/schedules/f-9/f-9-releng-tasks.h33 KB (5,290 words) - 17:31, 13 February 2015
- *Where: '''Chh.Shahu College of Engineering'''2 KB (260 words) - 03:18, 31 August 2015
- {{admon/important|This page is deprecated| All Fedora Release Engineering Documentation has moved [https://docs.pagure.org/releng/ here] with source ...that the mass rebuild has already been approved and scheduled via release engineering and FESCo. Coordinate with10 KB (1,676 words) - 14:45, 18 September 2016
- ...ps://pagure.io/releng/issue/7920 #7920] (a check of an impact with Release Engineering is needed) <!-- REQUIRED FOR SYSTEM WIDE AS WELL AS FOR SELF CONTAINED CHAN5 KB (778 words) - 22:41, 4 December 2018
- |20:30 pm - 21:00 pm || Mini Workshop Spyder, Spin : Sceintific & Engineering || [[User:creaturahpc| Oscar Gonzalez]]2 KB (260 words) - 21:25, 12 November 2015
- ...jects. It also functions as a test equipment for electronics hobbyists and engineering students.2 KB (374 words) - 14:28, 26 August 2014
- Key: '''FE''' = Fedora Engineering; '''CA''' = Community Architecture. Villas costs are expressed as $60 for 33 KB (377 words) - 17:33, 28 July 2013
- ...e coordination within the distribution (for example mass rebuilds, release engineering or other teams effort etc.) * Release engineering: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->9 KB (1,499 words) - 05:02, 24 December 2014
- * [[Development/SteeringCommittee/Nominations|FESCo (Engineering)]] (4 seats)3 KB (367 words) - 15:54, 7 May 2009
- ...have been accepted by the Fedora [[Fedora_Engineering_Steering_Committee |Engineering Steering Committee]] for the Fedora 28 Release as System Wide Changes. ...have been accepted by the [[Fedora_Engineering_Steering_Committee |Fedora Engineering Steering Committee]] for the Fedora 28 Release as Self Contained Changes.4 KB (592 words) - 01:55, 16 October 2018
- ...e coordination within the distribution (for example mass rebuilds, release engineering or other teams effort etc.) * Release engineering: N/A10 KB (1,545 words) - 13:57, 18 November 2013
- ...n, working with QA to develop criteria and tests, and working with release engineering to land the changes to image building. I plan to be actively involved in al * Release engineering: Yes, Jay Greguske, Andrew Thomas, and I are working on the improvements to6 KB (887 words) - 14:33, 19 August 2013
- = Fedora Release Engineering Meeting :: Monday 2008-11-03 = ...f13: #865 (Compose Fedora 10 Preview "Spins" Live images) - Fedora Release Engineering - Trac - https://fedorahosted.org/rel-eng/ticket/86550 KB (6,715 words) - 05:23, 4 November 2008
- * Release engineering: N/A <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> <!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? I5 KB (782 words) - 17:05, 22 April 2016
- ...e coordination within the distribution (for example mass rebuilds, release engineering or other teams effort etc.) * Release engineering: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->10 KB (1,687 words) - 18:27, 3 April 2014
- ...e coordination within the distribution (for example mass rebuilds, release engineering or other teams effort etc.) * Release engineering: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->10 KB (1,687 words) - 18:28, 3 April 2014
- | Release Engineering SOPs || Fedora Release Engineering is working on drafting Standard Operating Proceedures to cover the tasks we6 KB (907 words) - 12:39, 12 September 2010
- ...hnical fonts » for a font with coverage of technical unicode blocks (math, engineering, music and other non-text blocks).2 KB (361 words) - 13:11, 8 December 2009
- Pungi is set of tools which is used by Release Engineering to create composes of Fedora and RHEL. ...adata (preferably json with python-library see [https://github.com/release-engineering/productmd productmd]) so other tool can take it as input.3 KB (406 words) - 11:06, 23 January 2019
- ...ps://pagure.io/releng/issue/8549 #8549] (a check of an impact with Release Engineering is needed)5 KB (821 words) - 02:59, 12 August 2019
- * working with [https://docs.pagure.org/releng/ Release Engineering] on Composing trees for that architecture * Participate in and give progress reports to the Release Engineering meeting on a weekly basis9 KB (1,210 words) - 23:19, 19 April 2023
- ...e coordination within the distribution (for example mass rebuilds, release engineering or other teams effort etc.) * Release engineering: Mass rebuild requested6 KB (805 words) - 15:17, 17 February 2022
- * Release engineering: N/A <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> <!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? I6 KB (887 words) - 16:14, 14 October 2013
- # Script executed by RHT Engineering Operations which queries bugs according to following criteria and takes the * Script written and executed by RHT Engineering Operations which selects bugs according to specified criteria and takes the9 KB (1,425 words) - 14:25, 5 June 2008