On 06/12/12 09:34 -0600, zodman wrote: > I have this question when i seen the mercurial repos on hg.tryton.org > > How manage tryton with a lot of repos? and how maintaing for bug hunting. > > For example i understand if i found a bug on tryton 2.4 and report it. > > You apply the fix on tryton 2.4 but if the bug exist on 2.6 go to repo > 2.6 and fix it and then go to 2.8 repo and fix it ? > > You apply 3 times the fixes for all versions. > > ¿How manage it ? > > this the worst case... but the regular case you apply 2 times the fix ?¿ > > And how manage the bugs/errors on 2.6 not reapeat on branch 2.8 ?¿
Ok, I will explain how I manage the backport of the fixes. First, we fix on the higher branch where the issue exists (most of the time it is trunk). Once the patch if pushed, I decide if it needs to be backported or not. The decision is based on the importance of the bug and also if it doesn't infringe the series rules (no migration and no API changes). If it is decided to be backported than I keep it in a personal queue for at least 1 week (delay to be sure the fix doesn't introduce bugs). (I try) once a week to process the queue by using mercurial transplant [1]. [1] http://mercurial.selenic.com/wiki/TransplantExtension -- Cédric Krier B2CK SPRL Rue de Rotterdam, 4 4000 Liège Belgium Tel: +32 472 54 46 59 Email/Jabber: [email protected] Website: http://www.b2ck.com/
pgp1GcIiPqw0Y.pgp
Description: PGP signature
