-
Notifications
You must be signed in to change notification settings - Fork 95
Configuration Management Plan
This is the list of where artifacts in the project are stored and maintained. It was especially needed when moving from the old (tigris.org) and the new (Github) location. It might be confusing since it describes where stuff is located based on where it came from, on Tigris, the old site.
Store everything on github. Gerrithub is used for code reviews.
Central parts in the argouml repository. This is what was in the argouml.tigris.org project.
Additional features in their own git repository in the argouml-tigris-org organization. This was in other argouml-whatever.tigris.org projects.
Additional features include:
- Quick Guide and User Manual are in the argouml-documentation repository.
- Support for programming languages.
- Localization and i18n support.
List of repositories in the manifest repository. The format is a repo input file.
Changes are discussed, reviewed and verified at gerrithub before submit to the master branch. Verification is done by a host that is run by Linus Tolke. For the time being, submit is done by Linus Tolke.
Any pull requests on Github will be imported to gerrithub, verified and reviewed there.
Wiki in the argouml-tigris-org/argouml project (this wiki) referenced from README.md at the top of each project. This is the go-to location for developer information. It contains links to instructions and notes.
Instructions in web-page form are available in the Github pages of the organization https://argouml-tigris-org.github.io/. Changes to the web-pages are reviewed and discussed as Pull requests on github for the argouml-tigris-org.github.io repository.
We have nothing except the very old stuff in the Github Pages of the organization such as Tour. The very old stuff comes from the web pages of the argouml.tigris.org project. The www.argouml-users.net site with Forum is no longer working.
There are some artifacts that the build rely on, old jar files that may or may not be possible to recreate. They are published from a maven2 repository published at https://argouml-tigris-org.github.io/tigris/maven2 from the argouml-tigris-org.github.io repository. The profiles are published at https://argouml-tigris-org.github.io/profiles from the argouml-tigris-org.github.io. http://argouml.org is pointing to https://argouml-tigris-org.github.io/ so old references to the profiles using http://argouml.org/profiles should work. Alas we discovered a problem when redirecting from http to https so old versions of argouml will not handle this correctly.
New issues are created as issues per repository on github. All old issues from argouml.tigris.org project are archived in the GITHUB_IMPORT release in argouml repository.
We have no new mailing lists. Instead Discussions is enabled in the argouml repo and a Dev Teams in the argouml-tigris-org organization on Github.
Rationale: The old mailing lists at Tigris cannot be easily moved and is probably mostly stale mail addresses.
Snapshots are published to Maven repository. Linus Tolke has the sonatype account and is running the host that does this. Maven sites are published in Github Pages at https://argouml-tigris-org.github.io/ see the index. Scripts for this are in the argouml-gen repository. This replaces the old build server scripts storing information in the argouml-stats.tigris.org project.
The following things are still unclear:
- Release process.
- Where to publish maven versioned artifacts.
- If we should publish all old releases (from argouml-downloads.tigris.org).