https://github.com/jenkinsci/jenkins/pull/2954 has been integrated into the
master branch
2017-08-03 13:01 GMT+02:00 Andres Rodriguez :
> Thanks!
>
> On Thu, Aug 3, 2017 at 12:34 PM, Oliver Gondža wrote:
>
>> I am sorry but I was not able to make it to the meeting on the last
>> moment. I have b
Thanks!
On Thu, Aug 3, 2017 at 12:34 PM, Oliver Gondža wrote:
> I am sorry but I was not able to make it to the meeting on the last
> moment. I have backported the 4 candidates and I am pushing the RC today.
> JENKINS-45057 seems pretty nasty yet not backported, I am open to revisit
> that for 2
I am sorry but I was not able to make it to the meeting on the last
moment. I have backported the 4 candidates and I am pushing the RC
today. JENKINS-45057 seems pretty nasty yet not backported, I am open to
revisit that for 2.60.3 once merged to master.
--
oliver
--
You received this message
So, what's the status of the RC? Is it going to be pushed today / tomorrow
or is it waiting on some additional backport?
On Wed, Aug 2, 2017 at 8:06 PM, Oleg Nenashev
wrote:
> We have two pending pull requests for JENKINS-45057.
> I think it worth to consider backporting them. Will try to get on
We have two pending pull requests for JENKINS-45057.
I think it worth to consider backporting them. Will try to get one of the
fixes landed in the next weekly
четверг, 27 июля 2017 г., 17:07:01 UTC+2 пользователь Andreas Mandel
написал:
>
> All valid points, for sure. This aspect of the Train Mo
All valid points, for sure. This aspect of the Train Model was not clear to
me... I need to find a way for me how to reduce the risk to run into such
issues as much as possible for our productive system. We do tests in
advance and feedback - but actually this is not very formal (on our side)
an
> On 27. Jul 2017, at 07:19, Andreas Mandel wrote:
>
> Thanks for the feedback. Does this mean, according to plan, you release LTS
> versions even with blocker issues? Or do you judge the severity of the issue
> different?
Yes. The train model means we leave the station no matter what. Otherw
On 2017-07-27 07:19, Andreas Mandel wrote:
Thanks for the feedback. Does this mean, according to plan, you release
LTS versions even with blocker issues? Or do you judge the severity of
the issue different?
We are trying to narrow this further down to the versions you have
mentioned in the ti
Thanks for the feedback. Does this mean, according to plan, you release LTS
versions even with blocker issues? Or do you judge the severity of the
issue different?
We are trying to narrow this further down to the versions you have
mentioned in the ticket but time is unfortunately quite limited.
> On 25. Jul 2017, at 23:05, Andreas Mandel wrote:
>
> I'm not sure if this is the right place. But please take note of
> JENKINS-45057 before releasing the next LTS Version.
LTS releases only get security fixes or backports of fixes previously in the
weekly releases. See https://jenkins.io/d
I'm not sure if this is the right place. But please take note of
JENKINS-45057 before releasing the next LTS Version.
Kind Regards,
Andreas.
Am Donnerstag, 20. Juli 2017 12:26:27 UTC+2 schrieb ogondza:
>
> Backporting has started and the RC is scheduled for 2017-08-02.
>
> All 4 outstanding can
Backporting has started and the RC is scheduled for 2017-08-02.
All 4 outstanding candidates ware trivial enough and backported
immediately. There are 2 rejects that are rejected for the whole 2.60
line but I doubt we want to revisit that for .3.
Candidates: https://issues.jenkins-ci.org/issu
12 matches
Mail list logo
