Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/moosetechnology/famixtagging
A Famix extension to be able to tag entities.
https://github.com/moosetechnology/famixtagging
moose pharo smalltalk
Last synced: about 1 month ago
JSON representation
A Famix extension to be able to tag entities.
- Host: GitHub
- URL: https://github.com/moosetechnology/famixtagging
- Owner: moosetechnology
- License: mit
- Created: 2020-04-03T09:35:02.000Z (over 4 years ago)
- Default Branch: master
- Last Pushed: 2024-08-27T13:31:40.000Z (4 months ago)
- Last Synced: 2024-08-27T14:56:20.016Z (4 months ago)
- Topics: moose, pharo, smalltalk
- Language: Smalltalk
- Homepage:
- Size: 109 KB
- Stars: 0
- Watchers: 12
- Forks: 1
- Open Issues: 13
-
Metadata Files:
- Readme: README.md
- Contributing: CONTRIBUTING.md
- License: LICENSE
Awesome Lists containing this project
README
# Famix Tagging
A Famix extension to be able to tag entities.
- [Installation](#installation)
- [Documentation](#documentation)
- [Version management](#version-management)
- [Smalltalk versions compatibility](#smalltalk-versions-compatibility)
- [Contact](#contact)
## Installation
To install the project in your Pharo image execute:
```Smalltalk
Metacello new
githubUser: 'moosetechnology' project: 'FamixTagging' commitish: 'v1.x.x' path: 'src';
baseline: 'FamixTagging';
load
```
To add it to your baseline:
```Smalltalk
spec
baseline: 'FamixTagging'
with: [ spec repository: 'github://moosetechnology/FamixTagging:v1.x.x/src' ]
```
Note that you can replace the #v1.x.x by another branch such as #development or a tag such as #v1.0.0, #v1.? or #v1.1.?.
## Documentation
> TODO
## Version management
This project use semantic versioning to define the releases. This means that each stable release of the project will be assigned a version number of the form `vX.Y.Z`.
- **X** defines the major version number
- **Y** defines the minor version number
- **Z** defines the patch version number
When a release contains only bug fixes, the patch number increases. When the release contains new features that are backward compatible, the minor version increases. When the release contains breaking changes, the major version increases.
Thus, it should be safe to depend on a fixed major version and moving minor version of this project.
## Smalltalk versions compatibility
| Version | Compatible Pharo versions |
|------------- |--------------------------- |
| 1.x.x | Pharo 80 |
## Contact
If you have any questions or problems do not hesitate to open an issue or contact cyril (a) ferlicot.me