Hi Even,

Not volunteering for release manager however a few remarks pop up
- is there any release policy document?
- in a past job I have encountered
  - release on request (except on Friday afternoon)
  - release on urgency
  - release on some time argument (day, week, sprint, month, quarter, year)
  - release when hardware was released (software was following)

All had their pros and cons so having a release policy can help to manage
the expectations of
- the users
- the developers
- the maintainers

For the TIFF library I would propose the following release policy (just a
starting point)

   1. There is a nightly build of the main/master branch available.  (think
   this one is covered)
   Allows everyone to work with the latest greatest.
   2. There are two (or three?) releases per year for PR's that can wait -
   minor fixes/changes/adds/removes.
   The release month is communicated in advance.
   Maintainers can decide if a Pull/ Change Request is in coming release or
   one after.
   Developers know in theory a timeframe when their PR/CR is included.
   3.  Additional releases can be made on request e.g. for broken code or
   security patches.
   Users have the right to request such release
   Developers have the right to work on such item
   Maintainers have the right to schedule the request.
   4. Maintainers can reschedule releases
   5. The release policy is written and maintained by the TIFF maintainers.


Just thinking out loud,

Regards,
Rob







On Wed, Aug 16, 2023 at 3:09 PM Even Rouault <[email protected]>
wrote:

> Hi,
>
> apparently people are not happy with the current release pace of the
> current team: https://gitlab.com/libtiff/libtiff/-/issues/602
>
> So if anyone wants to take care of that, they're welcome. I'm not
> totally giving up, but for my own needs, a release every year is
> generally just fine.
>
> Actually maybe we should do a release "soon", now that the removal of
> most of the tools has been committed
> (https://gitlab.com/libtiff/libtiff/-/merge_requests/520), to get
> relieved from the main source for such repeated pressure. I may find
> some motivation for that... maybe...
>
> Even
>
> --
> http://www.spatialys.com
> My software is free, but my time generally not.
>
> _______________________________________________
> Tiff mailing list
> [email protected]
> https://lists.osgeo.org/mailman/listinfo/tiff
>
_______________________________________________
Tiff mailing list
[email protected]
https://lists.osgeo.org/mailman/listinfo/tiff

Reply via email to