From Fedora Project Wiki

Results 1 – 139 of 2,542
Advanced search

Search in namespaces:

Page title matches

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
  • ...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
  • .../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
  • {{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 Engineering
    336 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 Te
    689 bytes (103 words) - 16:34, 24 May 2008
  • Category for Release Engineering SOPs
    23 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 [[Community Platform Engineering/Flock]]
    50 bytes (5 words) - 16:58, 15 February 2018
  • #REDIRECT [[Fedora Engineering Steering Committee]]
    51 bytes (5 words) - 21:45, 1 February 2010
  • # Re-confirm that release day is on track with release engineering. # Confirm execution of ''rawhide rebase'' with Red Hat Engineering Operations
    967 bytes (140 words) - 19:26, 2 June 2009
  • #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 [[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 [[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 maintainers
    857 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 Operations
    833 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 sp
    906 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 l
    917 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 bugs
    426 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://ttrink
    195 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 publication
    1 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, Israel
    648 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 (as
    1 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 Malbaz
    2 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'' war
    1 KB (154 words) - 23:41, 11 November 2008
  • Chemical Engineering and Technology (coal chemical industry) 08 th Class 1 Chemical Engineering and Technology
    939 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 than
    324 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 hour
    3 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 module
    3 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, the
    6 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 Resea
    1 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 l
    1 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, India
    2 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 docs
    535 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 artif
    3 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" Callaway
    2 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 fedora
    424 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 be
    667 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 Labor
    578 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.co
    572 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 Sch
    2 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, We
    2 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 provides
    2 KB (402 words) - 17:56, 3 November 2015
  • = Drupal Workshop at College of Engineering, Pune [CoEP]= College of Engineering, Pune
    1 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 Engineering
    1 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 power
    2 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 engineering
    3 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 sho
    2 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
View (previous 100 | ) (20 | 50 | 100 | 250 | 500)