Hyrum K. Wright

  • Citations Per Year
Learn More
Empirical studies that use software repository artifacts have become popular in the last decade due to the ready availability of open source project archives. In this paper, we survey empirical studies in the last three years of ICSE and FSE proceedings, and categorize these studies in terms of open source projects vs. proprietary source projects and the(More)
Wonsoo Kim, Owais Khan, Kien T. Truong, Soon-Hyeok Choi, Robert Grant, Hyrum K. Wright, Ketan Mandke, Robert C. Daniels, Robert W. Heath, Jr., Scott M. Nettles Wireless Networking and Communications Group (WNCG) Department of Electrical and Computer Engineering The University of Texas at Austin 1 University Station C0803, Austin, TX 78712-0240 Email: {wkim,(More)
As data rates supported by the physical layer increase, PHY and especially MAC overheads increasingly dominate the throughput achievable by wireless networks. A promising approach for reducing these overheads is to aggregate a number of frames together into a single transmission. The 802.11n standard uses such an approach for unicast frames. We present the(More)
In June 2008, the Subversion development team released Subversion 1.5.0. This release contained a number of new features, but arrived only after a long and difficult development, test and release cycle. This protracted process confused and frustrated both users and developers. In this paper, we discuss the events which led to this breakdown, how the release(More)
The release and deployment phase of the software development process is often overlooked as part of broader software engineering research. In this paper, we discuss early results from a set of multiple semi-structured interviews with practicing release engineers. Subjects for the interviews are drawn from a number of different commercial software(More)
Maintaining large code bases can be a challenging endeavour. As new libraries, APIs and standards are introduced, old code is migrated to use them. To provide as clean and succinct an interface as possible for developers, old APIs are ideally removed as new ones are introduced. In practice, this becomes difficult as automatically finding and transforming(More)
No matter the development process or methodology, a software product must ultimately be released to a user in a readily consumable form. Different software products, from desktop applications to web services, may require different release processes, but each process must produce an artifact which meets an expected level of quality, and is relatively(More)
To a user, unreleased software is nonexistent software, even in open source projects which make the source code readily accessible. Every project requires regular software releases to encourage adoption and attract developers. Different projects approach the task of releasing software in various ways [2], and many experience breakdowns in their release(More)
  • 1