“Mapping the Apache Software Foundation” / An Antic Disposition
Many units on the business side of the education industry directly employ a larger software staff than all the electricians, HVAC mechanics and plumbers combined. Software staff must continually “maintain” enterprise software to keep information flow steady, secure and interoperable with other platforms.
Software upgrade versioning is an essential part of producing that result. At a fine-grained level, revision control is used for keeping track of incrementally different versions of information, whether or not this information is computer software. Software action is tracked using two different software versioning schemes—internal version number that may be incremented many times in a single day, such as a revision control number, and a release version that typically changes far less often, such as semantic versioning or a project code name.
Because the Apache catalog is open source, stakeholders can enter and leave the community at any time. We encourage software experts with sensitivity to cost constraints to become involved in the Apache consensus product development process. We always encourage direct communication:
Getting Involved with Apache Subversion and the Community
We keep all software consensus products on the standing agenda of our Information & Communications (ICT) technology teleconferences. See our CALENDAR for the next online meeting; open to everyone.
Apache Software Foundation 2007
