Hi all, Just a quick update for this and the related discussions:
- As we discussed at the governance meeting, the Jenkins 3 discussions were scheduled to the Jenkins Contributor Summit on June 25th <https://groups.google.com/g/jenkinsci-dev/c/Tg3_pmHd5dE/m/xczMQ6eaBgAJ>. My plan was to have at least 3 hours of discussion of Jenkins 3 there, with focus on delivering changes needed for reducing maintenance overhead, Java 17 support, and Jenkins paradigm changes to reflect the modern CasC ecosystem and cloud environments. - I am sad to announce that I will be unable to drive this topic due to the conflict of interest I was unable to resolve. - If there is any contributor interested in driving the conversation for this topic, this is really good time to step up. I will be happy to help as a contributor summit organizer. Thanks to all community members who contributed by providing feedback and reviews for some of my ideas in other channels.I might have some time to drive this effort in the future, but I cannot do it now. Thanks for understanding, Oleg Nenashev Engineer, CloudBees On Wednesday, January 27, 2021 at 8:09:46 PM UTC+1 Jesse Glick wrote: > On Wed, Jan 27, 2021 at 1:18 PM Tim Jacomb <[email protected]> wrote: > >> > Date based >> […] any thoughts on the effort involved here in release automation? >> > > I think this would most easily be done by ditching `maven-release-plugin`. > We have already done the tricky bits with `flatten-maven-plugin` etc. in > JEP-305. The JEP-229 system is the safest. You can also create a special > variant like > > mvn -Drevision=$(date -I) -Dchangelist= deploy > > plus some profile activation for `maven-javadoc-plugin` & > `maven-source-plugin` similar to what `produce-incrementals` does, plus > manual tagging, with the downside that snapshot & incremental builds will > not easily or safely compare properly to releases. > -- 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/0ff2a4e6-564f-4822-b639-c0fd93fe515an%40googlegroups.com.
