On Mon, Feb 2, 2026 at 4:03 AM Jan Faracik wrote: > Two cents on this based on our discussion on Friday. Agreed that a year > based approach is the better long term solution, but I’d argue switching to > 3.x is the better short term move. We need to agree what we’re doing this > for - e.g. a marketing boost for the short term vs more sensible version > numbers for the long term. I'd argue we'd benefit more from the short term > boost than the long term, e.g. increasing/maintaining user base, increasing > contributors for 2026/2027. >
I don't see the difference in marketing boost between 3.x and year based version. In both cases, the users will see a significant change to the version number and will evaluate the meaning of that significant change to the version number. Can you explain further? Mark Waite -- 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 visit https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtE3OhHKiripPA4Dw13JasendR%2BxRoyAezGOU7enAfT4tA%40mail.gmail.com.
