Access to git parameter plugin

[Raihaan Shouhell]

Hi All,

I'd like to request access to the git parameter 
plugin. https://github.com/jenkinsci/git-parameter-plugin

It seems to have been abandoned. I've tried reaching out to its current 
listed 
maintainers, 
https://github.com/jenkinsci/git-parameter-plugin/blob/f1daa529bef163c9b678b537b1d4ff98c2bbc39e/pom.xml#L39-L48

One of whom, Niklaus has mentioned that he stepped down as maintainer in 
2015 and Boguslaw(kilmas7) is the current maintainer. I have yet to receive 
any reply from him.

I'd like to merge some of the PRs, move its docs to github, enable 
dependabot and incrementals and cut a new release.

Github username: res0nance
Jenkins infra account: raihaan

Cheers,
Raihaan

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/1dea1ad2-b86f-4a05-b2ed-d6e5510caf5e%40googlegroups.com.

Re: LTS schedule winter break

[Oleg Nenashev]

No objections from me.

On Tuesday, December 3, 2019 at 9:23:42 AM UTC, ogondza wrote:
>
> Alright, provided there are no objection by the meeting time tomorrow, I 
> will go and adjust the schedule. 
>
> On 02/12/2019 22.28, Mark Waite wrote: 
> > I like the postponement idea.  +1 from me 
> > 
> > On Mon, Dec 2, 2019 at 10:55 AM Daniel Beck   
> > > wrote: 
> > 
> > Hi everyone, 
> > 
> > 2.204.1 is scheduled for Dec 18, .2 would be released on Jan 15, 
> > with the RC scheduled for on Jan 1. 
> > 
> > I don't expect a lot of backport candidates, or feedback on .1 in 
> > general, to come in between Dec 18 and Jan 1. 
> > 
> > Hence I propose we take a two week break as in past years, 
> > postponing the RC and release of .2 (and all subsequent releases) by 
> > two weeks, so that the new dates are: 
> > 
> > - Dec 18: .1 release (unchanged) 
> > - Jan 15: .2 RC 
> > - Jan 29: .2 release 
> > - Feb 12: .3 RC 
> > etc. 
> > 
> > Thoughts? 
> > 
> > Daniel 
> > 
> > -- 
> > 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 jenkin...@googlegroups.com  
> > . 
>
> > To view this discussion on the web visit 
> > 
> https://groups.google.com/d/msgid/jenkinsci-dev/7D652E56-59DA-4C41-A48A-D05CBA6CCFA0%40beckweb.net.
>  
>
> > 
> > 
> > 
> > -- 
> > Thanks! 
> > Mark Waite 
>
>
> -- 
> 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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/029d955f-45d1-43e0-a17b-56047647a3a1%40googlegroups.com.

Re: Check if agent is running as a service

[Jonathan Mackenzie]

C:\WINDOWS\system32>sc query "jenkins"

SERVICE_NAME: jenkins
TYPE   : 10  WIN32_OWN_PROCESS
STATE  : 4  RUNNING
(STOPPABLE, NOT_PAUSABLE, ACCEPTS_SHUTDOWN)
WIN32_EXIT_CODE: 0  (0x0)
SERVICE_EXIT_CODE  : 0  (0x0)
CHECKPOINT : 0x0
WAIT_HINT  : 0x0

C:\WINDOWS\system32>sc query "fred"
[SC] EnumQueryServicesStatus:OpenService FAILED 1060:

The specified service does not exist as an installed service.


C:\WINDOWS\system32>

On Tue, Dec 3, 2019 at 5:56 AM Adakar  wrote:

> Hi There :)
>
> I'm working on a Jenkins plugin. I'm looking for a way to check if the
> Jenkins agent is running as a Windows service. So far my idea is to check
> if the WINSW_SERVICE_ID is set. Is there any other way? Any suggestions are
> highly appreciated :)
>
> BR, Adakar
>
> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/3193b476-8414-4c83-a3f3-a45cd6cbe1b5%40googlegroups.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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAO1vCWEALq4afNdA6ToM0SuvYd%2BW_DSFJxpEzgYuSHT%2BWhWCTw%40mail.gmail.com.

