[prev in list] [next in list] [prev in thread] [next in thread] 

List:       taglib-devel
Subject:    TagLib's future
From:       Lukáš Lalinský <lalinsky () gmail ! com>
Date:       2015-05-12 23:20:03
Message-ID: CAGUtLj90U+ErDwSOtnGwKLF+TMB=GFwkBYLLzyyQPeoOuQOGSg () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


Hi all,

Since there are people asking for a new release more and more often and it
seems that I'm not really able to do it, I'd like to discuss TagLib's
future. A few years back Scott asked me to coordinate the 1.6 release and
generally become the maintainer of the project, but since then I have not
worked on many projects that use TagLib and I currently have no direct use
for it myself.

We have have a long list of pull requests on GitHub, a lot of changes in
master and at least one backward-compatible release pending. I find it very
hard to motivate myself to review pull requests, especially if they are
questionable in some way. This was already showing in the last release,
where I didn't take my time to review all the changes properly and the
result was not very good. I'm afraid that if I try to do this new release,
it will end similarly badly.

So I'd like to discuss what would be the best way to go forward.

Lukas

[Attachment #5 (text/html)]

<div dir="ltr">Hi all,<div><br></div><div>Since there are people asking for a new \
release more and more often and it seems that I&#39;m not really able to do it, \
I&#39;d like to discuss TagLib&#39;s future. A few years back Scott asked me to \
coordinate the 1.6 release and generally become the maintainer of the project, but \
since then I have not worked on many projects that use TagLib and I currently have no \
direct use for it myself.</div><div><br></div><div>We have have a long list of pull \
requests on GitHub, a lot of changes in master and at least one backward-compatible \
release pending. I find it very hard to motivate myself to review pull requests, \
especially if they are questionable in some way. This was already showing in the last \
release, where I didn&#39;t take my time to review all the changes properly and the \
result was not very good. I&#39;m afraid that if I try to do this new release, it \
will end similarly badly.</div><div><br></div><div>So I&#39;d like to discuss what \
would be the best way to go forward.  \
</div><div><br></div><div>Lukas</div><div><br></div></div>


[Attachment #6 (text/plain)]

_______________________________________________
taglib-devel mailing list
taglib-devel@kde.org
https://mail.kde.org/mailman/listinfo/taglib-devel


[prev in list] [next in list] [prev in thread] [next in thread]