Yes, I'll tag a release when it's ready to go. On Tue, 16 Feb 2016 at 17:26 Sean Whitton <spwhit...@spwhitton.name> wrote:
> Hello, > > On Tue, Feb 16, 2016 at 01:55:47PM +0000, James R Barlow wrote: > > I updated my tree, eliminating one file whose status I couldn't > determine, > > replacing another with an equivalent free file and documenting the rest. > The > > file has also been renamed to README so that Github shows it > automatically. > > https://github.com/jbarlow83/OCRmyPDF/tree/develop/tests/resources > > Thank you for taking the time to clarify the status of those files. > > > Please note this is in my develop branch at the moment, not yet merged > > into master until I fix a few broken test cases (unrelated reasons). > > Okay. Are you planning to tag a release after you merge into master? > If a new release is imminent I'll hold off uploading my package. No > pressure; just let me know your plans. > > > Does a Deb package usually run tests? From the point of view of saving > > some disk space, maybe this is not wanted. > > Yes, if there is an upstream test suite then a Debian package should run > it at package build time. We also have a CI farm running tests and I > intend to run OCRmyPDF's tests there too. > > It wouldn't help with disc space as Debian packages are meant to include > an untouched copy of upstream releases. > > -- > Sean Whitton >
