Re: [PROPOSE] RM for 4.14

| e. ggoodr...@ippathways.com> j...@ippathways.com> >> >> >> >> On Dec 19, 2019, at 12:30 PM, Paul Angus > >> > >> paul.an...@shapeblue.com>> wrote: >> >> >> >> I can answe

Re: [PROPOSE] RM for 4.14

current branch at the time that an LTS was due, that branch would > get some > >> 'extra treatment' and be supported for a few years rather than a few > >> months. > >> > >> Very importantly, the post x.x.0 LTS releases were to

Re: [PROPOSE] RM for 4.14

improvement, is another person's bugfix) >> >> Yes 4.13 is young (and an LTS) so there will undoubtably a 4.13.1 with all >> critical/blocker/major bugfixes in it (probably as soon as enough people >> have recovered from a 4.14 release cycle) but it can'

Re: [PROPOSE] RM for 4.14

pported' branch but still get bug fixes in releases, without having to >> worry about, test or document new features constantly. >> >> (I'll hand-wave over the fact that one person's feature is another >> person's improvement, is another person's bugfix) >> >> Yes 4.1

Re: [PROPOSE] RM for 4.14

people > have recovered from a 4.14 release cycle) but it can't have any new > features in it. > > So looking forward, if someone wants a 4.15 release in (say) April, then > the 'summer' LTS branch (July/August time) will be 4.16, if not, then the > summer LTS release would be 4.15 >

Re: [PROPOSE] RM for 4.14

al Message- From: Gabriel Beims Bräscher Sent: 19 December 2019 16:59 To: dev Subject: Re: [PROPOSE] RM for 4.14 Hello Andrija, That is always good news to have contributors stepping up and getting new releases done. We definitely need a release (either a major or a 4.13.1.0) to keep the pro

Re: [PROPOSE] RM for 4.14

peblue.com<mailto:paul.an...@shapeblue.com> > www.shapeblue.com<http://www.shapeblue.com> > Amadeus House, Floral Street, London WC2E 9DPUK > @shapeblue > > > > > -Original Message- > From: Gabriel Beims Bräscher > Sent: 19 December 2019 16:59 > To: dev > Subjec

Re: [PROPOSE] RM for 4.14

reet, London WC2E 9DPUK @shapeblue -Original Message- From: Gabriel Beims Bräscher Sent: 19 December 2019 16:59 To: dev Subject: Re: [PROPOSE] RM for 4.14 Hello Andrija, That is always good news to have contributors stepping up and getting new releases done. We definitely need a

RE: [PROPOSE] RM for 4.14

Bräscher Sent: 19 December 2019 16:59 To: dev Subject: Re: [PROPOSE] RM for 4.14 Hello Andrija, That is always good news to have contributors stepping up and getting new releases done. We definitely need a release (either a major or a 4.13.1.0) to keep the project traction. However, I would like

Re: [PROPOSE] RM for 4.14

Hello Andrija, That is always good news to have contributors stepping up and getting new releases done. We definitely need a release (either a major or a 4.13.1.0) to keep the project traction. However, I would like to understand why 4.14.0.0 is being considered an LTS release. As far as I know,

Re: [PROPOSE] RM for 4.14

Hi Andrija, How can I help and engage in this process? Cheers Sven __ Sven Vogel Teamlead Platform EWERK DIGITAL GmbH Brühl 24, D-04109 Leipzig P +49 341 42649 - 99 F +49 341 42649 - 98 s.vo...@ewerk.com www.ewerk.com Geschäftsführer: Dr. Erik Wende, Hendrik Schubert, Frank Richter

[PROPOSE] RM for 4.14

Hi All, I’d like to put myself forward as release manager for 4.14. The 4.14 releases will be the next major version LTS release and will be supported for 20 months per the LTS manifesto [2]. I'll have support from Rohit/Daan/Paul during the process and anyone else interested is most welcome to