You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 2, 2024. It is now read-only.
Since returning to Skyscanner I've continued bare-minimum maintenance of this repo, which has been required as Skyscanner transitioned off Drone to GitHub Actions. As that transition is drawing to an end, we will have no need for it and will become unable to test it.
The situation is:
development on the repo is effectively at a standstill already - it's mature enough.
the image seems to get 300-400 pulls per day, last I looked. This is not a big number.
I don't think there's any natural successor to take over ownership of this repo, as most changes over the years have been done by myself or Skyscanner colleagues, and there's been almost no work done on it in the last few years.
it serves an increasingly niche use case that the core Testcontainers team shouldn't be on the hook to support.
Therefore I'd like to propose that we archive this repository in the near future.
From then on, I think:
for any teams still using it, they'd still be free to fork the repo and continue their own maintenance of it (in their own org or privately)
we could leave published images as they are on quay.io (not delete them), but only provide reasonable efforts to keep them there (e.g. if quay.io starts charging or expiring etc, we'd let the images go).
Please let me know if you have any thoughts or alternative ideas!
The text was updated successfully, but these errors were encountered:
cc @kiview @bsideup @eddumelendez 👋
Since returning to Skyscanner I've continued bare-minimum maintenance of this repo, which has been required as Skyscanner transitioned off Drone to GitHub Actions. As that transition is drawing to an end, we will have no need for it and will become unable to test it.
The situation is:
Therefore I'd like to propose that we archive this repository in the near future.
From then on, I think:
Please let me know if you have any thoughts or alternative ideas!
The text was updated successfully, but these errors were encountered: