How to manage the evolution of the Bloc API?

[labordep]

The Bloc API is undergoing development.
How can we effectively manage long-term changes (e.g., Bloc v1, v2, etc.) to ensure compatibility with previously saved views?
This challenge also extends to the upcoming Toplo serialization project.

[Nyan11]

Same issue : OpenSmock/Pyramid#151

[LabordePierre]

@Nyan11 I think that we can close this issue.

[Nyan11]

I like the idea to add meta-datas to a Pyramid Project.
For example,

• who created this project,
• when it was created,
• when it was modified,
• who work on it (we should think also about the risk/security of such information).

Maybe the meta-datas should includes the different bloc and toplo version.
It is painful to download a project an cannot be able to start it because Bloc and Toplo have evolve so much.

[LabordePierre]

I like this idea too. I will create a specific issue to work on that.