Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » Community » Newbie corner » Ultimate++ i.r.t. Fossil SCM (POC of trying to integrate Fossil SCM with UMK.exe)
Ultimate++ i.r.t. Fossil SCM [message #53969] Mon, 18 May 2020 18:15 Go to previous message
alkema_jm is currently offline  alkema_jm
Messages: 25
Registered: November 2015
Promising Member
LS,

I look how I can change window in the next template. I think that these attributes are 'better' in relation to revision control systems:

index.php?t=getfile&id=6082&private=0

First I look to UMK.exe, specially the Makefile Smile

In revision control systems, a repository[1] is a data structure which stores metadata for a set of files or directory structure. Depending on whether the version control system in use is distributed (for instance, Git or Mercurial) or centralized (Subversion or Perforce, for example), the whole set of information in the repository may be duplicated on every user's system or may be maintained on a single server. Some of the metadata that a repository contains includes, among other things:
• A historical record of changes in the repository.
• A set of commit objects.
• A set of references to commit objects, called heads.
https://en.wikipedia.org/wiki/Repository_(version_control)

> This example is from 2009, probably did not matured well with time...

I will try to put a phase field in selection screen:
Development, Testing, Acceptance and Production (DTAP)[1][2] is a phased approach to software testing and deployment. The four letters in DTAP denote the following common steps:
1. The program or component is developed on a Development system. This development environment might have no testing capabilities.
2. Once the software developer thinks it is ready, the product is copied to a Test environment, to verify it works as expected. This test environment is supposedly standardized and in close alignment with the target environment.
3. If the test is successful, the product is copied to an Acceptance test environment. During the Acceptance test, the customer will test the product in this environment to verify whether it meets their expectations.
4. If the customer accepts the product, it is deployed to a Production environment, making it available to all users of the system.
https://en.wikipedia.org/wiki/Development,_testing,_acceptan ce_and_production

Greetings Jan Marco

Appendix A: Info from internet:

About Fossil SCM (Source Control Management)
Fossil is an open-source version control system: it's fully based on SQLite, and it comes from the same author of SQlite (Dr. R. Hipps).
More or less, Fossil is the same as the best known GIT or SVN; but Fossil is unbelively simple and lighweight compared to them.
That's not all: Fossil supports many features typical of web-based project management and bug-tracking tools such as Trac or RedMine.
See also http://www.gaia-gis.it/gaia-sins/about-fossil.html
 
Read Message
Read Message
Read Message
Read Message
Previous Topic: nightly builds broken?
Next Topic: Function key to Button
Goto Forum:
  


Current Time: Fri Mar 29 05:49:03 CET 2024

Total time taken to generate the page: 0.01486 seconds