Sometimes it can be a daunting task to keep track of what h as been done in between releases of an application. \; When multiple developers or even entirely different teams are trying to commit features and fixes on the same project\, records can be jumbled at best. Often\, spreadsheets or other story boards are filled in by hand to try and keep tabs on implemented changes\, but things can still sneak by without being documented or tasks that came in during the middle of a development cycl e can be lost. This presentation takes a look at one approach that can be utilized to automatically generate a list of changes which can then be u sed to populate future change requests and release notes or just to keep afloat in a sea of change.
DTEND;TZID=America/Phoenix:20141018T093000 DTSTAMP:20260713T152334Z DTSTART;TZID=America/Phoenix:20141018T083000 GEO:33.293070;-111.796620 LOCATION:Chandler - Gilbert Community College - IRN-230 ORGANIZER: SEQUENCE:0 STATUS:CONFIRMED SUMMARY:Sometimes it can be a daunting task to keep track of what has b een done in between releases of an application. \; When multiple deve lopers or even entirely different teams are trying to commit features and fixes on the same project\, records can be jumbled at best. Often\, spre adsheets or other story boards are filled in by hand to try and keep tabs on implemented changes\, but things can still sneak by without being doc umented or tasks that came in during the middle of a development cycle ca n be lost. This presentation takes a look at one approach that can be uti lized to automatically generate a list of changes which can then be used to populate future change requests and release notes or just to keep aflo at in a sea of change.
UID:a31d7d8e-24dd-404a-b880-ac880980beb8 END:VEVENT END:VCALENDAR