in reply to Keeping unreleased modules in a CPAN repo?

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.

Replies are listed 'Best First'.
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]

In Section Seekers of Perl Wisdom