That (archiving) sounds like a good option to me
Regards
Carsten
Stefan Seifert wrote
i think as well we should not delete the git repository.
adding a badge makes sense.
additionally in github there is an option to "archive" a repository [1] - it's then set
to readonly for everyone and github displays a label "Archived" in the repository list
and a warning message if anything from the repo itself is displayed. if need arise it can be
un-archived as well. i suppose this can only be done by infra.
stefan
[1] https://help.github.com/articles/archiving-a-github-repository/
-----Original Message-----
From: Carsten Ziegeler [mailto:cziege...@apache.org]
Sent: Tuesday, January 15, 2019 10:49 AM
To: dev@sling.apache.org
Subject: How to we handle deprecated modules?
Hi
with svn we moved deprecated/obsolete modules to the attic
How do we handle this now with git?
The thread at [1] seems to suggest batches.
I personally don't like having git repositories around which should not
be used. On the other hand, removing the git repo has some disadvantages
as well.
WDYT?
[1]
https://lists.apache.org/thread.html/63719253a3f3659e4e24009e2e8e212a1c9bb7
7fddc696b7720000d9@%3Cdev.sling.apache.org%3E
Regards
Carsten
--
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org
--
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org
