Ah, indeed I did. Using App::Mi6 is so ingrained in me (and before that "cpan-upload"), that it is hard for me to imagine any other situation :-)
Liz > On 10 Jul 2022, at 21:41, Vadim Belman <vr...@lflat.org> wrote: > > Hi, > > Liz has probably missed the point of your question. Yes, you must do fez > upload for each new release. It means each time you'd need to do some > pre-release preparations to create an archive, etc... The fastest way is to > switch to App::Mi6 for building distributions. My approach is a makefile plus > helper scripts I include as a submodule for nearly each project I develop > because mi6 doesn't cover my needs. > > Best regards, > Vadim Belman > >> On Jul 10, 2022, at 11:38 AM, Richard Hainsworth <rnhainswo...@gmail.com> >> wrote: >> >> I have begun uploading modules to fez. >> >> Suppose a module is in active development. And I have v0.7.1, then v0.7.2 >> etc. Do I need to upload each version, or will fez automatically provide the >> most updated module? >> >> When p6c was the main ecosystem, the reference was to github. So, the latest >> version on github was used, and zef would use whatever was on github. >> >> >
