how much work and effort should go into customizing a release for GitHub as compared to CPAN?
You're confusing deploying and releasing. You deploy changes (patches) to your module via GitHub, and you release versions (tarballs) to your users via CPAN.
Because GitHub is far more than just a git repository host, GitHub can technically be used to host releases as well, but noone does that —at least not exclusively— because cpan won't find them.
On the other hand, some people use GitHub as their bug tracker instead of rt.cpan.org. You can specify your preferred bug tracker in your release's (distribution's) META file.
-
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.
|
