Search results

From PostgreSQL wiki

Jump to: navigation, search

Page title matches

  • ...a patch and you can use the new feature, you're already qualified to start reviewing it. ...e example of the output a thorough review might produce. Reviews for other patches might, of course, contain different sections or for that matter, look com
    Relevance: 6.2% - 6 KB (964 words) - 18:26, 21 December 2016
  • ...е внимание на насмешливую [[Media:11_eggyknap-patch-review.pdf | презентацию]] Джошуа Толле (Josh Tolley), и б ...требуемые навыки: использование команд ''patch'', ''configure'' и ''make'', вывод ошибок в лог) ==
    Relevance: 4.9% - 10 KB (116 words) - 10:59, 9 September 2015
  • {{Languages|Reviewing a Patch}} ...ような人材が求められているかは、[[Media:11_eggyknap-patch-review.pdf|Josh Tolley 氏のプレゼンテーション]]に、冗談めかしな
    Relevance: 4.9% - 6 KB (97 words) - 07:47, 4 October 2010
  • {{Languages|Reviewing a Patch}} ...s, tu ayuda va a ser bienvenida. Ver también la [[Media:11_eggyknap-patch-review.pdf|presentación de Josh Tolley]] para ver una descripción irónica, pero
    Relevance: 4.9% - 6 KB (963 words) - 00:53, 2 October 2010

Page text matches

  • ...log?) that the CF is beginning on the date, and that they should get their patches registered/submitted. * Do a patch sweep (see below).
    Relevance: 10.0% - 10 KB (1,774 words) - 20:37, 2 August 2016
  • # to make commitfests easier, more comprehensible and more fun for reviewers ... patches (some automated testing is required to make things easier for the reviewers, but we could do more)
    Relevance: 9.7% - 13 KB (2,200 words) - 18:14, 12 July 2013
  • ...a patch and you can use the new feature, you're already qualified to start reviewing it. ...e example of the output a thorough review might produce. Reviews for other patches might, of course, contain different sections or for that matter, look com
    Relevance: 9.6% - 6 KB (964 words) - 18:26, 21 December 2016
  • == Pending patches == {{patch|49C74FE8.6030601@ak.jp.nec.com|Security Enhanced PostgreSQL|KaiGai Kohei}}
    Relevance: 9.5% - 11 KB (1,563 words) - 14:06, 14 July 2009
  • {{CommitFestSectionOld|Pending patches}} {{CommitFestSectionOld|Committed patches}}
    Relevance: 9.4% - 13 KB (1,769 words) - 21:07, 18 June 2009
  • == Initial patch design == ...tgresql.org/pgsql-hackers/ pgsql-hackers] list before being submitted as a patch.
    Relevance: 9.3% - 16 KB (2,616 words) - 22:30, 22 July 2013
  • == Pending patches == == Committed Patches ==
    Relevance: 9.1% - 20 KB (2,766 words) - 21:02, 18 June 2009
  • ...e final review and commit. The CF page is used to keep track of submitted patches and their status, to help manage the ...ers are able to participate at normal levels; such a phase may be called a ReviewFest (RF).
    Relevance: 8.7% - 2 KB (395 words) - 02:38, 14 November 2013
  • == Committed patches == ...co.jp|Common Table Expressions|Yoshiyuki Asaba|status=Committed 2008-10-04|reviewers=Jeff Davis}}
    Relevance: 8.3% - 47 KB (6,762 words) - 20:34, 18 June 2009
  • * Heavier filtering for patches in last CF (Andres Freund) * How can CFs/development process put more focus on long pending patches (Andres Freund, Jonathan Katz)
    Relevance: 7.4% - 33 KB (5,940 words) - 06:29, 4 September 2018
  • * Review the progress of the 11.0 schedule, and formulate plans to address any issue * 11.0 Release Review
    Relevance: 6.7% - 23 KB (4,010 words) - 13:38, 6 February 2018
  • == What's a Round Robin Reviewer (RRR)? == ...e assigned random patches (usually according to their level of ability) to review during a commitfest by the [[Running a CommitFest|CommitFest Manager]]. Th
    Relevance: 6.4% - 4 KB (606 words) - 19:50, 26 June 2012
  • ...he patch review process, add them to the RRReviewers pool, and review some patches. * have the latest Pg & the patches on a USB key (because there's usually one person who forgets to get them)
    Relevance: 6.3% - 4 KB (658 words) - 22:00, 19 May 2012
  • * [[Submitting a Patch]] * [[Reviewing a Patch]]
    Relevance: 5.9% - 3 KB (345 words) - 11:30, 21 June 2018
  • This first CommitFest relied on Bruce's patch queue as its primary input: * [[Todo:PatchStatus|Patch Status Overview]]
    Relevance: 5.9% - 6 KB (792 words) - 21:07, 18 June 2009
  • * Introduction to Hacking PostgreSQL - With lots of code review! https://linux.org.au/conf/2007/att_data/Miniconfs(2f)PostgreSQL/attachment tools/make_diff has tools to create patch diff files that can be applied to the distribution. This produces context d
    Relevance: 5.9% - 46 KB (7,596 words) - 13:16, 30 August 2018
  • * [[Submitting a Patch]] * [[Reviewing a Patch]]
    Relevance: 5.3% - 2 KB (240 words) - 13:05, 9 November 2010
  • * [[Submitting a Patch]] * [[Reviewing a Patch]]
    Relevance: 5.3% - 2 KB (251 words) - 00:39, 25 November 2016
  • * Review the progress of the 9.6 schedule, and formulate plans to address any issues ... be more strict with commitfest dates, and if so, how do we remain fair to patch submitters?
    Relevance: 5.2% - 34 KB (5,312 words) - 23:04, 1 February 2016
  • * Review the progress of the 10.0 schedule, and formulate plans to address any issue |Reviewing unreviewed patches
    Relevance: 5.2% - 16 KB (2,652 words) - 04:00, 2 December 2016

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)

Views
Personal tools