Re^2: Version Control - GitHub and CPAN

Is this the sort of thing you would expect to see?

Do I need to make a 'release' or 'package'?
Do they set the point at which development becomes a version?

Comment on Re^2: Version Control - GitHub and CPAN

Replies are listed 'Best First'.
Re^3: Version Control - GitHub and CPAN by choroba (Cardinal) on Jun 20, 2023 at 09:55 UTC
The common practice is to tag the commit that made it into a release with something like "cpan-1.0.1". `map{substr$_->[0],$_->[1]\|\|0,1}[\\|\|{},3],[[]],[ref qr-1,-,-1],[{}],[sub{}^ARGV,3]`	[reply] [d/l]
Re^3: Version Control - GitHub and CPAN by hippo (Archbishop) on Jun 20, 2023 at 09:29 UTC
Is this the sort of thing you would expect to see? That looks fine to me :-) Do I need to make a 'release' or 'package'? On github? No, I would not bother. You have PAUSE and CPAN for that. So long as your repo includes the user-level instructions for obtaining and installing (which it does right there in the README.md) there's no need AFAICS to duplicate the release effort. Do they set the point at which development becomes a version? Github? No, I cannot see how or why they would. 🦛	[reply]