Thanks to a github security alert, I find out we have a fork of an
official groovy repo[1] in our org. It is terribly outdated and unused
for over 8 years[2].
Are there any objections to archiving such repositories? The repo will
remain readable but it would clearly indicate it is obsolete and it will
not be searched for vulnerabilities, noone is interested in.
[1] https://github.com/jenkinsci/groovy
[2]
https://github.com/jenkinsci/jenkins/commit/b8673633da9aa4f0632a4a9e1fc26729cfca0f9e
Thanks!
--
oliver
--
You received this message because you are subscribed to the Google Groups "Jenkins
Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/3ce4514d-3464-6003-2f96-7125155c18eb%40gmail.com.
