increment $VERSION after 0.31 release
[p5sagit/Try-Tiny.git] / CONTRIBUTING
CommitLineData
cb57845a 1
2CONTRIBUTING
3
4Thank you for considering contributing to this distribution. This file
5contains instructions that will help you work with the source code.
6
7PLEASE NOTE that if you have any questions or difficulties, you can reach the
8maintainer(s) through the bug queue described later in this document
9(preferred), or by emailing the releaser directly. You are not required to
10follow any of the steps in this document to submit a patch or bug report;
11these are just recommendations, intended to help you (and help us help you
12faster).
13
14The distribution is managed with Dist::Zilla (https://metacpan.org/release/Dist-Zilla).
15This means than many of the usual files you might expect are not in the
16repository, but are generated at release time (e.g. Makefile.PL).
17
18However, you can run tests directly using the 'prove' tool:
19
20 $ prove -l
21 $ prove -lv t/some_test_file.t
22 $ prove -lvr t/
23
0a844ed9 24In most cases, 'prove' is entirely sufficient for you to test any patches you
25have.
cb57845a 26
27You may need to satisfy some dependencies. The easiest way to satisfy
28dependencies is to install the last release -- this is available at
29https://metacpan.org/release/Try-Tiny
30
31If you use cpanminus, you can do it without downloading the tarball first:
32
33 $ cpanm --reinstall --installdeps --with-recommends Try::Tiny
34
35Dist::Zilla is a very powerful authoring tool, but requires a number of
36author-specific plugins. If you would like to use it for contributing,
37install it from CPAN, then run one of the following commands, depending on
38your CPAN client:
39
40 $ cpan `dzil authordeps --missing`
41or
42 $ dzil authordeps --missing | cpanm
43
44You should then also install any additional requirements not needed by the
45dzil build but may be needed by tests or other development:
46
47 $ cpan `dzil listdeps --author --missing`
48or
49 $ dzil listdeps --author --missing | cpanm
50
51Or, you can use the 'dzil stale' command to install all requirements at once:
52
53 $ cpan Dist::Zilla::App::Command::stale
54 $ cpan `dzil stale --all`
55or
56 $ cpanm Dist::Zilla::App::Command::stale
57 $ dzil stale --all | cpanm
58
59You can also do this via cpanm directly:
60
61 $ cpanm --reinstall --installdeps --with-develop --with-recommends Try::Tiny
62
63Once installed, here are some dzil commands you might try:
64
65 $ dzil build
66 $ dzil test
67 $ dzil test --release
68 $ dzil xtest
69 $ dzil listdeps --json
70 $ dzil build --notgz
71
72You can learn more about Dist::Zilla at http://dzil.org/.
73
74The code for this distribution is hosted at GitHub. The repository is:
0a844ed9 75
b4b13135 76https://github.com/p5sagit/Try-Tiny
0a844ed9 77
cb57845a 78You can submit code changes by forking the repository, pushing your code
0a844ed9 79changes to your clone, and then submitting a pull request. Please include a
80suitable end-user-oriented entry in the Changes file describing your change.
81Detailed instructions for doing that is available here:
cb57845a 82
83https://help.github.com/articles/creating-a-pull-request
84
0a844ed9 85All pull requests for this distribution will be automatically tested on Linux
86by Travis at: https://travis-ci.com/p5sagit/Try-Tiny
87Results will be visible in the pull request on GitHub. Follow the appropriate
88links for details when tests fail. Changes will not be mergeable until all
89tests pass.
90
cb57845a 91If you have found a bug, but do not have an accompanying patch to fix it, you
92can submit an issue report here:
93https://rt.cpan.org/Public/Dist/Display.html?Name=Try-Tiny
94or via email: bug-Try-Tiny@rt.cpan.org
95This is a good place to send your questions about the usage of this distribution.
96
97If you send me a patch or pull request, your name and email address will be
98included in the documentation as a contributor (using the attribution on the
99commit or patch), unless you specifically request for it not to be. If you
100wish to be listed under a different name or address, you should submit a pull
101request to the .mailmap file to contain the correct mapping.
102
103
0a844ed9 104This file was generated via Dist::Zilla::Plugin::GenerateFile::FromShareDir 0.015
105from a template file originating in Dist-Zilla-PluginBundle-Author-ETHER-0.161.