Getting ready for 0.9

Development
1

Happy new year fellow pijulers,
do we have a planning for the release of 0.9. In particular, given that we should undergo a format change, we need to:

  • release a 0.9 tarball
  • switch the nest to pijul-0.9
  • state what the migration story is

Which of these are ready, and what is left to do for the other ones?

2

Sorry for not communicating properly on this. I’m almost done with everything “I” wanted (as in, everything people have suggested that looks feasible for the next release).
I have a NixOS version that compiles (required fixes in carnix), and a Windows version that compiles. I’m currently adding support for SSH agents, and that should be it.

We had an interesting discussion with @lthms about show-dependencies: detecting missing contexts symmetrically (the “zombies” tests) requires the dependencies field of patches to include the direct dependencies, even if transitivity makes them redundant.

However, this forces us to do some extra work (essentially, a topological sort) every time we want to show dependencies to the user, either on the Nest, or with show-dependencies.

There are several options:

  1. do the extra work every time, it’s O(|B|), where B is a branch (set of patches).
  2. add an extra field for “zombie dependencies”, and test thoroughly again.
  3. add an extra field for “minimised dependencies” just for the sake of displaying.

In general, I don’t like adding new fields (so I’m slightly in favor of option 1), and I believe @lthms would prefer option 3.

3

You summarised it right. :slight_smile:

Also, what is the status of the pijul converter, from 0.8 to 0.9?

4

I believe I’ve fixed it since we last talked, but I still need to test it at a larger scale, like on Pijul itself, and then on all repositories on the Nest (this last task is actually more than a test, I’ll need to do it).