Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • fusiondirectory fusiondirectory
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 33
    • Issues 33
    • List
    • Boards
    • Service Desk
    • Milestones
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • fusiondirectoryfusiondirectory
  • fusiondirectoryfusiondirectory
  • Issues
  • #6371
Closed
Open
Issue created Sep 03, 2024 by dockx thibault@tdockxDeveloper

[Dev Core Manual] - Migration - Explain how obsolete work in the dev manual and update our logic

[Migration] - Explain how obsolete work in the dev manual

The attribute must gain the value OBSOLETE and the attribute must be set as "may" within its objectClass.

This is a key factor for migration tool to work properly.

~~https://fusiondirectory-developer-documentation.readthedocs.io/en/1.4/fusiondirectory/release/releasepolicy.html

We also have to update the documentation for release policy, explaining the removal of obsolete tags between major release.~~

Note : Decision has been made to create an internal documentation about CORE development and guidelines. This issue is to be integrated into that logic and not within public dev-manual

Edited Feb 18, 2025 by dockx thibault
Assignee
Assign to
Time tracking