Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Description

None

Environment

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:

David Crossley January 6, 2020 at 6:27 AM

Done. The old repository is now "archived read-only" as explained in my comments above and at FOLIO-2251.

Peter Murray December 20, 2019 at 4:02 PM

A new security advisory popped up for the old `mod-kb-ebsco` code.

David Crossley September 11, 2019 at 1:09 AM

I added the new ticket FOLIO-2251 for the Core Platform Team to rename and archive, as explained in my previous comment above.

However, this current Sprint 72 is very busy, so it may need to wait.

Carole Godfrey September 10, 2019 at 1:22 PM
Edited

Sure I think that makes sense and
Would this be a good reference https://medium.com/maintainer-io/how-to-deprecate-a-repository-on-github-8f0ceb9155e for steps we should take to do this?
Also found this reference on archiving the repository
https://github.blog/2017-11-08-archiving-repositories/

Peter Murray September 10, 2019 at 1:09 PM
Edited

: Is it okay if we mark this Ruby-based project as Deprecated in GitHub? It'll stop the security alerts in addition to signalling to others that the code is no longer used

and , what do you guys think?

Something went wrong on our end

If this keeps happening, share this information with your admin, who should contact support.

Hash 1GILD5Q Trace 244d33f1b30e45eb9ab26aefbb00c2e7

Details

Assignee

Unassigned

Reporter

Carole Godfrey

Priority

P3

Story Points

3

Development Team

Spitfire

Fix versions

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

TestRail: Cases
TestRail: Runs

Flag notifications