it's not very inviting to go on GitHub and see all the CPAN related modules

What an odd thing to think. I take the opposing view.

how much work and effort should go into customizing a release for GitHub as compared to CPAN?

Github is not a release channel, it is a publicly-accessible, managed VCS repository.

is Pod::Weaver the best way to autogenerate the pod or is it easier just to rely on a default template that you modify?

Autogenerating POD is lazy and not in a good way, so don't do that.

Also, some more basic questions: when do you commit to GitHub vs. releasing to GitHub and CPAN?

See above, you don't "release to github".

I was wondering if I could get some basic advice and hear how others are using Dist::Zilla/CPAN/GitHub to try to find an optimal software release solution.

Optimal in terms of what, exactly? Fewest bugs or most extensive documentation or easiest for others to contribute or efficient for you as release roller or most structured commit logs or ... ?

Perhaps it's time to heed what almost everyone has been suggesting and stay away from Dist::Zilla until you've answered all the questions you posed to your own satisfaction. It doesn't seem to be helping you. Good luck.

In reply to Re: What are your best practice recommendations for maintaining CPAN module with GitHub repo? by hippo
in thread What are your best practice recommendations for maintaining CPAN module with GitHub repo? by nysus

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.