* should we move the Kawa's bug-tracker to gitlab?
@ 2016-11-27 6:34 Per Bothner
0 siblings, 0 replies; only message in thread
From: Per Bothner @ 2016-11-27 6:34 UTC (permalink / raw)
To: kawa
I think the answer is 'yes" - it doesn't really make sense to use
gitlab for git hosting unless we also use it for bugs/issues.
If for no other reason than people will do so regardless ...
(Though I have mixed feelings about the "pull/merge request" way of working
- and we will always accept old-fashioned patches, we should also
accept merge requests on gitlab which suggests also using their issue tracker.)
For now let's call it an experiment: feel free to report bugs and
issues at: https://gitlab.com/kashell/Kawa/issues
Likewise feel free to host merge requests (pull requests) there.
If the experience is satisfactory I will update the manual
with the above link as where people should report and browse bugs.
I have no plans to migrate the old bugs from Savannah - I don't
know any practical way to do that.
There is nothing very wrong with Savannah's bug tracker,
and in some ways it is more elegantly minimalist and efficient.
However, I think most people would prefer gitlab's.
--
--Per Bothner
per@bothner.com http://per.bothner.com/
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2016-11-27 6:34 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-11-27 6:34 should we move the Kawa's bug-tracker to gitlab? Per Bothner
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).