What should be included in 1.0

[Arun Chandrasekaran]

On Mon, Mar 12, 2018 at 10:54 AM, Dominik Ruf <dominikruf at gmail.com> wrote:
> Hi all,
>
> we discussed in the past that we are long over due to release a new version.
> We also agreed that we should strongly push towards a 1.0 release.
> Since this may attract new users, I think we should carefully think about
> what should be included in this release. There is only one chance for a
> first impression.
>
> These are the things, I believe, the users will expect and therefore should
> be included in the 1.0 release.
>
> 1. attractive UI
> We are not there yet, but close(r)
> 2. ssh support
> There is an old PR for this. I made some fixes and started to and some
> tests. I'll create a PR soon.
> 3. manage hooks (incl. custom hooks) on a repository and repository group
> bases
> I have an old PR about this as well.
>
> Of course YMMV, but I think we should discuss this.
>
> cheers
> Dominik
>
> P.S.: Like I mentioned before, I think we should use a proper project
> management tool, to keep track of things like this. Since you guys don't
> like JIRA, because it is not open source, does somebody know
> https://www.openproject.org? @andrew maybe you know it?
>
> _______________________________________________
> kallithea-general mailing list
> kallithea-general at sfconservancy.org
> https://lists.sfconservancy.org/mailman/listinfo/kallithea-general
>

Talking from mercurial point of view, it would be fantastic to have a
feature to to strip the changesets from the changelog view. We mostly
use the fork and work model. `hg strip` on remote will void the need
to use evolve and would simplify the loop with just histedit, rebase
and strip on the client side.

Git allows remote branch deletion by default, so this may not be
required after all for git repos.