Re: Archiving jenkinsci/groovy repo

[Oleg Nenashev]

Thanks! 
Looks like it was a custom fork for 
https://github.com/jenkinsci/groovy/commit/73ad9b61697e453fb334f0fe6eb3a9c3d66ce2ab
 which 
was integrated into upstream in 2011
https://issues.apache.org/jira/browse/GROOVY-5017

No need to keep it indeed

BR, Oleg

On Tuesday, January 7, 2020 at 1:09:26 PM UTC+1, ogondza wrote:
>
> The repo is archived now. It can always be unarchived if the need arises. 
>
> On 07/01/2020 11.33, Raihaan Shouhell wrote: 
> > +1 should have been archived a long time ago. 
> > 
> > Cheers, 
> > Raihaan 
> > 
> > On Tue, Jan 7, 2020 at 4:17 PM Oliver Gondža   
> > > wrote: 
> > 
> > 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 jenkin...@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.
>  
>
> > 
> > -- 
> > 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 jenkin...@googlegroups.com  
> > . 
> > To view this discussion on the web visit 
> > 
> https://groups.google.com/d/msgid/jenkinsci-dev/CAFoxvgwcj-gBCuxUyfm_w-VogutwXbtNmohigmm_9NSaw-oweg%40mail.gmail.com
>  
> > <
> https://groups.google.com/d/msgid/jenkinsci-dev/CAFoxvgwcj-gBCuxUyfm_w-VogutwXbtNmohigmm_9NSaw-oweg%40mail.gmail.com?utm_medium=email_source=footer>.
>  
>
>
>
> -- 
> 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/03a33107-4054-43a1-a832-0d6e38ac63cd%40googlegroups.com.

Re: Archiving jenkinsci/groovy repo

[Oliver Gondža]

The repo is archived now. It can always be unarchived if the need arises.

On 07/01/2020 11.33, Raihaan Shouhell wrote:

+1 should have been archived a long time ago.

Cheers,
Raihaan

On Tue, Jan 7, 2020 at 4:17 PM Oliver Gondža > wrote:


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.

--
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/CAFoxvgwcj-gBCuxUyfm_w-VogutwXbtNmohigmm_9NSaw-oweg%40mail.gmail.com 
.



--
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/56421f16-b20b-361b-5dde-f402ff856429%40gmail.com.

Re: Archiving jenkinsci/groovy repo

[Raihaan Shouhell]

+1 should have been archived a long time ago.

Cheers,
Raihaan

On Tue, Jan 7, 2020 at 4:17 PM Oliver Gondža  wrote:

> 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
> .
>

-- 
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/CAFoxvgwcj-gBCuxUyfm_w-VogutwXbtNmohigmm_9NSaw-oweg%40mail.gmail.com.

Archiving jenkinsci/groovy repo

[Oliver Gondža]

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.