benrhughes
commented
5 years ago To be honest there isn't really a plan - it's more about when I find the time to create and test the release.
As for what's included, it will be all the pull requests merged since the last release, which you can find with this query: https://github.com/benrhughes/todotxt.net/pulls?utf8=%E2%9C%93&q=is%3Apr+is%3Aclosed+closed%3A2017-09-23..2019-01-20+ As you can see, there's not a whole lot waiting to be released. I usually hold off until it feels like there's enough in there to justify the effort.
In terms of help, I'm always happy with doco contributions. The other thing that would be more useful (to me, at least) would be beta testing the next release. One of the issues I have is that there are a lot of features that I don't use, so I don't always notice bugs before I let the release out into the wild.
---- On Sun, 20 Jan 2019 08:51:22 +1100 shulist mailto:notifications@github.com wrote ----
https://github.com/benrhughes There have been many references in these issues to the "next release" of TDT. When exactly is the next release planned for? Is there some overall plan of when this might occur and what might be included as far as bugs, features, improvements etc.?
While I am useless at programming I could add some effort into documentation (or the wiki), if that is required, as it seems the documentation for TDT is only in these issues.
— You are receiving this because you were mentioned. Reply to this email directly, https://github.com/benrhughes/todotxt.net/issues/376, or https://github.com/notifications/unsubscribe-auth/AAOUMds4ikx5CrEZBv4cKM25ZbeKClFoks5vE5NagaJpZM4aJWc4.
shulist
@benrhughes There have been many references in this issue log to the "next release" of TDT. When exactly is the next release planned for? Is there some overall plan of when this might occur and what might be included as far as:
Recognizing that as of today there are only 7 issues tagged as "Ready For Work" it would seem that there is some planning effort required to bridge the gap between that and outstanding issues as shown in the list above. While I am useless at programming I could add some effort into documentation (or the wiki), if that is required, as it seems the documentation for TDT is somewhat in the wiki and partly in these issues. I really appreciate the work that has gone into TDT thus far and would like to see it moved to the next level.