#1 C2NET Configuration Management Plan

1.0
open
nobody
None
2015-09-25
2015-09-24
Carlos Coutinho
No

The C2NET project should create a Configuration Management Plan that will:
- Specify the practices to be held wrt the GIT configuration management (suggestion: https://opensourceprojects.eu/p/timbus/wiki/Configuration%20Management%20for%20the%20TIMBUS%20code/)
- Specify if we should have a single GIT repository, which means the developers have all C2NET code, or if we should separate the C2NET into multiple sub-projects with separate GIT repositories per C2NET component (DCF, CPL, COT, OPT), or even further, one GIT repository per tool. In this case, an interested developer needs only to clone the specific tool's GIT repository. This is a problem if you want ALL tools (multiple cloning), but I've already overcome this in another project using the Android repo tool.

Related

Ticket: #184
Ticket: #185

Discussion

  • cramirez
    cramirez
    2015-09-25

    This ticket responds to the discussion
    http://opensourceprojects.eu/p/c2net/discussion/general/thread/16954364/#37d4
    , isn't it?

    By the way It would be nice if you could provide an examples I mean you could create the branches and the projects in advance I mean we can take advantage of your expertise with git.

     
    Link