Split ztree-dir and ztree-diff to different projects

[fourier]

Since the ztree-dir was just a proof-of-concept for ztree-diff, but it keeps its own dedicated users, probably it is better to split these 2 projects and develop ztree-dir as a stand-alone project with more intensive pace to add more features (like nerd-tree for vim or stand-alone x-tree dos app )? Any opinions from users of ztree-dir ?

[rchar01]

I was looking for a module that, apart from the usual directory tree, would also have the option of showing differences in trees. Therefore, even if the project were divided I would use dir and diff.

From what I noticed ztree (dir and diff) has common parts.
Is it beneficial to separate (duplicate) these parts?

[fourier]

It will make it easier to add different features to different projects, without caring how it affect another project. Currently they are quite tightly coupled so its not that easy to do.

[rchar01]

So there will be two packages for the elpy and melpy (e.g. ztree-dir and ztree-diff), right?
Will the ztree project on github also be divided, or there will be one repository?

[fourier]

No, I think it will still be the same package, just internally they could be splitted.

[rchar01]

I think that the change will be good for the project.
As you wrote, it will be easier to make changes, there will be one package like now, so I think there is nothing to lose. I will check and report if errors appear.

Will the beta package be introduced for verification before the implementation of the final version?

[fourier]

I consider deploying to GNU ELPA as a release and rolling on MELPA as a "beta".