Re: How to consume incrementals?

[Jesse Glick]

On Mon, Dec 2, 2019 at 12:17 PM Matt Sicker  wrote:
> change your IntelliJ config to delegate to Maven rather than
> using its own build code

Probably not sufficient. The issue is that the IDE needs to understand
the Maven classpath for use from its editor. In the case of NetBeans,
which always runs Maven builds using a forked `mvn`, builds were never
an issue, but the IDE’s internal model had to be patched to grok
`-Pconsume-incrementals` in `.mvn/maven.config`. Otherwise it did not
know about the alternate repository location, and failed to locate
some transitive dependencies.

Possibly we could switch to activating this profile (and
`might-produce-incrementals`, though that is likely irrelevant to an
IDE) using a property set in `pom.xml` rather than relying on
`maven.config`. I cannot recall whether I tried that option during
JEP-305 research. It would be compatible, I think, and might be
supported better by IDEs.

(We also have some file-activated profiles using e.g.
`.mvn_exec_node`. I do not think that has any benefit over using a
property in this case; there is different inheritance behavior when
you have an intermediate parent POM derived from `plugin-pom`.)

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr0WshpeQuf3QP3NBS0gf%3DX%3Drp5TdKhv0JnAEGSQxq%2BMcQ%40mail.gmail.com.

Re: 2019 Election: voting has closed

[Marky Jackson]

Thank you KK, I can edit now and added my feedback

> On Dec 3, 2019, at 6:57 AM, Kohsuke Kawaguchi  wrote:
> 
> I believe you can edit the document directly. The documen is WiP at the 
> moment, so feel free to add text, comment, provide edit suggestions, etc. If 
> you prefer, prefix the text with your name.
> 
> Looking forward to seeing your feedback.
> 
> On Tue, Dec 3, 2019 at 2:13 PM Marky Jackson  > wrote:
> Tracy,
> 
> Thank you for putting this document together. I do have a few questions.
> 
> 1. How can people contribute items to this list?
> 2. Will the retrospective also have a transparent meeting with all new board 
> and officer members present?
> 3. I provided feedback I do not see on this list 
> 
> I would like to add my feedback publicly and that is the possibilities of 
> conflicts of interest in voting and nominations. More specifically around the 
> handling of votes by people whom are also nominated.
> 
> My hope is there will be a scheduled public meeting once the board and 
> officers are seated and settled.
> 
> Thank you kindly.
> 
> 
> { 
> "regards" : {
>  "name" : “marky”,
>  "phone" : "+1 (408) 464 2965 ”,
>  "email" : “marky.r.jack...@gmail.com 
> ",
>  "team" : “jackson5“,
>“role” : “software engineer"
>  }
>  }
> 
>> On Dec 3, 2019, at 3:12 AM, Tracy Miranda > > wrote:
>> 
>> 
>> Hi all,
>> 
>> Below is a doc Kohsuke kicked off, I've updated with outline of events and 
>> some of the feedback I've heard. 
>> Please feel free to add in additional feedback, much appreciated!
>> 
>> Elections Retro 
>> 
>> 
>> Tracy
>> 
>> On Sun, Dec 1, 2019 at 4:43 AM Marky Jackson > > wrote:
>> Congratulations to all! 
>> I am also very interested in giving and hearing public feedback so this 
>> process can be improved. 
>> 
>> -- 
>> 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-dev+unsubscr...@googlegroups.com 
>> .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/b95a0cdf-e34d-4ce0-a85b-3db4d91fdc88%40googlegroups.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-dev+unsubscr...@googlegroups.com 
>> .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/CACTaz6qAAknW2zPeUmRzwu6fQHw8R_DQFB_jEu9H2jf-SNjJfA%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-dev+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/0DC0419C-940C-4208-9D2A-6140DE6AB0FB%40gmail.com
>  
> .
> 
> 
> -- 
> Kohsuke Kawaguchi
> 
> -- 
> 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-dev+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/CAN4CQ4yYYgA%3D9LZuXWAOM57td1v86ZNKon2jS18Js0kiAovmGg%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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/19A862A1-9ED3-4A23-8275-9151BD55BFE2%40gmail.com.

