News for hackers. Stuff that matters.
Re:Show HN: Ship – A fast, native issue tracker for software... by dragonwriter on Friday January 29, 2016 @01:36PM (#10997357)
> Some of the issues shown on the site seem like what I would call features as opposed to bugs. Is it a different use case? Does it work to have software "features" in Jira or Trello or similar and then use an issue tracker like Ship for just the bugs?

"Features" and "bugs" are essentially the same thing: differences between the current and desired state of a piece of software.

Tracking them in separate tools seems to be a bad idea.

Re:Show HN: Ship – A fast, native issue tracker for software... by clay_to_n on Friday January 29, 2016 @03:58PM (#10998442)
That makes sense. My next question then would be: Can you use Ship or some other issue tracker to manage the software lifecycle reasonably? Planning for a sprint or release, development, code review, QA, etc. I'm used to having these as columns in Trello or Jira - is the alternative to do them as labels or similar? Or would you use some other tool for them?
Re:Show HN: Ship – A fast, native issue tracker for software... by hockeybias on Friday January 29, 2016 @01:42PM (#10997405)
Agreed. That is how we do it (with FogBugz).