I don't know of a why of propagating comments and work items to a merge changeset. (Consider that a merge operation might comprise many changesets from "Mainline.") The person doing the merge operation should generally be adding a comment for the merge changeset that indicates what is being merged (i.e. up to a label, up to a changeset #, the set of changesets that were cherry-picked, etc.)
The easiest way to tell if a mainline changeset has been merged to release is if it is no longer in the merge candidate list for the release branch. Scott Colestock On 12/13/07, Patrick Green <[EMAIL PROTECTED]> wrote: > > We currently have a Mainline which is branched to Release. When I merge > a changeset from Mainline to release the information from the original > changeset(Comments, WorkItems etc) are not shown or referenced in the new > changeset in the Release Branch. > > > > I would like to be able to generate ReleaseNotes by doing a > changeset/workitem query on the Release branch, but because the work was > carried out in Mainline and merged selectively to Release, and the > information doesn't seem to come across, I cant get this info. > > > > Does anyone know if this can be done? Or of any alternative to know if the > status of the Mainline Changeset would show that it was merged to release? > > > > Regards > > > > Patrick Green > > > OzTFS.com - to unsubscribe from this list, send a message back to the > list with 'unsubscribe' as the subject. View the web archives at > http://www.mail-archive.com/[email protected]/ > Powered by mailenable.com, supported by www.readify.net -- scott colestock trace ventures, LLC 612.559.0580 OzTFS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. View the web archives at http://www.mail-archive.com/[email protected]/ Powered by mailenable.com, supported by www.readify.net
