stephenconnolly on JENKINS-35402: [~olivergondza] I really would like this in the 2.7.1 LTS
stephenconnolly on JENKINS-35402: [~olivergondza] I really would like this in the 2.7.1 LTS
--
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/4b27217d-6487-4091-b46b-d869f4326d69%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
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 jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/4af38d30-773d-fa5d-d237-fe256d6fc58f%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
I would also consider PR 2379, because it slightly improves Jenkins WebUI performance. JENKINS-31915 seems to be important as well, but there is not so much votes for this fix.
Regarding non-released changes, maybe we want to consider the following:
BR, Oleg
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/3050071d-3e43-4cfa-993a-ff63d4380aa6%40googlegroups.com.
Any chance for https://github.com/jenkinsci/jenkins/commit/310c952602f7241cb74454b7e7fb2be0bf3d2980 to be backported ? https://issues.jenkins-ci.org/browse/JENKINS-34923
--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/ieXnaHVqX3k/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANMVJznF8P4UU7JE9xT_HzCdj2pi7cx%2B%3D%2Bqr8M_UXSSe82YT9w%40mail.gmail.com.
@NicolasAny chance for https://github.com/jenkinsci/jenkins/commit/310c952602f7241cb74454b7e7fb2be0bf3d2980 to be backported ? https://issues.jenkins-ci.org/browse/JENKINS-34923This an improvement, which changes the API.In order to make it backportable, you should ensure that there is no external API users and add @Restricted then.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLAt60a6t5Y9qcwrgkgOEfPE8M5MgLEE_G8pgXQkg76qnQ%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-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/42EC5EF4-DAFA-4F20-8DBA-00A7B23D9BB5%40beckweb.net.
JENKINS-35402 is the only one that I am asking for. I know technically it is a feature but it is a simple refactoring and I believe it will be needed for some use cases with regard to people that are repackaging Jenkins... there are other ways around if we cannot get this in, but those other ways are considerably more ugly and require adding a lot more code to a repackaged Jenkins WAR than would be required with this small change
JENKINS-35402 is the only one that I am asking for. I know technically it is a feature but it is a simple refactoring and I believe it will be needed for some use cases with regard to people that are repackaging Jenkins... there are other ways around if we cannot get this in, but those other ways are considerably more ugly and require adding a lot more code to a repackaged Jenkins WAR than would be required with this small change
I agree that this change would be useful && it's harmless.
So it may be fine to merge it into .1 or maybe .2
--пятница, 10 июня 2016 г., 0:20:39 UTC+2 пользователь Stephen Connolly написал:JENKINS-35402 is the only one that I am asking for. I know technically it is a feature but it is a simple refactoring and I believe it will be needed for some use cases with regard to people that are repackaging Jenkins... there are other ways around if we cannot get this in, but those other ways are considerably more ugly and require adding a lot more code to a repackaged Jenkins WAR than would be required with this small changeOn 9 June 2016 at 23:05, Daniel Beck <m...@beckweb.net> wrote:
> On 09.06.2016, at 14:57, Oleg Nenashev <o.v.ne...@gmail.com> wrote:
>
> I would also consider PR 2379, because it slightly improves Jenkins WebUI performance.
Could we please remember what constitutes a change eligible for back porting?
Because this isn't. I like the change as well, but it's a tiny performance improvement.
> On 09.06.2016, at 18:07, nicolas de loof <nicolas...@gmail.com> wrote:
>
> Any chance for https://github.com/jenkinsci/jenkins/commit/310c952602f7241cb74454b7e7fb2be0bf3d2980 to be backported ?
> https://issues.jenkins-ci.org/browse/JENKINS-34923
Similar problem. It's an improvement/feature.
We're already drowning Oliver in legitimate requests, wanting features in LTS is overkill ;-)
--
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/42EC5EF4-DAFA-4F20-8DBA-00A7B23D9BB5%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.
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/e0431963-cda0-4460-a604-6ef7478cd57b%40googlegroups.com.
--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/ieXnaHVqX3k/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/aded04c1-28e3-5359-5bb9-6eaa647c7b0a%40gmail.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/CAPfivLDE627Tc6_vvHzZz0nu-hrLZSxEyxucPoxX9QzZi7wmEQ%40mail.gmail.com.
--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/ieXnaHVqX3k/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/4f621098-ed39-462d-a245-52f882650d89%40googlegroups.com.
Thanks a lot for your efforts!The RC branch looks good to me
2016-06-21 19:02 GMT+02:00 ogondza <ogo...@gmail.com>:
I consider backporting to be close. All was backported except for JENKINS-35641 and JENKINS-34923 where I would like it to have some extra soaking time. Note that I will not be able to attend the Governance meeting (travelling) so I will proceed with the rc at the closest time I am available unless I hear some objection, either here or in meeting logs, or the ATH will fail seriously.
--
oliver
--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/ieXnaHVqX3k/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-dev+unsubscribe@googlegroups.com.
Hi,
Sorry for being a slowpoke.
@Oliver @KK If you have not started the RC release yet, maybe makes sense to pick remoting-2.60. It contains several important fixes (see changelog), which has been soaked for about 1 week. IMHO it would be useful to pick this version.
I'm planning to maintain an LTS & Backporting branch in remoting for 2.7.1 baseline, so bumpong of the release would be useful in order to avoid full backporting for the next release.
BR, Oleg
вторник, 21 июня 2016 г., 19:09:00 UTC+2 пользователь Oleg Nenashev написал:
Thanks a lot for your efforts!The RC branch looks good to me
2016-06-21 19:02 GMT+02:00 ogondza <ogo...@gmail.com>:
I consider backporting to be close. All was backported except for JENKINS-35641 and JENKINS-34923 where I would like it to have some extra soaking time. Note that I will not be able to attend the Governance meeting (travelling) so I will proceed with the rc at the closest time I am available unless I hear some objection, either here or in meeting logs, or the ATH will fail seriously.
--
oliver
--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/ieXnaHVqX3k/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/da62c57c-dbc8-4d8d-879a-275ec246a88e%40googlegroups.com.
If remoting 2.60 didn't get into the RC, I would vote against bumping the version without re-spinning RC. If we don't want to re-spin the RC, it should be perfectly fine to keep the version as is.All 2.60 fixes are actually [node/client]-side fixes, so Jenkins users can get them by updating slave.jar files.
BR, Oleg
--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/ieXnaHVqX3k/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAFNCU--tb8Oh72H%2B1-qYBhudQf4iN9Ug1JsL2_nxyWt6gt647Q%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-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLADFEY%2Be6-d_X4mGQ7wdWJa%3DxY4HzyRggWk%2BXTHTO%2BQKQ%40mail.gmail.com.