From Fedora Project Wiki

Results 91 – 111 of 2,556
Advanced search

Search in namespaces:

  • {{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
  • # Docs, Engineering, Design, Ambassadors regular linking # Make use of new Fedora Engineering Services Queue
    2 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 Engineering
    564 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 201009
    2 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 useful
    10 members (0 subcategories, 0 files) - 09:47, 6 August 2014
  • universities and Engineering schools. had mostly students from the Engineering schools asking a lot of
    3 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
View ( | ) (20 | 50 | 100 | 250 | 500)