2016-02-11 8:07 GMT+01:00 Krzysztof Kosiński <tweenk.pl@...400...>:
2016-02-10 22:45 GMT-08:00 Bryce Harrington <bryce@...961...>:
On Tue, Feb 09, 2016 at 11:55:28AM +0100, joakim@...1974... wrote:
Bryce Harrington <bryce@...961...> writes:
On Fri, Feb 05, 2016 at 09:16:36AM -0800, mathog wrote:
On 05-Feb-2016 05:40, Eduard Braun wrote:
In general I would avoid splitting the code repository from the bug tracker as those two are closely related and often intertwined. It hinders efficiency a lot when tracking bugs elsewhere.
I agree with that - everything in one place. Moving to git is fine
so
long as the entire history of the project makes the transition, all
the
bugs, all the revisions, and so forth. There shouldn't be anything "left behind" on launchpad. Not that I have any idea how one would
go
about doing this sort of migration, never having used git except to download entire projects for a local build.
I'll throw out another thing maybe worth considering is Phabricator
http://phabricator.org/This is a very powerful platform, and highly customizable, providing an integrated solution for bugs, patchreview, and a heap of other stuff as well as git hosting. I've had some limited experience using it on Enlightenment and Wayland, and it gets very high marks from people who use it.
Thanks for the link Bryce, I was looking around for JIRA alternatives for non-Inkscape stuff and phabricator seems like a good candidate.
There do seem to be a lot of parallels between github today and sourceforge back when. SourceForge was also "the standard" at one point, then turned focus entirely to commercialization and kind of stagnated.
This is a valid concern, but it doesn't look too terrible yet. The distributed nature of Git ensures that should anything troublesome start happening, moving the repository elsewhere is trivial.
On the other hand, the GitHub + Travis CI + AppVeyor + Launchpad bug tracker looks like the best combination for now, as long as Inkscape can reliably build on Travis CI servers within their 50 minute time limit. Installation of dependencies is not counted against the time limit on Ubuntu, but is on OSX.
Best regards, Krzysztof
I'm on the same page with you Krzysztof the "GitHub + Travis CI + AppVeyor + Launchpad bug tracker" combination seems like the best option at the moment.
I also asked for suggestions in a Swedish DevOps facebook-group and the feedback I got was to buy a Mac-mini. On that mac-mini OS X builds can be built as well as run Windows VMs and build windows versions of Inkscape. I was already planning to setup some kind CI infrastructure at home so I can build Inkscape on it as well, but I don't have any time estimate when it will be up and running.