Re: [E-devel] Proposal for a small release schedule change

2014-10-27 Thread Jonathan Aquilina
You mentioned catching a break fast? do you guys host your own version control? as there is a way with github to setup Continuous integratoin testing which means the patch gets sent of to the travis CI build system a test build is carried out to verify if the patch breaks anything and said

Re: [E-devel] Proposal for a small release schedule change

2014-10-27 Thread Stefan Schmidt
Hello. On 27/10/14 08:47, Jonathan Aquilina wrote: You mentioned catching a break fast? do you guys host your own version control? as there is a way with github to setup Continuous integratoin testing which means the patch gets sent of to the travis CI build system a test build is carried

Re: [E-devel] Proposal for a small release schedule change

2014-10-25 Thread Jonathan Aquilina
How come they dont work in master directly and all patches get submitted to that. then any bug fix patches get merged from the stable branch. --- Regards, Jonathan Aquilina Founder Eagle Eye T On 2014-10-24 10:32, Daniel Kolesa wrote: 2014-10-24 9:49 GMT+02:00 Stefan Schmidt

Re: [E-devel] Proposal for a small release schedule change

2014-10-25 Thread Stefan Schmidt
Hello. On 25/10/14 09:29, Jonathan Aquilina wrote: How come they dont work in master directly and all patches get submitted to that. then any bug fix patches get merged from the stable branch. Because we want ll people to use master during the stabilization phase. That way we can ensure

Re: [E-devel] Proposal for a small release schedule change

2014-10-25 Thread The Rasterman
On Sat, 25 Oct 2014 11:59:22 +0200 Stefan Schmidt ste...@datenfreihafen.org said: Hello. On 25/10/14 09:29, Jonathan Aquilina wrote: How come they dont work in master directly and all patches get submitted to that. then any bug fix patches get merged from the stable branch.

Re: [E-devel] Proposal for a small release schedule change

2014-10-24 Thread Stefan Schmidt
Hello. On 23/10/14 10:54, Daniel Juyung Seo wrote: Hello Daniel Juyung Seo (SeoZ) On Oct 23, 2014 12:23 AM, Stefan Schmidt ste...@datenfreihafen.org wrote: Hello. On 12/10/14 16:40, Tom Hacohen wrote: I think 4 weeks is too long, 3 weeks should suffice. I agree with Tasn's idea. If I

Re: [E-devel] Proposal for a small release schedule change

2014-10-24 Thread Daniel Kolesa
2014-10-24 9:49 GMT+02:00 Stefan Schmidt ste...@datenfreihafen.org: Hello. On 23/10/14 10:54, Daniel Juyung Seo wrote: Hello Daniel Juyung Seo (SeoZ) On Oct 23, 2014 12:23 AM, Stefan Schmidt ste...@datenfreihafen.org wrote: Hello. On 12/10/14 16:40, Tom Hacohen wrote: I think

Re: [E-devel] Proposal for a small release schedule change

2014-10-24 Thread Tom Hacohen
On 24/10/14 09:32, Daniel Kolesa wrote: 2014-10-24 9:49 GMT+02:00 Stefan Schmidt ste...@datenfreihafen.org: Hello. On 23/10/14 10:54, Daniel Juyung Seo wrote: Hello Daniel Juyung Seo (SeoZ) On Oct 23, 2014 12:23 AM, Stefan Schmidt ste...@datenfreihafen.org wrote: Hello. On 12/10/14

Re: [E-devel] Proposal for a small release schedule change

2014-10-24 Thread Daniel Kolesa
On Oct 24, 2014 10:42 AM, Tom Hacohen tom.haco...@samsung.com wrote: On 24/10/14 09:32, Daniel Kolesa wrote: 2014-10-24 9:49 GMT+02:00 Stefan Schmidt ste...@datenfreihafen.org: Hello. On 23/10/14 10:54, Daniel Juyung Seo wrote: Hello Daniel Juyung Seo (SeoZ) On Oct 23, 2014

Re: [E-devel] Proposal for a small release schedule change

2014-10-24 Thread Tom Hacohen
On 24/10/14 11:28, Daniel Kolesa wrote: On Oct 24, 2014 10:42 AM, Tom Hacohen tom.haco...@samsung.com wrote: On 24/10/14 09:32, Daniel Kolesa wrote: 2014-10-24 9:49 GMT+02:00 Stefan Schmidt ste...@datenfreihafen.org: Hello. On 23/10/14 10:54, Daniel Juyung Seo wrote: Hello Daniel Juyung

Re: [E-devel] Proposal for a small release schedule change

2014-10-24 Thread The Rasterman
On Fri, 24 Oct 2014 09:49:20 +0200 Stefan Schmidt ste...@datenfreihafen.org said: Hello. On 23/10/14 10:54, Daniel Juyung Seo wrote: Hello Daniel Juyung Seo (SeoZ) On Oct 23, 2014 12:23 AM, Stefan Schmidt ste...@datenfreihafen.org wrote: Hello. On 12/10/14 16:40, Tom Hacohen

Re: [E-devel] Proposal for a small release schedule change

2014-10-23 Thread Daniel Juyung Seo
Hello Daniel Juyung Seo (SeoZ) On Oct 23, 2014 12:23 AM, Stefan Schmidt ste...@datenfreihafen.org wrote: Hello. On 12/10/14 16:40, Tom Hacohen wrote: I think 4 weeks is too long, 3 weeks should suffice. I agree with Tasn's idea. If I remember correctly, the main reason of splitting the

Re: [E-devel] Proposal for a small release schedule change

2014-10-22 Thread Stefan Schmidt
Hello. On 12/10/14 16:40, Tom Hacohen wrote: I think 4 weeks is too long, 3 weeks should suffice. You would want to add this week to the merge window or cut the whole cycle down to 11 weeks? From my experience with the last 4 releases I think an extra week for testing would help. regards

[E-devel] Proposal for a small release schedule change

2014-10-12 Thread Stefan Schmidt
Hello. Greetings from EFL Dev Day! During my release status talk I mentioned a small change I would like to change for future releases. The feedback was positive so I want to bring it up here for a wider audience. What I propose is to merge the the two merge windows (pun intended) and move the

Re: [E-devel] Proposal for a small release schedule change

2014-10-12 Thread Stefan Schmidt
Hello. On 12/10/14 10:34, Stefan Schmidt wrote: Hello. Greetings from EFL Dev Day! During my release status talk I mentioned a small change I would like to change for future releases. The feedback was positive so I want to bring it up here for a wider audience. What I propose is to

Re: [E-devel] Proposal for a small release schedule change

2014-10-12 Thread Tom Hacohen
I think 4 weeks is too long, 3 weeks should suffice. On 12 Oct 2014 10:35, Stefan Schmidt ste...@datenfreihafen.org wrote: Hello. Greetings from EFL Dev Day! During my release status talk I mentioned a small change I would like to change for future releases. The feedback was positive so I