Packaging current lame CVS snapshot for Debian -- good or bad idea?

Dear lame-devs,

I am (one of the) maintainer(s) of the lame package in Debian:

https://tracker.debian.org/pkg/lame

We are currently packaging the latest stable release 3.99.5 and over
time, we have added more and more patches to our package, most of them
have already been applied in the lame CVS repository as well (thanks
rbrito):

http://anonscm.debian.org/cgit/pkg-multimedia/lame.git/tree/debian/patches

Now that Debian "jessie" has been released, I'd like to prepare a new
Debian package for lame based on a current CVS snapshot, so I can get
rid of most of the patches we currently apply. Do you know of any issues
with the current state of the code in the repository or another reason
why this might turn out as a bad idea? Is there anything that should
keep me from packaging it? Anything I should know?

Thank you very much already!

Cheers,

- Fabian

------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y

_______________________________________________
Lame-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lame-dev