just quick info for u =) http://docs.google.com/fileview?id=0B7E-_t3x8o0TZWQ5ODdkZDEtZTRlNy00MmMxLWI5MzEtMjE0OTE3ZmNiNTk2&hl=en
-- Vitaliy Kulikov <[email protected]> Complexity Simplified. On Wed, 2010-04-28 at 21:03 +0300, Charlie Poole wrote: > Hi All, > > Like a lot of other projects I see on Launchpad, mine has a trunk > branch that is the development > focus and mulitple release branches. At any given time, one of the > release branches has milestones > in progress, while the others are usually stable. I'd like to know how > folks typically manage this > situation without duplicating updates. > > Do you push tested new code to trunk _and_ to the branch being worked > on immediately? > Do you push to trunk but then merge into the branch periodically? > Do you wait unitl you are ready to release to merge the latest trunk > code into the release > branch? > Do you sometimes merge only selected commits from trunk to the release? > > I know the answer to all of these is probably "yes" for at least some > project, so I'm > looking for a judgement of what seems to be typical and/or best practice. > > TIA, > Charlie > > _______________________________________________ > Mailing list: https://launchpad.net/~launchpad-users > Post to : [email protected] > Unsubscribe : https://launchpad.net/~launchpad-users > More help : https://help.launchpad.net/ListHelp
<<attachment: face-smile.png>>
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Mailing list: https://launchpad.net/~launchpad-users Post to : [email protected] Unsubscribe : https://launchpad.net/~launchpad-users More help : https://help.launchpad.net/ListHelp