Re: 2019 Election: voting has closed

[Kohsuke Kawaguchi]

I believe you can edit the document directly. The documen is WiP at the
moment, so feel free to add text, comment, provide edit suggestions, etc.
If you prefer, prefix the text with your name.

Looking forward to seeing your feedback.

On Tue, Dec 3, 2019 at 2:13 PM Marky Jackson 
wrote:

> Tracy,
>
> Thank you for putting this document together. I do have a few questions.
>
> 1. How can people contribute items to this list?
> 2. Will the retrospective also have a transparent meeting with all new
> board and officer members present?
> 3. I provided feedback I do not see on this list
>
> I would like to add my feedback publicly and that is the possibilities of
> conflicts of interest in voting and nominations. More specifically around
> the handling of votes by people whom are also nominated.
>
> My hope is there will be a scheduled public meeting once the board and
> officers are seated and settled.
>
> Thank you kindly.
>
>
> {
> "regards" : {
>  "name" : “marky”,
>  "phone" : "+1 (408) 464 2965 <+1%20(408)%20464%202965>”,
>  "email" : “marky.r.jack...@gmail.com",
>  "team" : “jackson5“,
>  “role” : “software engineer"
>  }
>  }
>
> On Dec 3, 2019, at 3:12 AM, Tracy Miranda  wrote:
>
> 
> Hi all,
>
> Below is a doc Kohsuke kicked off, I've updated with outline of events and
> some of the feedback I've heard.
> Please feel free to add in additional feedback, much appreciated!
>
> Elections Retro
> 
>
> Tracy
>
> On Sun, Dec 1, 2019 at 4:43 AM Marky Jackson 
> wrote:
>
>> Congratulations to all!
>> I am also very interested in giving and hearing public feedback so this
>> process can be improved.
>>
>> --
>> 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-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/b95a0cdf-e34d-4ce0-a85b-3db4d91fdc88%40googlegroups.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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CACTaz6qAAknW2zPeUmRzwu6fQHw8R_DQFB_jEu9H2jf-SNjJfA%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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/0DC0419C-940C-4208-9D2A-6140DE6AB0FB%40gmail.com
> 
> .
>


-- 
Kohsuke Kawaguchi

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAN4CQ4yYYgA%3D9LZuXWAOM57td1v86ZNKon2jS18Js0kiAovmGg%40mail.gmail.com.

Re: Backporting for LTS 2.204.1 started

[Baptiste Mathus]

Just as heads-up, also because I am not fully sure of the usual
practice/process: but I think this is worth mentioning:
https://issues.jenkins-ci.org/browse/JENKINS-57304 fix was just merged,
hence should land in next weekly next Monday or so.

If possible to consider, I think this could be a good candidate maybe. The
fix is a one-liner.

I would fully understand we'll wait for .2 for this one to receive more
weekly testing to be eligible for an LTS backport.
I just thought I'd mention it given it will not show up in the filter
before next week when it's finally marked as Resolved and released.

Cheers

Le lun. 25 nov. 2019 à 22:27, Oleg Nenashev  a
écrit :

> I went through 2.205 and 2.206 changes and marked JIRA issues which may
> deserve backporting.
>
> Best regards,
> Oleg
>
>
> On Friday, November 22, 2019 at 9:18:16 AM UTC+1, ogondza wrote:
>>
>> Backporting has started and the RC is scheduled for 2019-12-04.
>>
>> Candidates: https://issues.jenkins-ci.org/issues/?filter=12146
>> Fixed:
>> https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%202.204.1-fixed
>> Rejected:
>> https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%202.204.1-rejected
>> --
>> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/a6a15fb4-defb-4475-a045-ecaa69de8270%40googlegroups.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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS5R46ZS7dk65LKni1W5cEKm%3Do-TT6Cex5gSs6G-LCF%2Bxg%40mail.gmail.com.

