List view
Goal is to streamline repositories, i.e. redhat, debian, and alpine use a well organized structured tree that is reused for all three managers. * Reduce duplicates, e.g. (mirror of release and dist as for alpine, duplicates in pool vs archive) * Rethink the labeling of our releases. alpha is like debian-sid i.e. unstable, then we have stable and oldstable (mdsplus-previous) * manage versions uniformly: - either debian like three version/flavors (stable, oldstable, unstable) - or like for redhat and alpine: let the manager handle it (include all) - preferred * drop '-alpha' from package name and manage them as flavors (selected though the repo url). - one should not have both repos active anyway. * make the installation as intuitive as possible and allow to seemingly switch back and forth between alpha and stable, (uniform labels e.g. in start menu entries) * add --version argument to our applications returning the release string. * add minimum version info to all core shared libs. TdiShr,TreeShr,MdsShr,...
No due date•3/3 issues closedfrom issue #1847
No due date•1/1 issues closedfrom issue #1532 - Improve the usability and usage of "standard" xnci's for node metadata * creation of combobox nodes could be filled by description field in the parts structure for nodes in a python device *Additional infos in traversers/mdstcl, e.g. help text on device nodes *add information used by a generic gui *user defined xncis
No due date•1/1 issues closednaming coventions #1867 Possibly to a level where we can use tools like clang.
No due date•8/8 issues closed