noun: CollabNet
quote
CollabNet founder and CTO Brian Behlendorf is the founder and earliest major developer of the Apache Software Foundation, known as the father of Apache, the leader of open source projects and methods. HP, Intel, Sun strategic investment partner, the main investor and promoter of the open source project SubVersion. More than 800,000 global users, 15,000 projects, hundreds of organizations, dozens of countries.
CollabNet now has more than 1.5 million users, more than 500 companies, and 20,000 software projects! CollabNet has now helped hundreds of customers and more than 1.5 million users reduce costs and risks, increase efficiency and foster innovation in software projects. CollabNet Corporation is the owner of Subversion, which provides a new standard for software configuration management for globally distributed teams. And CollabNet is the main sponsor of the Subversion open source project. The amazing thing is that CollabNet already offers a live experience where you can actually experience two-way engineering. At present, CollabNet has started Subversion5 and successfully completed the migration.
CollabNet main products
Subversion Subversion is the new standard for version control and software configuration management (SCM) for globally distributed organizations that need to share source code everywhere. Ease of use and out-of-the-box support for remote teams make Subversion the best solution for global projects, compared to legacy tools that are inadequate for distributed teams and too expensive to run. CollabNet Subversion is an enterprise-ready Subversion distribution that includes certified binaries, platform-specific installers, certified plugins for other tools, and enterprise-ready add-ons. Subversion features: Certified binaries on enterprise platforms, platform-specific installers, native support for distributed teams, latest SCM efficient installation and repository management, out-of-the-box integrations, centralized source code repository, easy Access to remote developers, scalable web-based architecture, secure web-based access. TeamForge TeamForge (formerly CollabNet TeamForge) is an integrated suite of web-based SCM, issue tracking, project management, and collaboration tools that allow teams to build large-scale software. With centralized management of users, projects, processes and assets, CollabNet TeamForge can significantly reduce costs, increase productivity and improve project visibility. CollabNet TeamForge can be deployed on-site or as a secure on-demand product, further reducing infrastructure costs. A trial version for 3 users is available. TeamForge Capabilities: Application Lifecycle Management (ALM), Common User and Project Management, Software Configuration Management (SCM), Change Management, Project Management, Integrated Collaboration Tools, Open Web Services API CollabNet Software as a Service (SaaS). CUBiT CUBiT enables distributed development teams to quickly access a large number of on-demand build and test services. Teams can manage their own repository of continuous build software stack configuration files, quickly configure on available machines, and version control configuration files throughout development, build, and QA testing. CUBiT Significant cost and time savings: By centralizing development tools, servers, and management infrastructure, server provisioning for coding, build, and test cycles is 10x faster, saving teams up to 90% in hard costs. CUBiT Capabilities: Self-Service via Browser or IDE, Dynamic Development Distribution, Build and Test Services, Profile Repository: Centralized Management of Build and Test Software Stacks, Build Repository: Centralized Management and Reuse of Build Components, Governance and Reporting: Cross- Visibility and control of a large number of computing resources, projects, configuration files and build artifacts around the world.
nounbackport : _
quote
Backporting is the act of applying a patch of software to a version older than the version to which the patch corresponds. This is part of the maintenance step in the software development process. The simplest and probably the most common example is a patch for a vulnerability in a piece of software. A new version of a certain software finds a vulnerability, which can be repaired by patching the source code; but the old version of this software cannot be repaired by the same patch because the source code is different. Code patched.
Changes made to an aspect of the software may be as simple as changing a few lines of code, or as complex as requiring changes to a large number of source code files. If the changes are complex, then the backport behavior is not worth it, unless the old version of the software is still more popular than the newer version.
For closed source software, only people in the core development team can backport. For open source software, backports are sometimes created by publishers, who then upstream (ie, send back to the core development team) changes to the source code.
Example
quote
The father of Linux praised the advantages of Backport technology for integrating the system.
Recently , Linus Torvalds, the father of the Linux operating system, said that after his measurement, the practice of Backporting (porting) some features of the new version of the Linux kernel to the old version of the Linux kernel is an excellent feature of the two. integration is commendable.
Earlier, Juergen Geck, CTO of German Linux giant SuSe, criticized at the Real World Linux conference that Red Hat's decision to backport new features from the 2.6 kernel to the 2.4 kernel was wrong because it would affect the open source operating system. standardization. Geck is trying to convey the tone: avoid implementing any behavior that might break the standards of open source operating systems. Geck's remarks caused widespread debate in the industry.
When interviewed by the media and asked about his views on the issue, Torvalds said: "Every company has its own view and position on the 'advanced version' of the software, as long as they think it is beneficial and important to the customer. Yes, it makes sense. From that standpoint, I think backports are actually a good idea."
Miguel de Icaza, Novell's deputy manager, also defended Red Hat's backport measures. He explained that developers often bundle features at the request of customers, but don't ship them in the official kernel. For example, Red Hat's 2.5 X NPTL (Native Posix Threading Library) backport to the 2.4 kernel is a successful example, and now the stability and scalability of the 2.4 kernel have been widely recognized. In addition, many Linux companies have expressed different opinions, with mixed opinions.
Although Torvalds, the father of Linux, agreed with Red Hat's backport work, he also warned that the development of the kernel after the backport may not be long-term, because of the lack of "consistency" (it is difficult to ensure that different Source Trees can be properly maintained), which makes long-term problems. become prominent. "There are gains and losses, but so far I think it's a positive development."
Torvalds acknowledged the benefits of backport, but he still encouraged users to use an improved version of the Linux kernel.