Re: Wrong date for Jenkins LTS Release 2.387.2?

['FredG' via Jenkins Developers]

Hi Mark,

Thanks for the fast response! Next time I'll try to create a PR myself. 

Regards,

Fred
On Thursday, April 6, 2023 at 2:07:52 PM UTC+2 Mark Waite wrote:

> Thanks for catching that.  Fix proposed in 
> https://github.com/jenkins-infra/jenkins.io/pull/6243
>
> On Thursday, April 6, 2023 at 5:58:37 AM UTC-6 FredG wrote:
>
>> Hi,
>>
>> First of all, thanks to everyone that is working on Jenkins LTS releases!
>> Your work is greatly appreciated. 
>>
>> I assume this was a simple copy and paste error, but shouldn't the date
>> for Jenkins LTS release 2.387.2 be 2023-04-05 instead of 2023-03-22?
>>
>> 2023-03-22 was the release date of the LTS RC, if I'm not mistaken.
>>
>> Regards,
>>
>> Fred
>>
>

-- 
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/961aea95-7527-4794-bf76-5df1650120a5n%40googlegroups.com.

Wrong date for Jenkins LTS Release 2.387.2?

['FredG' via Jenkins Developers]

Hi,

First of all, thanks to everyone that is working on Jenkins LTS releases!
Your work is greatly appreciated. 

I assume this was a simple copy and paste error, but shouldn't the date
for Jenkins LTS release 2.387.2 be 2023-04-05 instead of 2023-03-22?

2023-03-22 was the release date of the LTS RC, if I'm not mistaken.

Regards,

Fred

-- 
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/28063477-3ff9-4dc5-adea-9504a7568b1cn%40googlegroups.com.

Re: Enforcing HTTPS on mirrors.jenkins.io + consolidating to get.jenkins.io

['FredG' via Jenkins Developers]

Thanks Damien for the confirmation. I'm glad it's not "just me". :)

I can confirm that I can reach updates.jenkins.io again! 

Regards,

Fred

On Thursday, May 19, 2022 at 12:18:29 PM UTC+2 damien@gmail.com wrote:

> Hello FredG,
>
> our messages crossed, but yes, the errors on updates.jenkins.io are an un 
> planned side effect of this change.
>
> We try our best to keep status.jenkins.io up to date (sometime we fail ;) 
> ) but it has the informations.
>
> updates.jenkins.io should be back for you now: can you confirm?
> Le jeudi 19 mai 2022 à 11:59:59 UTC+2, FredG a écrit :
>
>> Hi,
>>
>> Do I assume correctly that this also affects the availability of 
>> ùpdates.jenkins.io`?
>> I'm having issues connecting to it (e.g. while trying to access the 
>> update center).
>>
>>
>> Regards,
>>
>> Fred
>>
>>
>> On Thursday, May 19, 2022 at 9:57:33 AM UTC+2 damien@gmail.com wrote:
>>
>>> Hello there!
>>>
>>> Reminder that we’re going to change the DNS record of `
>>> mirrors.jenkins.io` to `get.jenkins.io` in the upcoming hour, enforcing 
>>> HTTPS.
>>>
>>>
>>> Ref. https://www.jenkins.io/blog/2022/05/13/mirrors/
>>>
>>>
>>> Cheers, 
>>>
>>> For the infra team,
>>> Damien DUPORTAL
>>>
>>

-- 
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/e464e662-b3a1-4c63-a754-0c1e82841a39n%40googlegroups.com.

Re: Enforcing HTTPS on mirrors.jenkins.io + consolidating to get.jenkins.io

['FredG' via Jenkins Developers]

Hi,

Do I assume correctly that this also affects the availability of 
ùpdates.jenkins.io`?
I'm having issues connecting to it (e.g. while trying to access the update 
center).


Regards,

Fred


On Thursday, May 19, 2022 at 9:57:33 AM UTC+2 damien@gmail.com wrote:

> Hello there!
>
> Reminder that we’re going to change the DNS record of `mirrors.jenkins.io` 
> to `get.jenkins.io` in the upcoming hour, enforcing HTTPS.
>
>
> Ref. https://www.jenkins.io/blog/2022/05/13/mirrors/
>
>
> Cheers, 
>
> For the infra team,
> Damien DUPORTAL
>

