devel:tools:scm Software configuration management to quote wikipedia: Software Configuration Management (SCM) is part of configuration management (CM). Roger Pressman (in his book) Software Engineering: A Practitioner's Approach, says that software configuration management (SCM) is a "set of activities designed to control change by identifying the work products that are likely to change, establishing relationships among them, defining mechanisms for managing different versions of these work products, controlling the changes imposed, and auditing and reporting on the changes made." In other words, SCM is a methodology to control and manage a software development project. SCM concerns itself with answering the question: somebody did something, how can one reproduce it? Often the problem involves not reproducing "it" identically, but with controlled, incremental changes. Answering the question will thus become a matter of comparing different results and of analysing their differences. Traditional CM typically focused on controlled creation of relatively simple products. Nowadays, implementers of SCM face the challenge of dealing with relatively minor increments under their own control, in the context of the complex system being developed. https://download.opensuse.org/repositories/devel:/tools:/scm/openSUSE_Tumbleweed/ openSUSE:Factory The next openSUSE distribution Any user who wishes to have the newest packages that include, but are not limited to, the Linux kernel, SAMBA, git, desktops, office applications and many other packages, will want Tumbleweed. Tumbleweed appeals to Power Users, Software Developers and openSUSE Contributors. If you require the latest software stacks and Integrated Development Environment or need a stable platform closest to bleeding edge Linux, Tumbleweed is the best choice for you. Staging dashboard is located at: https://build.opensuse.org/staging_workflows/openSUSE:Factory List of known devel projects: https://build.opensuse.org/package/view_file/openSUSE:Factory:Staging/dashboard/devel_projects Have a look at http://en.opensuse.org/Portal:Factory for more details. https://download.opensuse.org/tumbleweed/repo/oss/ openSUSE:Tumbleweed Tumbleweed Tumbleweed is the openSUSE Rolling Release This OBS Project represents the content of the currently published snapshot. The newer repository for next publish can be found in openSUSE:Factory standard repository. https://download.opensuse.org/repositories/openSUSE:/Tumbleweed/standard/ openSUSE:Tumbleweed Tumbleweed Tumbleweed is the openSUSE Rolling Release This OBS Project represents the content of the currently published snapshot. The newer repository for next publish can be found in openSUSE:Factory standard repository. https://download.opensuse.org/tumbleweed/repo/oss/ openSUSE:Factory The next openSUSE distribution Any user who wishes to have the newest packages that include, but are not limited to, the Linux kernel, SAMBA, git, desktops, office applications and many other packages, will want Tumbleweed. Tumbleweed appeals to Power Users, Software Developers and openSUSE Contributors. If you require the latest software stacks and Integrated Development Environment or need a stable platform closest to bleeding edge Linux, Tumbleweed is the best choice for you. Staging dashboard is located at: https://build.opensuse.org/staging_workflows/openSUSE:Factory List of known devel projects: https://build.opensuse.org/package/view_file/openSUSE:Factory:Staging/dashboard/devel_projects Have a look at http://en.opensuse.org/Portal:Factory for more details. https://download.opensuse.org/repositories/openSUSE:/Factory/ports/ mr Version control repository manager The mr(1) command can checkout, update, or perform other actions on a set of repositories as if they were one combined respository. It supports any combination of git, svn, mercurial, bzr, darcs, cvs, vcsh, fossil, and veracity repositories. It supports extensions which in turn can use more version control systems. It is configurable via shell scripting. Some examples of things it can do include: * Update a repository no more frequently than once every twelve hours. * Run an arbitrary command before committing to a repository. * When updating a git repository, pull from two different upstreams and merge the two together. * Run several repository updates in parallel, greatly speeding up the update process. * Remember actions that failed due to a laptop being offline, so they can be retried when it comes back online. This package also includes the webcheckout(1) command.