I just deployed the 1.509.4
My maven jobs are plenty of
INFO:
11-Oct-2013 17:51:58 org.apache.maven.cli.event.ExecutionEventLogger mojoStarted
ex : https://ci.exoplatform.org/job/gatein-portal-4.0.x-ci/67/console
Not critical but logs are less readable
Cheers,
On Thu, Oct 10, 2013 at 5:19
The price of Maven 3.1 support:
https://issues.jenkins-ci.org/browse/JENKINS-19396
On 11.10.2013, at 17:54, Arnaud Héritier aherit...@gmail.com wrote:
I just deployed the 1.509.4
My maven jobs are plenty of
INFO:
11-Oct-2013 17:51:58 org.apache.maven.cli.event.ExecutionEventLogger
On Thu, Oct 10, 2013 at 1:13 AM, Marnix Klooster
marnix.kloos...@gmail.com wrote:
I'm assuming this is a Changelog oversight
Probably. The changelog is generated by some script which in every LTS
release I have seen produces quite inaccurate results and should not
be taken too seriously.
On 10 October 2013 16:08, Jesse Glick jgl...@cloudbees.com wrote:
On Thu, Oct 10, 2013 at 1:13 AM, Marnix Klooster
marnix.kloos...@gmail.com wrote:
I'm assuming this is a Changelog oversight
Probably. The changelog is generated by some script which in every LTS
release I have seen produces
Hi,
I have backported one more commit[1] Stephen wanted after the 1.509.4-rc
was released. Contrary to what we have agreed on governance meeting I
decided _not_ to backport JENKINS-19251 as it depends on JENKINS-16261
(which is something I should have checked before, sorry). If someone
1.509.4 is released now
2013/10/9 ogondza ogon...@gmail.com
Hi,
I have backported one more commit[1] Stephen wanted after the 1.509.4-rc
was released. Contrary to what we have agreed on governance meeting I
decided _not_ to backport JENKINS-19251 as it depends on JENKINS-16261
(which is
Kohsuke Kawaguchi
Gesendet: Donnerstag, 10. Oktober 2013 03:03
An: jenkinsci-dev@googlegroups.com
Betreff: Re: Backporting 1.509.4 complete
1.509.4 is released now
2013/10/9 ogondza ogon...@gmail.commailto:ogon...@gmail.com
Hi,
I have backported one more commit[1] Stephen wanted after
But it should not really raise questions if would include it in the LTS…
In my opinion we should but this in - also when looking at the number of Votes
and Watchs on this issue, we should but it in….
Domi
On 05.10.2013, at 14:05, Christoph Kutzinski ku...@gmx.de wrote:
prevent the LTS
Or include a fix for JENKINS-19352 - which doesn't exist, yet, ergo
doesn't fulfill the requirements to be included in the LTS?
Sorry, that should read, of course:
Or include a fix for JENKINS-19396
Am 05.10.2013 14:23, schrieb Christoph Kutzinski:
I'm afraid that I'm not getting what you're
Sorry Kutz,
I was missing you point - but i got it now - so yes your right, everything is OK
..sorry for irritating you…
Domi
On 05.10.2013, at 14:25, Christoph Kutzinski ku...@gmx.de wrote:
Or include a fix for JENKINS-19352 - which doesn't exist, yet, ergo doesn't
fulfill the requirements
We have https://issues.jenkins-ci.org/browse/JENKINS-15935 in this,
which *may* have caused https://issues.jenkins-ci.org/browse/JENKINS-19352
Can someone confirm (or disprove) that JENKINS-19352 is observable in
the LTS branch? I'll try to find some time this weekend to confirm myself.
cheers
On 10/03/2013 05:46 AM, oliver gondža wrote:
Hi,
I have finished backporting issues for 1.509.4. On governance meeting, we
agreed that this is the very last minor release based on 1.509. We have 5
blockers and 8 critical fixes backported, 35 issues in total[1]. All 4
issues rejected from
Note that this is stable-rc. You should look under
http://mirrors.jenkins-ci.org/war-stable-rc/
On 10/04/2013 12:32 PM, Mirko Friedenhagen wrote:
Hello Kohsuke,
when surfing to http://mirrors.jenkins-ci.org/war-stable/ I only see
1.503.3 from September 9th.
Regards
Mirko
Regards Mirko
--
Hi,
I have finished backporting issues for 1.509.4. On governance meeting, we
agreed that this is the very last minor release based on 1.509. We have 5
blockers and 8 critical fixes backported, 35 issues in total[1]. All 4
issues rejected from 1.509.3 will be present in 1.509.4.
Kohsuke,
14 matches
Mail list logo