-- 
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/0d2c82c9-196e-424a-855f-830704dda4den%40googlegroups.com.

Re: Jenkins Security Advisories - UX Improvement Suggestions

['FredG' via Jenkins Developers]

Sorry to resurrect this thread from the dead. 
More than one year later, the security advisories still suffer from the 
same issues.

Especially security advisories for a large number of plugins like 
https://www.jenkins.io/security/advisory/2022-02-15/ are hard to read, when 
the severity is only mentioned in a list at end.

Hopefully the format/structure of the security advisories can be improved 
in the near future. TIA

Regards,

Fred

On Thursday, January 14, 2021 at 8:00:15 PM UTC+1 FredG wrote:

> Thanks Daniel!
>
> I think I'll wait for the human-readable version. :D
>
> On Thursday, January 14, 2021 at 7:55:55 PM UTC+1 Daniel Beck wrote:
>
>>
>>
>> > On 14. Jan 2021, at 17:58, 'FredG' via Jenkins Developers <
>> jenkin...@googlegroups.com> wrote:
>> > 
>> > I'd suggest to add the severity to each issue's description to avoid 
>> the scrolling. If there is no added value in the separate severity section, 
>> than maybe getting rid of it entirely makes sense as well.
>>
>> Thanks for the feedback, I'll do that. I'm pretty sure I even have some 
>> work in progress for this somewhere, and then I wanted to move 
>> affected/fixed components too, but that ended up being more difficult, and 
>> I didn't do either in the end... Time to restart this!
>>
>> (Meanwhile, as a workaround, you could view the page source. Unlike most 
>> jenkins.io stuff, the page is basically generated from front matter 
>> (metadata) using the page template. So if you can read YAML somewhat well, 
>> that is already grouped like you expect.)
>>
>>

-- 
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/a1b288ab-1dd4-4dea-992e-395d08065131n%40googlegroups.com.

Re: Jenkins Security Advisories - UX Improvement Suggestions

['FredG' via Jenkins Developers]

Thanks Daniel!

I think I'll wait for the human-readable version. :D

On Thursday, January 14, 2021 at 7:55:55 PM UTC+1 Daniel Beck wrote:

>
>
> > On 14. Jan 2021, at 17:58, 'FredG' via Jenkins Developers <
> jenkin...@googlegroups.com> wrote:
> > 
> > I'd suggest to add the severity to each issue's description to avoid the 
> scrolling. If there is no added value in the separate severity section, 
> than maybe getting rid of it entirely makes sense as well.
>
> Thanks for the feedback, I'll do that. I'm pretty sure I even have some 
> work in progress for this somewhere, and then I wanted to move 
> affected/fixed components too, but that ended up being more difficult, and 
> I didn't do either in the end... Time to restart this!
>
> (Meanwhile, as a workaround, you could view the page source. Unlike most 
> jenkins.io stuff, the page is basically generated from front matter 
> (metadata) using the page template. So if you can read YAML somewhat well, 
> that is already grouped like you expect.)
>
>

-- 
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/8ef6a049-c342-4148-9d94-66032e36be8dn%40googlegroups.com.

Jenkins Security Advisories - UX Improvement Suggestions

['FredG' via Jenkins Developers]

Hi,

Thanks for the very thorough Jenkins security advisories.
Unfortunately, I find myself scrolling up and down a lot, when trying to 
find out the severity of an issue while reading it's description. That the 
order of the issues differs between the description section and the 
severity section does not help either. ;)

I'd suggest to add the severity to each issue's description to avoid the 
scrolling. If there is no added value in the separate severity section, 
than maybe getting rid of it entirely makes sense as well.

Regards,

Fred

-- 
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/7ec18933-2407-46b8-b812-84618d46a17fn%40googlegroups.com.

Re: disk-usage-plugin seems to be abandoned

['FredG' via Jenkins Developers]

Hi,

Unfortunately Lucie did not seem to have time to do the release.

@Oleg: Could you spin a release?
(If I don't need any special permissions, I can also do it myself if that's 
OK).

