Hotfix Branching Strategy

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



 At any one time, up to 3 developers could be developing hotfixes
addressing issues.    Whether it is one or multiple people working on
hotfixes, we always want to produce one hotfix.  Each hotfix is a
cumulative update since beginning of release.  Just about every hotfix
requires database upgrade.  Being that it is cumulative each developer
is dependent on the other.  Considering the requirements, what should
be a strategy to deal with this problem.?



Thanks in advance



[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux