Skip to content

Should we spin clojure-test-mode into a separate project? #214

@bbatsov

Description

@bbatsov

Half the issues are currently tagged as clojure-test-mode issues. I think it would make sense to promote clojure-test-mode to a separate project (repo) to avoid cluttering the clojure-mode issue tracker. As a stand-alone project clojure-test-mode is also likely to be documented better, as currently it doesn't make sense to write too much about in clojure-mode's README. There's also the fact that by keeping both modes in the same repo it looks like that we're encouraging users to use clojure.test, which doesn't seem totally right.

The transition would be fairly simple:

  • New repo in the organisation named clojure-test-mode
  • Update of the MELPA recipe to use the new repo
  • Update the el-get recipe
  • Manual copying of the outstanding tickets to the dedicated issue tracker

Thoughts?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions