On 2018-04-13 18:23, Carlos Sanchez wrote:
Hi Oliver,
There are some changes for core that would be really helpful to have in
hands of people for testing sooner than later
https://github.com/jenkinsci/jenkins/pull/3302
All new methods are marked with the new @Beta annotation so it should be
clear that it's not final.
We expect this to be in the next weekly or so,but I would really like to
ensure we can pull this into the next LTS if at all possible,what can I
do to help prepare these changes for the LTS,even if we tried to
backport it?
Hi, Let's make the discussion public.
My personal take is the LTS and Beta.class are quite orthogonal in
principle. When it comes to the actual change, it feels far from trivial
for such an exception IMO. What is the motivation here? Backporting this
will get it in LTS in 4 weeks, otherwise it will get in in 8 weeks.
Thoughts? I would really like to avoid backporting something before it
has its final shape (IOW, merged to master).
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/3b119729-f2a5-f3ac-a217-16a90a26e426%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
