Release schedule #500
Replies: 1 comment 3 replies
-
That's a good point. So far, my strategy has been to delay putting out a new release for two or three weeks after a Pull Request has been merged in case another change gets accepted that could be included in the same release. So far, this resulted in 3-5 releases per year as there isn't that much active development going on. It seems like I forgot to set a reminder for myself after the commits to TinyDB in last July and November. Maybe, a better strategy would be to have a recurring release date (e.g. monthly) and just skip releases that wouldn't contain any changes. But that would introduce more delay for changes that just didn't make it in time. And also I don't know if I can guarantee that I'll be able to make time on a fixed day in order to prepare a new release. At any rate, I'll put together a new release in a couple of minutes. |
Beta Was this translation helpful? Give feedback.
-
I see it's coming up on a year since last release, any plans for a new one?
6ef791e...master
Beta Was this translation helpful? Give feedback.
All reactions