TagLib's future

[Sander Jansen]

I don't think closing a request is that necessary, but may be adding a
comment whether it should be applied to master before or after release. In
that respect, it would have been nice if github allowed you to add labels
to your own pullrequests. (or perhaps a taglib admin setting)

Sander



On Tue, Jun 23, 2015 at 1:45 PM, Tsuda Kageyu <tsuda.kageyu at gmail.com>
wrote:

> Hi Sander,
>
> 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.)
>
> Regards,
> Kageyu
>
> 2015-06-24 3:14 GMT+09:00 Sander Jansen <s.jansen at gmail.com>:
>
>>  Kageyu,
>>
>> I think your never ending stream of pull requests have some really nice
>> changes, however it doesn't feel like it is getting us closer to any new
>> release.
>> What's holding us back from releasing the current master branch? How
>> about "feature / cleanup / refactor" freeze and just focus only on bugfixes
>> (flac id3v1 comes to mind).
>>
>> Sander
>>
>> _______________________________________________
>> taglib-devel mailing list
>> taglib-devel at kde.org
>> https://mail.kde.org/mailman/listinfo/taglib-devel
>>
>>
>
> _______________________________________________
> taglib-devel mailing list
> taglib-devel at kde.org
> https://mail.kde.org/mailman/listinfo/taglib-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/taglib-devel/attachments/20150623/b8ca1255/attachment.html>