Hi Bob, Agree with your statement, and there might be a way to handle at least the "when is a new release" question.
In the past I worked on a project that had every 2 months a new release. There was no guarantee what was in it, what would be solved etc, but if some patch or functionality appeared in the master-branch, it would be part of the next release. Depending on what was solved the X.Y.Z number was increased. If Libtiff could setup a similar workflow and have an (semi) automatic release e.g. every 2,3,4,6,12 months, the "release date" questions would always have a clear answer. The only reason to skip a new release would be that nothing is merged into master. One would not need discussions about when the next release is, or what is in it as the above way of working solves both questions in a pragmatic way. (I know in reality it will be more complicated ) thoughts? regards, Rob On Wed, Mar 9, 2022 at 5:40 PM Bob Friesenhahn <[email protected]> wrote: > Recently there have been a number of people making direct demands to > libtiff maintainers (e.g. @userid in GitLab communications, or > human@address) to create libtiff releases, or address some specific > issue which is of interest to them. > > If it is not clear, libtiff developers/maintainers are unpaid > volunteers who are donating precious time that they could be spending > at the lake, walking their dog, or spending time with their family. > > It is not reasonable to make direct demands of a volunteer. Making > direct demands to a volunteer to perform a service for you is likely > to have the opposite effect which was intended. > > Rather than making direct demands of a volunteer, it is better to > volunteer your own time to assist the libtiff project, or perhaps > provide direct payments for services to volunteers willing to accept > such payments, keeping in mind that developers at this skill level > normally earn well over $100k/year in US dollars and you would be > paying for their most valuable time. > > Bob > -- > Bob Friesenhahn > [email protected], http://www.simplesystems.org/users/bfriesen/ > GraphicsMagick Maintainer, http://www.GraphicsMagick.org/ > Public Key, http://www.simplesystems.org/users/bfriesen/public-key.txt > _______________________________________________ > Tiff mailing list > [email protected] > https://lists.osgeo.org/mailman/listinfo/tiff >
_______________________________________________ Tiff mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/tiff
