If you are working on an in-house project you probably won't want to release it to CPAN. In that case you are welcome to skip this part. However even it that case it might be useful for you to know how modules can be packaged for CPAN. After all even for in-house project you might set up a private CPAN repository injecting your modules. For that case it is a good idea to know how to package the code.
Some people will say it is too early to make an official release. After all we can only parse a very limited Markua syntax.
So why do I release it anyway and how do I do it?
Perl Maven Pro - screencasts with articles
As a Perl Maven Pro subscriber you will enjoy a growing library of articles and screencasts.
Two screencasts a week and all the previous screencasts!
Ad free browsing!
The articles contain topics such as Web Application Development, Object Oriented programming, testing, deployment, code walkthroughs, best practices, and many more subjects in Perl, and in related technologies.
The related technologies over HTML5, CSS3, JavaScript, Git, Subversion, vim, Unix/Linux shell, SQL and NoSQL just to name a few topic that I, as a Perl programmer find useful.
Subscriptions include all previous pro episodes.
In order to subscribe to the Perl Maven Pro, first register and login to the web site, and then pay via PayPal:
or
If you already have Perl Maven Pro subscription, you will need to login to access the articles.
Gabor who runs the Perl Maven site helps companies set up test automation, CI/CD
Continuous Integration and Continuous Deployment and other DevOps related
systems.