From Fedora Project Wiki
Page title matches
- #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
- 4 KB (710 words) - 14:28, 4 February 2019
- 32 bytes (4 words) - 18:55, 10 June 2009
- 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
- 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
- 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
- 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
- #REDIRECT [[Archive:Release Engineering Release Tickets]]57 bytes (6 words) - 12:54, 8 August 2014
Page text matches
- #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