sorry, the table below looks terrible :(
On May 29, 2:26 pm, mart <[email protected]> wrote: > Hi, > > On some days, things move really fast, which is a great thing!, > but... also backtracking (going back and taking time go through them) > isn't so easy... Does anyone have something to keep track of trunk > changes when, for example, Massimo submits multiple changes/features > in one day? > > Last Thusrday, I think there were at least 3 of these new features, > and I only see 2. I remember thinking that are somehow related (kind > of - i think). Anyways, if someone already has something set up (a > table or something) with description, change number, paths, etc...), > would be nice to track these things... > > Just thought I'd ask :) Sometimes syncing the files affected by a > change we want to look at is easier to manage than grabbing everything > - at least, that's how I like to manage the ins and outs. But no > worry, I will come up with something if none already exists. > > anyways, was think something simple that would link trunk to release: > > TRUNK | RELEASE > ___________________________|___________________ > title | title > ___________________________|___________________ > submitted to 'REALEASE': T/F | > ___________________________|___________________ > submission number | submission number > ___________________________|____________________ > affected files | affected files > ___________________________|___________________ > description | > description > ___________________________|____________________ > blablabla | blablabla > > Thanks, > Mart :)
