Beefy Boxes and Bandwidth Generously Provided by pair Networks
The stupid question is the question not asked
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
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":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others cooling their heels in the Monastery: (6)
As of 2024-03-28 21:23 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found