No such thing as a small change | |
PerlMonks |
Re: What are your best practice recommendations for maintaining CPAN module with GitHub repo?by stevieb (Canon) |
on Dec 18, 2017 at 21:02 UTC ( [id://1205820]=note: print w/replies, xml ) | Need Help?? |
I wouldn't call it "mirroring" per-se. Github is where the modifications are stored, CPAN where the final product for each release goes. I have a few pre-configured files that get brought into each project I create, primarily a .gitignore and a MANIFEST.SKIP. Each manages to ignore the files that aren't relevant to its own process. Very rarely to I have to edit these files to make it specific to a project. I do my work in my repo, then when all tests pass (most projects uses Travis-CI and/or Appveyor along with Coveralls.io. Some can't because they rely on external functionality or specific hardware, so I have my own in-house unit test automation software as well. Once all tests pass across the board, I do one last update to changes (essentially putting today's date in the current change log entry), tag it as a release, do a make dist, and upload it to the CPAN. Immediately after that process, I put a new entry in my change log:
...bump my version numbers in the required files, do a commit bumped ver to 0.31 and start the process over again. When I look at my code on the CPAN for a specific release, it will be exactly the same when I look at the release tag for the software in Git/Github. Of course that's a quick overview, but that's how I go about it. It's such a memory process from dist start through publishing that it isn't even worth me automating anything beyond that. It may help if you explained what you'd *like* to see the process look like first, lay that out for us, then get guidance on specific pieces, instead of starting without any idea/plan which is very difficult indeed.
In Section
Seekers of Perl Wisdom
|
|