festushagenlists at yahoo.com
Thu Jun 25 17:19:34 UTC 2015
It would be nice if the requester could assign predefined labels to their own pull requests ... I do like having only 'minor' and 'wishlist', no 'critical'.
Silence uint ambiguity errors in tests, Is my only pull request that should be in the next release, the rest are trivial wishlists items, the only one that could cause an issue is Append TIME to TDRC ..., I do not _know_ the big picture of affect, I'm not as fluent as most of y'all.
Thanks for doing what y'all do ...
----- Original Message -----
From: Scott Wheeler <wheeler at kde.org>
To: taglib-devel at kde.org
Sent: Wednesday, June 24, 2015 12:55 AM
Subject: Re: TagLib's future
On Jun 23, 2015, at 8:45 PM, Tsuda Kageyu <tsuda.kageyu at gmail.com> wrote:
> First, I agree with you it's good to freeze the changes at a certain point or just now. Many people are awaiting the next release.
> Certainly, I have been making a lot of pull requests that may delay the progress of the project. However, I don't think they have to necessarily merged into the next release. How about closing the non-urgent pull request for now? (Privately, I hope "length in milliseconds" feature be merged.)
Yes, and for a little context, I told Lucas a few weeks back that I could help with the next release and began going through the open requests, getting through about half of the ones that were open at the time. However, during the last few weeks there have been so many new requests opened (and many of them closed again) that I haven't had time to even read them, much less review them. There have been 6 new pull requests and 39 messages just in the last 24 hours.
It would probably be good if new pull requests being opened that are not critical for the next release could be tagged that way. I'd suggest (based on the old KDE bug tagging system) that they be either tagged as "minor" or "wishlist" for things that aren't actually critical.
taglib-devel mailing list
taglib-devel at kde.org
More information about the taglib-devel