On Monday 30 January 2017 09:47:45 Carsten Ziegeler wrote: > Hi, Hi,
> while I agree that it feels a little bit strange release without any > functional changes, there is nothing wrong with doing this release. As > you say releasing is cheap. that depends on how you define cheap. Doing a release takes about 1 hour and checking a release at least 20 to 30 minutes per developer (additional time for integrating a new release into a product). Regards, O. > Carsten > > Timothee Maret wrote > > > Hi, > > > > 2017-01-27 13:55 GMT+01:00 Oliver Lietz <[email protected]>: > >> On Thursday 26 January 2017 12:58:34 Stefan Seifert wrote: > >>> +1 > >>> > >>> (although it looks strange that the list of changes contains no > >> > >> functional > >> > >>> change and only an improved unit test coverage) > >> > >> Does improved test coverage really justify a new release? > > > > The motive is a technical one. Indeed, a release is needed for us @ Adobe > > as we run internal tests on released artefacts. > > > > Generally, I thought that releasing are cheap and thus we could go for it. > > However, if it does not make sense from Sling POV, I would cancel the > > release process. > > Please let me know. > > > > Regards, > > > > Timothee > > > >> O. > >> > >>> stefan
