Re: Java 11 as minimum? (Jetty 9.4.x EOL)

2021-12-28 Thread Oleg Nenashev 
I see no problem with switching the Weekly release line in February with
the new LTS baseline release. I also agree with Baptiste that a 3-month
notice for deprecation is too short. I suggest announcing the September LTS
as a target for complete Java 8 support removal in the LTS baseline. The
problem is how to switch the weekly early without disrupting the codebase
too much so that LTS becomes sustainable...

 A few options

   - Extend the lifetime of the current LTS baseline until September... or
   later more if needed (read as: "while somebody is dedicating resources to
   maintain it", maybe one of the vendors). We would maintain two LTS lines
   for some time, but the new one will be Java 11 only and hence we will be
   able to integrate all the upgrades shortly into the new LTS line.
   - Keep Java 8 de-facto compatibility until the June LTS cut-off in
   April/May. Add a patch to Extra Executables WAR that disables Java 8 by
   default unless *--use-deprecated-java* is set (inversuion of
   --use-future-java)

I suggest the first option if the Release and Security teams agree. IIUC
the CloudBees part of the security team would have to maintain the old
baseline for quite a while regardless, if I read
https://docs.cloudbees.com/docs/cloudbees-common/latest/maintenance-lifecycle#fixed-release
correctly. So it should not be a huge deal






On Wed, Dec 29, 2021 at 8:20 AM Baptiste Mathus  wrote:

> I like the planning idea, I think updating the minimum in Feb 2021 for
> weeklies and hence June for LTS is a bit too aggressive.
>
> I think we should *at least* target the LTS _after_ June.
>
> And in the meantime keep communicating on this timeline like we had done
> for Java 8.
> Blogs. Tweet encouraging to update to Java 11, etc. Messages on the users
> ML...
>
> Le mar. 21 déc. 2021 à 21:01, Tim Jacomb  a écrit :
>
>> Back to Java 11 :)
>>
>> (I suggest another thread for Java 17 Basil has been doing some great
>> work there)
>>
>> There's been an 'admin monitor' around for quite a while now encouraging
>> users to upgrade to Java 11 if they are on 8.
>>
>> The JavaVersionRecommendationAdminMonitor
>> 
>>  was
>> introduced in (approx):
>>
>>- 2.296 - 1st June 2021
>>- 2.303.1 - 25th August 2021
>>
>> Since that went in Java 11 usage skyrocketed according to
>> https://stats.jenkins.io/plugin-installation-trend/jvms.json
>>
>> Basil has created a PR 
>> for updating the monitor with a specific date (to be filled in) for
>> deprecation.
>>
>> I think we should target the LTS after next for dropping Java 8 support.
>>
>> That would be:
>>
>>- Weekly - 2nd February (week after baseline selection for next LTS)
>>- LTS - approx 7th June (roughly when ths LTS after next will be
>>released)
>>
>> Next LTS would also be possible, we could do:
>>
>>- Weekly - January 19th
>>- LTS - March 9th
>>
>> Thoughts?
>>
>> Thanks
>> Tim
>>
>> On Mon, 20 Dec 2021 at 22:19, Basil Crow  wrote:
>>
>>> On Mon, Dec 20, 2021 at 1:53 PM 'Jesse Glick' via Jenkins Developers
>>>  wrote:
>>> >
>>> > Is this mostly about Servlet API types, or other EE packages?
>>>
>>> Servlet types and JavaMail were the most common cases I saw in the
>>> prototype, along with a new package namespace for FileUpload to go
>>> along with the new servlet types. Seems more straightforward to do one
>>> large Jakarta migration rather than several smaller ones. This is
>>> going to be a major disruption anyway, so might as well just get it
>>> over with. The only migration I didn't tackle in the prototype was the
>>> Jakarta Dependency Injection API, because Guice doesn't support the
>>> new types yet (google/guice#1383). I imagine Guice will support them
>>> at some point in the future; Spring Security and Commons FileUpload
>>> only support the new types in snapshot releases at present. My gut
>>> feeling is that this migration will probably kick into full gear
>>> around late 2022 or early 2023.
>>>
>>> --
>>> 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/CAFwNDjpqkX2mBsBoh7LrwCBJtU%2B3ZGdvR-T9c3A3ij2mew-3ww%40mail.gmail.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/CAH-3Bie-uApHh6mDCSWOMzR%2BWBNC5ZZmjdVDXGd2cS8iaDtc3Q%40mail.gmail.com
>>

Re: Java 11 as minimum? (Jetty 9.4.x EOL)

2021-12-28 Thread Baptiste Mathus 
I like the planning idea, I think updating the minimum in Feb 2021 for
weeklies and hence June for LTS is a bit too aggressive.

I think we should *at least* target the LTS _after_ June.

And in the meantime keep communicating on this timeline like we had done
for Java 8.
Blogs. Tweet encouraging to update to Java 11, etc. Messages on the users
ML...

Le mar. 21 déc. 2021 à 21:01, Tim Jacomb  a écrit :

> Back to Java 11 :)
>
> (I suggest another thread for Java 17 Basil has been doing some great work
> there)
>
> There's been an 'admin monitor' around for quite a while now encouraging
> users to upgrade to Java 11 if they are on 8.
>
> The JavaVersionRecommendationAdminMonitor
> 
>  was
> introduced in (approx):
>
>- 2.296 - 1st June 2021
>- 2.303.1 - 25th August 2021
>
> Since that went in Java 11 usage skyrocketed according to
> https://stats.jenkins.io/plugin-installation-trend/jvms.json
>
> Basil has created a PR 
> for updating the monitor with a specific date (to be filled in) for
> deprecation.
>
> I think we should target the LTS after next for dropping Java 8 support.
>
> That would be:
>
>- Weekly - 2nd February (week after baseline selection for next LTS)
>- LTS - approx 7th June (roughly when ths LTS after next will be
>released)
>
> Next LTS would also be possible, we could do:
>
>- Weekly - January 19th
>- LTS - March 9th
>
> Thoughts?
>
> Thanks
> Tim
>
> On Mon, 20 Dec 2021 at 22:19, Basil Crow  wrote:
>
>> On Mon, Dec 20, 2021 at 1:53 PM 'Jesse Glick' via Jenkins Developers
>>  wrote:
>> >
>> > Is this mostly about Servlet API types, or other EE packages?
>>
>> Servlet types and JavaMail were the most common cases I saw in the
>> prototype, along with a new package namespace for FileUpload to go
>> along with the new servlet types. Seems more straightforward to do one
>> large Jakarta migration rather than several smaller ones. This is
>> going to be a major disruption anyway, so might as well just get it
>> over with. The only migration I didn't tackle in the prototype was the
>> Jakarta Dependency Injection API, because Guice doesn't support the
>> new types yet (google/guice#1383). I imagine Guice will support them
>> at some point in the future; Spring Security and Commons FileUpload
>> only support the new types in snapshot releases at present. My gut
>> feeling is that this migration will probably kick into full gear
>> around late 2022 or early 2023.
>>
>> --
>> 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/CAFwNDjpqkX2mBsBoh7LrwCBJtU%2B3ZGdvR-T9c3A3ij2mew-3ww%40mail.gmail.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/CAH-3Bie-uApHh6mDCSWOMzR%2BWBNC5ZZmjdVDXGd2cS8iaDtc3Q%40mail.gmail.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/CANWgJS6KhURORvDwO7CMfw%3DuLe7QTg2poAojwu6WuX50_sbyLQ%40mail.gmail.com.

Re: Setting up automated plugin release

2021-12-28 Thread Ullrich Hafner 
Maybe you can inline the existing Abstract form the JEP before the section 
‚Prerequisites‘? And add an example that shows the old and new versions in the 
abstract as well? 

> Am 28.12.2021 um 14:58 schrieb 'Jesse Glick' via Jenkins Developers 
> :
> 
> On Tue, Dec 28, 2021 at 5:50 AM Marit M  > wrote:
> now I understand that Incrementals appends a commit number, plus a SHA, to 
> version numbers.
> 
> https://www.jenkins.io/doc/developer/publishing/releasing-cd/#pom-file-modifications
>  
> 
>  says so; is there a way we could make this more prominent? 
> 
> -- 
> 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/CANfRfr04RcPDC8UQh5xKV2fQ1coQThNjR7AxSrnQ7Veay4rq7g%40mail.gmail.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/6DF2C911-A203-440A-8D28-754CD8FFB09E%40gmail.com.

Re: Setting up automated plugin release

2021-12-28 Thread 'Jesse Glick' via Jenkins Developers 
On Tue, Dec 28, 2021 at 5:50 AM Marit M  wrote:

> now I understand that Incrementals appends a commit number, plus a SHA, to
> version numbers.
>

https://www.jenkins.io/doc/developer/publishing/releasing-cd/#pom-file-modifications
says so; is there a way we could make this more prominent?

-- 
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/CANfRfr04RcPDC8UQh5xKV2fQ1coQThNjR7AxSrnQ7Veay4rq7g%40mail.gmail.com.

Re: Setting up automated plugin release

2021-12-28 Thread Marit M 
Sorry for the confusion, now I understand that Incrementals appends a 
commit number, plus a SHA, to version numbers.
I'll stick with this versioning format and revert my changes.

Thanks,
Marit. 

ב-יום שני, 27 בדצמבר 2021 בשעה 20:13:57 UTC+2, ga...@gavinmogan.com כתב/ה:

> I'll admit, I'm still confused by your request.
>
> If you enable CD, you'll have releases with a sha (ish?) on the end of
> it. If you just want the version number, don't use CD. At this point
> since version 62 is released to artifactory, you won't be able to have
> a version below 62 as they will all get parsed as older releases.
>
> I tried to look at the git history of your repo, but its all over the
> place, it looks like you un-did a bunch of jesse's fixes.
>
> Can you clearly state what your desired goals are instead of randomly
> changing things and then panicking when its not doing what your
> expecting it to work.
>
> Gavin
>
> On Mon, Dec 27, 2021 at 2:44 AM Marit M  wrote:
> >
> > I didn't meant to create that version format, what do I need to do to 
> format it as: 1.0.00?
> >
> > ב-יום שני, 27 בדצמבר 2021 בשעה 11:41:44 UTC+2, ga...@gavinmogan.com 
> כתב/ה:
> >>
> >> Why do you want that one to be the latest?
> >> According to https://github.com/jenkinsci/bmc-cfa-plugin/releases your
> >> latest version is 62 which matches updatecenter
> >> $ curl -qLs https://updates.jenkins.io/update-center.actual.json | jq
> >> '.plugins["bmc-cfa"]["version"]'
> >> "62.v6b7af476b7f8"
> >>
> >> So I'm not sure what more you want, it seems to be working fine
> >>
> >> On Mon, Dec 27, 2021 at 1:36 AM Marit M  wrote:
> >> >
> >> > I can see that version 1.0.00 exist in 
> https://repo.jenkins-ci.org/ui/repos/tree/General/releases/com/bmc/ims/bmc-cfa/1.0.00
> .
> >> > How do I make it the latest one?
> >> >
> >> >
> >> > Thanks,
> >> > Marit.
> >> >
> >> >
> >> > ב-יום שישי, 24 בדצמבר 2021 בשעה 06:57:07 UTC+2, ‪Marit M‬‏ כתב/ה:
> >> >>
> >> >> [WARNING] The requested profile "consume-incrementals" could not be 
> activated because it does not exist.
> >> >> 201[ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) 
> on project bmc-cfa: Failed to deploy artifacts: Could not transfer artifact 
> com.bmc.ims:bmc-cfa:hpi:1.0.00 from/to maven.jenkins-ci.org (
> https://repo.jenkins-ci.org/releases/): authorization failed for 
> https://repo.jenkins-ci.org/releases/com/bmc/ims/bmc-cfa/1.0.00/bmc-cfa-1.0.00.hpi,
>  
> status: 403 Forbidden -> [Help 1]
> >> >> 202[ERROR]
> >> >> 203[ERROR] To see the full stack trace of the errors, re-run Maven 
> with the -e switch.
> >> >> 204[ERROR] Re-run Maven using the -X switch to enable full debug 
> logging.
> >> >> 205[ERROR]
> >> >> 206[ERROR] For more information about the errors and possible 
> solutions, please read the following articles:
> >> >> 207[ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> >> >> 208Error: Process completed with exit code 1.
> >> >>
> >> >> ב-יום שישי, 24 בדצמבר 2021 בשעה 06:29:27 UTC+2, ‪Marit M‬‏ כתב/ה:
> >> >>>
> >> >>> And I don't see the incrementals checks in the PR.
> >> >>> How do I fix that and enable the incrementals?
> >> >>>
> >> >>> ב-יום שישי, 24 בדצמבר 2021 בשעה 06:22:29 UTC+2, ‪Marit M‬‏ כתב/ה:
> >> 
> >>  I removed the SNAPSHOT to eliminate the timestamp.
> >>  How do I set the latest version?
> >>  For some reason it sets the SNAPSHOT release as latest.
> >> 
> >>  Thanks,
> >>  Marit.
> >> 
> >>  ב-יום חמישי, 23 בדצמבר 2021 בשעה 16:32:23 UTC+2, ‪Jesse Glick‬‏ 
> כתב/ה:
> >> >
> >> > https://github.com/jenkinsci/bmc-cfa-plugin/pull/15 ought to fix 
> the version format I think. 61.vb33105387180 etc.
> >> >
> >> > You cannot easily delete a release, but there is not generally 
> any need to.
> >> >
> >> > --
> >> > 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-de...@googlegroups.com.
> >> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/43e8dfbd-55d0-4877-8c5d-e55f79ecc308n%40googlegroups.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-de...@googlegroups.com.
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/cac1551e-f2be-4c65-9b23-2d7ba5f88eb8n%40googlegroups.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