Abstract: Technologies are disclosed herein for automated software release lifecycle management. In particular, a software release management network service is disclosed that provides functionality for allowing a software developer to automate aspects of a software release pipeline. A software release pipeline can have multiple stages, each of which can have multiple actions. The actions can include internal actions that utilize network services internal to a service provider network. The actions can also include external actions that utilize network services that are external to a service provider network. The internal and external actions can perform various release-related functions, such as obtaining source code, building the source code, deploying built program code, and for performing tests. Stage gates and/or action gates can also be defined for conditional execution of the next stage or action in a software release pipeline, respectively. A gate bypass can also be specified to override stage or action gates.

Abstract: A light pointer is selectively activated to direct a light beam onto an interactive display surface, forming a pattern of light that is detected by a light sensor disposed within an interactive display table. The waveband of the light produced by the light pointer is selected to correspond to a waveband to which the light sensor responds, enabling the light sensor to detect the position of the pattern on the interactive display surface, as well as characteristics that enable the location and orientation of the light pointer to be determined. Specifically, the shape and size of the pattern, and the intensity of light forming the pattern are detected by the light sensor and are processed to determine the orientation of the light pointer and its distance from the interactive display surface. The pattern may comprise various shapes, such as circles, arrows, and crosshairs.

Abstract: A first exemplary method implementation for designing an application programming interface (API) includes: preparing multiple code samples for a core scenario, each respective code sample of the multiple code samples corresponding to a respective programming language of multiple programming languages; and deriving the API from the core scenario responsive to the multiple code samples. A second exemplary method for designing an API includes: selecting a core scenario for a feature area; writing at least one code sample for the core scenario; and deriving an API for the core scenario responsive to the at least one code sample. A third exemplary method for designing an API includes: deriving an API for a scenario responsive to at least one code sample written with regard to the scenario; performing one or more usability studies on the API utilizing multiple developers; and revising the API based on the one or more usability studies.

Abstract: Architecture for developing an application. The architecture provides an entry point to commonly used classes of an application development framework. A developer begins a project which predefines a set of collection classes. An exposer component includes an identifier component and a compiler for generating accessors to the collected classes. The identifier uses an attribute on a collection class which a compiler dynamically extracts in order to generate accessors to the desired collected classes and compiles the generated collection classes for use in the namespace.