Release planning 0.9.0

[valoq]

I would like to suggest we plan the upcoming feature release and what should be part of it.

there are a few PRs that should be merged first and we should review the changes regarding overwriting of files again since there have been a few related changes and its become a bit hard to keep the overview of what the intended behavior should be.

[marcospb19]

I'm favorable to us reviewing the code to try to find remaining overwrite cases, whether they can delete a folder and what the behavior should be.

Let's mention our findings in this thread, if any.

[marcospb19]

suggest we plan the upcoming feature release and what should be part of it

Should we make a smaller release instead of putting everything that's currently on main?

[marcospb19]

A small drawback to this would be: if the user finds a bug on such 0.9.0, we can't simply fix on main, we also need to cheryr-pick into another branch that diverges from main and release from that, which is a little more time-consuming.

[valoq]

suggest we plan the upcoming feature release and what should be part of it

Should we make a smaller release instead of putting everything that's currently on main?

No, I think we should just make this a feature release with everything.
We can then use minor versions to fix things and aim for 1.0.0 to be come the first really stable release at the end of the year or so.
So basically we try to get all behavior changing fixes into 0.9.0

[valoq]

Aside from the current open fix PRs we should also update the benchmark.

I ran is just now on the git version (see below), but it would probably make more sense to sue the same system that ran the last version. the

After 0.9.0 is released, we should add a security policy for reporting issues as well in preparation for 1.0.0
Maybe there is already a github bot that would track the advisories in the dependencies to help with that, also to be merged witht eh 1.0.0 release

Maybe we can aim for 0.9.0 until the end of this month

Benchmark on a development workstation:

Command	Mean [ms]	Min [ms]	Max [ms]	Relative
ouch compress rust output.tar	364.1 ± 5.9	358.5	376.5	2.22 ± 0.04
tar -cvf output.tar rust	164.2 ± 1.9	161.7	168.1	1.00

Command	Mean [ms]	Min [ms]	Max [ms]	Relative
ouch decompress input.tar --dir output	669.4 ± 8.2	657.8	683.3	2.50 ± 0.07
tar -xv -C output -f input.tar	267.3 ± 7.0	259.8	279.1	1.00

Command	Mean [ms]	Min [ms]	Max [ms]	Relative
ouch compress compiler output.tar.gz	35.4 ± 1.0	32.6	37.2	1.00
tar -cvzf output.tar.gz compiler	350.0 ± 1.2	348.5	352.1	9.87 ± 0.29

Command	Mean [ms]	Min [ms]	Max [ms]	Relative
ouch decompress input.tar.gz --dir output	69.2 ± 2.7	67.2	82.2	1.55 ± 0.08
tar -xvz -C output -f input.tar.gz	44.6 ± 1.6	42.8	51.5	1.00

Command	Mean [ms]	Min [ms]	Max [ms]	Relative
zip output.zip -r compiler	340.6 ± 1.4	338.4	342.6	1.74 ± 0.02
ouch compress compiler output.zip	196.1 ± 2.0	193.5	199.3	1.00

Command	Mean [ms]	Min [ms]	Max [ms]	Relative
ouch decompress input.zip --dir output	75.8 ± 1.0	74.5	79.0	1.00
unzip input.zip -d output	123.1 ± 3.3	120.7	137.3	1.62 ± 0.05

Old benchmark: https://github.com/ouch-org/ouch/blob/main/benchmarks/results.md

[valoq]

The overwrite issues should all be handles now (once the open PRs are merged).
Additional reviews would be appreciated but I think we can do the 0.9.0 release with this