[llvm-dev] [RFC] Helping release management
Renato Golin via llvm-dev
llvm-dev at lists.llvm.org
Wed May 4 13:15:53 PDT 2016
On 4 May 2016 at 19:35, Tom Stellard via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
> I think phabricator could probably be the best tool for managing
> releases, because it is integrated with source control and already has
> information about all the commits, but it does not currently have the
> right tool/features to make this work.
I personally don't like Phabricator that much. It's not really
integrated with the code. For instance, it has no idea which project
the commit is on, it doesn't have the context (we need to diff -U999),
etc. Compared to GitHub, Phab is very primitive.
I also don't like it that we have to use special tools to interact
with it. Both GitHub and GitLab work with plain git and a very nice
web interface. I find Phab's interface very confusing.
> Hans mentioned in another email about using Bugzilla, and I think this
> is a good idea. If we required users/developers to file a bug for each
> patch they wanted merged, then it would be really easy to track.
Bugzilla is as good as any other. Not suited to the task, but equally
not-so-bad at providing the functionality we need. Either Phab or
Bugzilla would have to be customized to have release management in
them, and I don't think we want that.
I know we can't use GitHub or GitLab because of the SVN repo, but it
would be good to have a tool that actually does release management and
code review in a clear and simple way.
More information about the llvm-dev