Re: 2019 Election: voting has closed

[Marky Jackson]

Tracy,

Thank you for putting this document together. I do have a few questions.

1. How can people contribute items to this list?
2. Will the retrospective also have a transparent meeting with all new board 
and officer members present?
3. I provided feedback I do not see on this list 

I would like to add my feedback publicly and that is the possibilities of 
conflicts of interest in voting and nominations. More specifically around the 
handling of votes by people whom are also nominated.

My hope is there will be a scheduled public meeting once the board and officers 
are seated and settled.

Thank you kindly.


{ 
"regards" : {
 "name" : “marky”,
 "phone" : "+1 (408) 464 2965”,
 "email" : “marky.r.jack...@gmail.com",
 "team" : “jackson5“,
 “role” : “software engineer"
 }
 }

> On Dec 3, 2019, at 3:12 AM, Tracy Miranda  wrote:
> 
> 
> Hi all,
> 
> Below is a doc Kohsuke kicked off, I've updated with outline of events and 
> some of the feedback I've heard. 
> Please feel free to add in additional feedback, much appreciated!
> 
> Elections Retro
> 
> Tracy
> 
>> On Sun, Dec 1, 2019 at 4:43 AM Marky Jackson  
>> wrote:
>> Congratulations to all! 
>> I am also very interested in giving and hearing public feedback so this 
>> process can be improved. 
>> 
>> -- 
>> 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-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/b95a0cdf-e34d-4ce0-a85b-3db4d91fdc88%40googlegroups.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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/CACTaz6qAAknW2zPeUmRzwu6fQHw8R_DQFB_jEu9H2jf-SNjJfA%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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/0DC0419C-940C-4208-9D2A-6140DE6AB0FB%40gmail.com.

Check if agent is running as a service

[Adakar]

Hi There :)

I'm working on a Jenkins plugin. I'm looking for a way to check if the 
Jenkins agent is running as a Windows service. So far my idea is to check 
if the WINSW_SERVICE_ID is set. Is there any other way? Any suggestions are 
highly appreciated :)

BR, Adakar

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/3193b476-8414-4c83-a3f3-a45cd6cbe1b5%40googlegroups.com.

Re: Possible LTS regression in commons-compress

[Oliver Gondža]

James, thanks for the updates. The way I understand that is, problem is 
easily fixable, affects proprietary component and is a fairly unlikely 
thing to do to begin with, so we do not consider this to be a blocker 
for LTS.


Unless someone tells me I am wrong, I am targeting the RC for tomorrow.

On 27/11/2019 12.50, James Nord wrote:
I have tracked the cause of the issue to an optimisation we had for the 
old Hudson code to not flush all the time to prevent lots of small 
chunks being flushed (as the old implementation flushed for each block 
(512 bytes))


If I disable that then the code works with 1.15 and above.  I have not 
looked into the code to see if commons compress also has issues with 
flushing, but I doubt any other plugins will be doing any similar 
optimisation.


/James




On Wednesday, November 27, 2019 at 8:23:47 AM UTC, Baptiste Mathus wrote:

Sounds to me we should git bisect commons-compress between 1.14 and
1.15 usage, to nail and possibly confirm Björn's hypothesis?

On Wed, Nov 27, 2019 at 8:36 AM 'Björn Pedersen' via Jenkins
Developers > wrote:

Hi,

I have 2 changes that seem candiates:
1) 1.15 enforces blocklen=512 which is different from the old
default and raises an error if anything else is specified
  
(https://commons.apache.org/proper/commons-compress/javadocs/api-1.19/index.html 
)
2) 1.16 renamed the preserveAbsolutePath to |TarArchiveEntry

(String


 name,
boolean preserveAbsolutePath)|
|(less likely that is the cause).
|

Björn

Am Mittwoch, 27. November 2019 01:03:40 UTC+1 schrieb James Nord:

Hi all,

just a quick note, I /think /I have discovered a regression
in 2.204 upcoming LTS due to commons-compress library bump.

