Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Method to get alerted on relevant team development activities

IP.com Disclosure Number: IPCOM000200632D
Publication Date: 2010-Oct-21
Document File: 2 page(s) / 24K

Publishing Venue

The IP.com Prior Art Database

Abstract

This article describes a method to get alerted on relevant team development activities

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 54% of the total text.

Page 01 of 2

Method to get alerted on relevant team development activities

Disclosed is a process to generate instant alerts based on local modifications made by a user (either committed or not committed) and current commit activities of other users on respective local repositories. The disclosed process enables a user receive immediate notification of what other users have been working on that could cause a problem involving merge, conflict, or duplication problem in the future.

Currently some development collaboration software offerings utilize concepts of delivery and commit. Commit enables developers to check code into a personal repository, while delivery enables developers to flow the code into the main stream. The concepts enable developers to check in interim code changes into personal repositories providing benefits including enabling code storage on machines of more than the developer and reading the code and executing private builds against the stored files.

However, committing code into a personal repository without delivering the code raises an issue for developers, because a developer may create code which impacts the code of another developer without realization until well after the code is delivered to the main stream. Resolving a duplicate code problem includes merging code (resolving conflicts) or discarding

portions of code. The options can be inefficient at best and possibly quite wasteful.

The disclosed process enables a system to generate instant alerts based on local modifications (either committed or not committed) of a user and current commit activities of other users on

  ersonal repositories. Use of the disclosed process typically provides an effective means for developers to receive notification; because developers tend to focus more on code than defects or other ways to track work items. Whenever a user changes a file locally, the system determines when anyone else has changed the same file in a personal repository. When a determination is made that a user has changed the same file in a personal repository the system will alert the user about whoever has also changed the same files/methods in a local tree, or committed or delivered the changes. The disclosed process also provides a capability to display corresponding task/defect work item identifiers so the user can easily understand what the other user is trying to accomplish. The notified user has an opportunity to contact the owner of the code or accept the changes, using a chat facility or other instant messagin...