25 inactive repos to be archived

56 views
Skip to first unread message

Andrew Burden

unread,
Jul 4, 2024, 9:34:59 AM7/4/24
to kubevirt-dev
Hey folks,

Over the many years, the KubeVirt project has accumulated a number of repos that have fallen into inactivity. To improve the tooling and monitoring of the project we think it's time to put these repos out to pasture and archive them.

Please have a look over the list and, if you disagree with any of these being archived, be sure to comment on the tracking issue:
https://github.com/kubevirt/community/issues/239

Please note any dissent before 25 July (3 weeks).


Thanks!
Andrew

[1] Well, 3 months ago. Any changes since then will not be reflected.

Or Shoval

unread,
Jul 4, 2024, 9:38:45 AM7/4/24
to Andrew Burden, kubevirt-dev
On Thu, Jul 4, 2024 at 4:35 PM Andrew Burden <abu...@redhat.com> wrote:
Hey folks,

Over the many years, the KubeVirt project has accumulated a number of repos that have fallen into inactivity. To improve the tooling and monitoring of the project we think it's time to put these repos out to pasture and archive them.

Please have a look over the list and, if you disagree with any of these being archived, be sure to comment on the tracking issue:
https://github.com/kubevirt/community/issues/239

Please note any dissent before 25 July (3 weeks).

From my investigation[1] the repos, in order of longest time since they were updated are:
2 Years:
https://github.com/kubevirt/qe-tools

Hi,
This one is used atm by kubevirt directly (to create Polarion report IIRC)
go.mod: kubevirt.io/qe-tools v0.1.8
Thanks
 
--
You received this message because you are subscribed to the Google Groups "kubevirt-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubevirt-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubevirt-dev/CANuWUD-dXi8VQ0bUVieufrWjOwZcHP5W%3DXO%2BZPbHBRp%2Btm4_pw%40mail.gmail.com.

Nahshon Unna Tsameret

unread,
Jul 4, 2024, 10:25:45 AM7/4/24
to Or Shoval, Andrew Burden, kubevirt-dev
I'm pretty sure this is not really working. As far as I know, ginkgo now just ignores custom reporter.

Daniel Hiller

unread,
Jul 5, 2024, 5:38:06 AM7/5/24
to Nahshon Unna Tsameret, Or Shoval, Andrew Burden, kubevirt-dev
Hey,

On Thu, Jul 4, 2024 at 4:25 PM Nahshon Unna Tsameret <nunn...@redhat.com> wrote:
I'm pretty sure this is not really working. As far as I know, ginkgo now just ignores custom reporter.

So you are saying that we can remove the dependency in u/s? Could you elaborate a bit?
 

On Thu, Jul 4, 2024 at 4:38 PM Or Shoval <osh...@redhat.com> wrote:


On Thu, Jul 4, 2024 at 4:35 PM Andrew Burden <abu...@redhat.com> wrote:
Hey folks,

Over the many years, the KubeVirt project has accumulated a number of repos that have fallen into inactivity. To improve the tooling and monitoring of the project we think it's time to put these repos out to pasture and archive them.

Please have a look over the list and, if you disagree with any of these being archived, be sure to comment on the tracking issue:
https://github.com/kubevirt/community/issues/239

Please note any dissent before 25 July (3 weeks).

From my investigation[1] the repos, in order of longest time since they were updated are:
2 Years:
https://github.com/kubevirt/qe-tools

Hi,
This one is used atm by kubevirt directly (to create Polarion report IIRC)
go.mod: kubevirt.io/qe-tools v0.1.8
Thanks

Archiving a repository doesn't mean that it's going away, it's just transferred to read-only, which states that it's not actively maintained any more [1]. So, the repo can still be used - setting aside the fact that it might be prone to vulnerabilities. And it can still be un-archived, should need be. 

 

Simone Tiraboschi

unread,
Jul 5, 2024, 2:59:52 PM7/5/24
to Daniel Hiller, Nahshon Unna Tsameret, Or Shoval, Andrew Burden, kubevirt-dev
On Fri, Jul 5, 2024 at 11:38 AM Daniel Hiller <dhi...@redhat.com> wrote:
Hey,

On Thu, Jul 4, 2024 at 4:25 PM Nahshon Unna Tsameret <nunn...@redhat.com> wrote:
I'm pretty sure this is not really working. As far as I know, ginkgo now just ignores custom reporter.

So you are saying that we can remove the dependency in u/s? Could you elaborate a bit?

I remember that we already discussed it a few months ago.
We double checked the results, and the conclusion is that the report from the v1 custom reporter is still working and it's still used in some environments.

It's still working because the Kubevirt test suite is using ReportViaDeprecatedReporter, see:

According to its documentation, ReportViaDeprecatedReporter is currently deprecated (it will be removed in a future minor version of Ginkgo).
  

Alice Frosi

unread,
Jul 10, 2024, 7:04:16 AM7/10/24
to Andrew Burden, kubevirt-dev
Hi Andrew,

I'm the owner of


I think we can archive it, it was an experiment but it was never used.

Alice 

Andrew Burden

unread,
Oct 1, 2024, 6:52:16 AM10/1/24
to Alice Frosi, kubevirt-dev
G'day folks,

Owing to some extended leave, it has been a bit longer than the original date of 25 July :)
In that time, it doesn't seem like this has attracted any further dissent. As such I have created this PR to archive all of the listed repos: https://github.com/kubevirt/project-infra/pull/3686

Please note, as Daniel mentioned previously, these can be unarchived at any time.

Thanks!
Reply all
Reply to author
Forward
0 new messages