One of our plugins was using TarInputStream

for
2.190 but this is now restricted.
so without bumping core we moved the code over to use the
commons-compress version (and all is happy).

However when bumping the Jenkins version to 2.204 which
picks up the newer compress we have lots of unit test
failures due to what seems like (at very first glance as I
just narrowed it down and its late!) empty tar files (when
they should not be empty)

as a (quick and dirty) test I made the commons-compress
version configurable and it does seem like this is the issue

mvn test -Dtest=TheTest -Djenkins.version=2.204
-DcompressVersion=1.19 -Denforcer.skip *fails*
mvn test -Dtest=TheTest -Djenkins.version=2.204
-DcompressVersion=1.10 -Denforcer.skip passes
mvn test -Dtest=TheTest -Djenkins.version=2.190.3
-DcompressVersion=1.10 -Denforcer.skip passes
mvn test -Dtest=TheTest -Djenkins.version=2.190.3
-DcompressVersion=1.19 -Denforcer.skip *fails
*
doing some more bisection

mvn test -Dtest=TheTest -Djenkins.version=2.190.3
-DcompressVersion=1.15 -Denforcer.skip *fails
*mvn test -Dtest=TheTest -Djenkins.version=2.190.3
-DcompressVersion=1.13 -Denforcer.skip passes
mvn test -Dtest=TheTest -Djenkins.version=2.190.3
-DcompressVersion=1.14 -Denforcer.skip passes


I don't yet know what is causing this (but it does appear to
be something in commons-compress 1.15 and I will investigate
that.  (changelog

)

But this seems very scary to me (and I am surprised there
has not been some reports in the weeklies of archives etc
not working correctly).  Also very weired as 1.15 has been
released for a good amount of time.

Will continue the investigation tomorrow but if this rings a
bell with anyone in any reported Jiras it would be good to
correlate.

/James

-- 
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 jenkin...@googlegroups.com .
To view this discussion on the web visit

Re: 2019 Election: voting has closed

[Tracy Miranda]

Hi all,

Below is a doc Kohsuke kicked off, I've updated with outline of events and
some of the feedback I've heard.
Please feel free to add in additional feedback, much appreciated!

Elections Retro


Tracy

On Sun, Dec 1, 2019 at 4:43 AM Marky Jackson 
wrote:

> Congratulations to all!
> I am also very interested in giving and hearing public feedback so this
> process can be improved.
>
> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/b95a0cdf-e34d-4ce0-a85b-3db4d91fdc88%40googlegroups.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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CACTaz6qAAknW2zPeUmRzwu6fQHw8R_DQFB_jEu9H2jf-SNjJfA%40mail.gmail.com.

Re: LTS schedule winter break

[Oliver Gondža]

Alright, provided there are no objection by the meeting time tomorrow, I 
will go and adjust the schedule.


On 02/12/2019 22.28, Mark Waite wrote:

I like the postponement idea.  +1 from me

On Mon, Dec 2, 2019 at 10:55 AM Daniel Beck > wrote:


Hi everyone,

2.204.1 is scheduled for Dec 18, .2 would be released on Jan 15,
with the RC scheduled for on Jan 1.

I don't expect a lot of backport candidates, or feedback on .1 in
general, to come in between Dec 18 and Jan 1.

Hence I propose we take a two week break as in past years,
postponing the RC and release of .2 (and all subsequent releases) by
two weeks, so that the new dates are:

- Dec 18: .1 release (unchanged)
- Jan 15: .2 RC
- Jan 29: .2 release
- Feb 12: .3 RC
etc.

Thoughts?

Daniel

-- 
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-dev+unsubscr...@googlegroups.com
.
To view this discussion on the web visit

https://groups.google.com/d/msgid/jenkinsci-dev/7D652E56-59DA-4C41-A48A-D05CBA6CCFA0%40beckweb.net.



--
Thanks!
Mark Waite



--
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/5499a505-1ead-4c3a-c0c2-c46c27be5e0b%40gmail.com.