View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0002722Slicer4Core: Extensionspublic2012-11-02 10:012014-05-13 08:50
Reporterpinter Assigned Tojcfr  
PrioritynormalSeverityfeatureReproducibilityhave not tried
Status closedResolutionno change required 
Product Version 
Target VersionSlicer 4.4.0Fixed in VersionSlicer 4.4.0 
Summary0002722: Think about organization of Data/Modules directory on midas to accomodate extension relationship
Description

When browsing the NA-MIC/Slicer/Data/Modules folder, it's not clear to which extension a module belong.

See http://slicer.kitware.com/midas3/folder/310

// ---------------------
From Csaba:

Hi JC,

If I create a folder for every module we want to test, we'll end up adding a dozen folders.
Shouldn't I put those in an outer SlicerRT folder like
Data/Modules/SlicerRT/<NameOfYourModule>/Nightly/Testing/Baseline ?

I know the name of the folder is Module, but we would pollute the whole thing otherwise.

csaba

// ---------------------
For now, let's keep all of them at the same level. I will have to coordinate with the development of the release script allowing to version the Data tree. See [1]

I created a feature request to keep track of it. See http://www.na-mic.org/Bug/view.php?id=2722

Thanks
Jc

[1] http://slicer-devel.65872.n3.nabble.com/Versioning-of-test-data-tree-on-slicer-kitware-com-What-does-this-mean-for-you-tt4026608.html

TagsNo tags attached.

Relationships

related to 0002561 closedjcfr Create script allowing to "version" na-mic data tree 

Activities

jcfr

jcfr

2014-05-13 08:33

administrator   ~0011756

The tree hierarchy on the Midas server is here to only store the data associated with a module. I don't think there is no need to add extra information to link back to the extension. The wiki and extension manager provides this capability.
pinter

pinter

2014-05-13 08:50

developer   ~0011757

OK, fine by me. Closing the issue.

Issue History

Date Modified Username Field Change
2012-11-02 10:01 jcfr New Issue
2012-11-02 10:01 jcfr Status new => assigned
2012-11-02 10:01 jcfr Assigned To => jcfr
2012-11-02 10:02 jcfr Reporter jcfr => pinter
2012-11-02 10:02 jcfr Target Version => Slicer 4.3.0
2012-11-02 10:02 jcfr Description Updated
2013-08-30 20:40 jcfr Target Version Slicer 4.3.0 => Slicer 4.3.1
2013-09-04 13:04 jcfr Relationship added related to 0002561
2013-09-12 11:05 jcfr Target Version Slicer 4.3.1 => Slicer 4.3.2
2014-03-06 10:15 nicole Target Version Slicer 4.3.2 => Slicer 4.4.0
2014-05-13 08:33 jcfr Note Added: 0011756
2014-05-13 08:33 jcfr Status assigned => resolved
2014-05-13 08:33 jcfr Fixed in Version => Slicer 4.4.0
2014-05-13 08:33 jcfr Resolution open => no change required
2014-05-13 08:50 pinter Note Added: 0011757
2014-05-13 08:50 pinter Status resolved => closed