Keeping unreleased modules in a CPAN repo?

Dallaylaen has asked for the wisdom of the Perl Monks concerning the following question:

Hello esteemed monks,

Say I have a git repository with a CPAN module. I'd like to add some experimental modules/scripts to it, but they're not yet ready for a release. How do I organize my repository so that (a) new modules don't get released just yet and (b) I can keep track of all the changes?

I think about adding xlib (or elib as xt is occupied by author tests) directory and listing it in MANIFEST.SKIP but maybe there's a more standard way?

Thanks!

Comment on Keeping unreleased modules in a CPAN repo?

Replies are listed 'Best First'.
Re: Keeping unreleased modules in a CPAN repo? by Corion (Patriarch) on Sep 01, 2018 at 06:35 UTC
You can simply choose to not distribute all files from your repository. Depending on what you use to build your distribution, this is as easy as putting the files and directories you want to exclude in your `MANIFEST.SKIP` file. Alternatively, use a different branch for keeping your mixed / experimental development and cherry-pick the changes you want to your release branch.	[reply] [d/l]
Re^2: Keeping unreleased modules in a CPAN repo? by Dallaylaen (Chaplain) on Sep 01, 2018 at 09:02 UTC
Yes, I'm leaning towards `MANIFEST.SKIP`. Having a separate branch has caused me grief in my current workplace when other people kept merging into master and I kept resolving conflicts. I ended up committing unfinished code with `die "unimplemented"; # TODO cover with tests & release` stubs all over it. But maybe that's just me.	[reply]