Hi all,

I am also open to discuss the Jenkins 3.x release, as well as any changes 
in the versioning policy which would be helpful to Jenkins adopters. I am 
not a big fan of semver due to the same reasons as Daniel noted, but it is 
definitely one of the options on the table. My only ask here is to not 
hurry with the decisions. We will have a newly elected Release Officer on 
Dec 03, and I would wait until this happens before we do final decisions.

The next LTS cycle definitely looks to be a good opportunity for a 3.0 
release from the technical standpoint. There is a lot of breaking changes 
that justify it. It would be great to deliver even more changes, but I 
doubt we will be able to have coordinated effort for that before the next 
LTS cycle (holidays and so on). So we can ship what we have.

On a separate note, Jenkins X 3.0 is also tentatively scheduled to early 
next year. It may lead to some confusion if Jenkins and Jenkins X releases 
happen within a short timeframe.

Best regards,
Oleg Nenshev





On Thursday, November 26, 2020 at 3:53:06 PM UTC+1 [email protected] 
wrote:

> On Thu, Nov 26, 2020 at 1:53 PM Manuel Ramón León Jiménez <
> [email protected]> wrote:
>
>>
>> Anyway, I would like, when the time comes, to introduce semantic 
>> versioning <https://semver.org/#why-use-semantic-versioning>, adding a 
>> third number to the version and using them according to this way of 
>> versioning. In the future we can extend it to plugins and add some features 
>> in core to support / check / leverage this.
>>
>
> We barely keep up with basic maintenance, and we're bound to get this 
> wrong on a fairly regular basis given how we merge and release. Unless 
> you're proposing to completely overhaul all of this, I'd say it's not worth 
> the effort to then have people complaining whenever we mess up. 
>

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/5b0886f6-8192-49c3-8190-d8e4d81c18bbn%40googlegroups.com.

Reply via email to