Biicode Version Bits - Overwrite versions when published

Question

I published on biicode using only DEV and STABLE tags. If I do not understand, for this block, it seems that I can publish the DEV version as many times as I like, and my previously published code will be overwritten with the new version every time. On the contrary, it seems that I can only publish the STABLE version once, and I cannot overwrite the code published under this tag.

I was wondering how other tags behave. Can the versions of ALPHA and BETA be overwritten, or can I publish them only under these tags only once?

Thanks!

Demetrius

Answer 1

All versions, but DEV alone, are not verifiable; they are frozen after publication. The goal is to achieve full reproducibility. Changing their content or their tags would alter what consumers of this code use effectively. For the same reason, DEV versions that can be overwritten cannot be marked.

So yes, ALPHA and BETA behave exactly like STABLE. Their name is just an indicator for the target audience. The idea when you publish the ALPHA version is that you want your teams and employees to test it. I would tag them like @ 1.2test1, @ 1.2test2 and so on. BETA variants are intended for community testing, probable tags can be released by @ 1.2rc3 candidates, and STABLE versions for production, you can mark them as @ 1.2 (and possibly create minors with @ 1.2.1

Note: @ is not required in the team, I think the actual team

$ bii publish user / block --tag = BETA --versiontag = 1.2rc3

For now, you can specify it in your configuration file as:

user / block @ 1.2rc3

This should find it and add the publication index, for example:

user / block: 3 @ 1.2rc3