Regards,

Fred

On Tuesday, February 21, 2017 at 11:34:34 PM UTC+1, FredG wrote:
>
> Hi Oleg,
>
> Unfortunately I also have too many other things going on to maintain yet 
> another plugin.
>
> It looks like Lucie might be able to do a release, which would be much 
> appreciated.
> Finding a new maintainer is important, but a lot less urgent.
>
> Regards,
>
> Fred
>
>
> On Tuesday, February 21, 2017 at 12:50:55 PM UTC+1, Oleg Nenashev wrote:
>>
>> Hi Fred,
>>
>> Are you ready to take the ownership (maybe till Lucie gets back)?
>> I can spin the release now if it is required, but unfortunately I have no 
>> time even to maintain my current stuff :(
>>
>> BR, Oleg
>>
>> P.S: Get well soon, Lucie!
>>
>>
>> вторник, 21 февраля 2017 г., 9:39:23 UTC+1 пользователь ogondza написал:
>>>
>>> On 2017-02-21 01:44, Kanstantsin Shautsou wrote: 
>>> > Confirm. @lvotypko made refactorings and disappeared. 
>>> > I made few attempts to request release with fixes in last half year, 
>>> but 
>>> > nobody from RedHat made release. Plugin is very useful and before 
>>> > lvotypko i was even ready to refactor or write new. 
>>> > Who remember @ogondza email? Please CC him. 
>>>
>>> Lucie is taking a sick leave to respond to this thread but I afraid she 
>>> is not able to devote much more of a time to maintaining this plugin. 
>>> Feel free to proceed with adoption. 
>>>
>>> -- 
>>> 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/6a3c77a4-5f8e-4d9c-ae32-af777cd57a56%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: disk-usage-plugin seems to be abandoned

['FredG' via Jenkins Developers]

Hi Oleg,

Unfortunately I also have too many other things going on to maintain yet 
another plugin.

It looks like Lucie might be able to do a release, which would be much 
appreciated.
Finding a new maintainer is important, but a lot less urgent.

Regards,

Fred


On Tuesday, February 21, 2017 at 12:50:55 PM UTC+1, Oleg Nenashev wrote:
>
> Hi Fred,
>
> Are you ready to take the ownership (maybe till Lucie gets back)?
> I can spin the release now if it is required, but unfortunately I have no 
> time even to maintain my current stuff :(
>
> BR, Oleg
>
> P.S: Get well soon, Lucie!
>
>
> вторник, 21 февраля 2017 г., 9:39:23 UTC+1 пользователь ogondza написал:
>>
>> On 2017-02-21 01:44, Kanstantsin Shautsou wrote: 
>> > Confirm. @lvotypko made refactorings and disappeared. 
>> > I made few attempts to request release with fixes in last half year, 
>> but 
>> > nobody from RedHat made release. Plugin is very useful and before 
>> > lvotypko i was even ready to refactor or write new. 
>> > Who remember @ogondza email? Please CC him. 
>>
>> Lucie is taking a sick leave to respond to this thread but I afraid she 
>> is not able to devote much more of a time to maintaining this plugin. 
>> Feel free to proceed with adoption. 
>>
>> -- 
>> 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/1aa7266d-96c6-41f9-8a6b-4d01f0b6be11%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

disk-usage-plugin seems to be abandoned

['FredG' via Jenkins Developers]

Hi,

It seems like the disk-usage-plugin 
 has been 
abandoned.
Last commit is from Feb 10, 2016, last release was done October 1, 2015.
The current maintainer lvotypko  did not react 
to messages and mentions on pull request #34 
.

Since there are quite a few commits with fixes that people are waiting for, 
including an annoying UI bug (see PR #34) that causes Icons not to show up,
I'd like to propose the following:

   - let's wait for one week
   - if maintainer does not reply or react somehow, let someone else 
   release the plugin (any volunteers?)
   - try to contact the maintainer again, if that fails, mark the plugin 
   for adoption
   

Please let me know, if this should be handled somehow differently.


Regards,


Fred

-- 
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/8ebc74f4-c623-4358-a1b7-760a5e0fc165%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.