Skip to content

remove references to Jira from the wiki #27

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 4, 2016
Merged

remove references to Jira from the wiki #27

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 0 additions & 13 deletions wiki/faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,19 +19,6 @@ there are still gaps.

You can find them via the *resources* tab just above this page.

#### Will I have to register a Jira account to submit issues?

Yes, you will need to provide a name and email address.

#### Why are you using Jira instead of Github Issues? It seems more complicated.

Jira **is** a bit more complicated than github's bug tracker, and it's certainly
not perfect. It is, however, a lot better suited to managing and planning a
project of this size. Cloud Haskell consists of no less than **13** individual
projects at this time, and that's not to mention some of the experimental ones
that have been developed by community members and *might* end up being absorbed
by the team.

### Help

If the documentation doesn't answer your question, queries about Cloud Haskell
Expand Down
4 changes: 2 additions & 2 deletions wiki/maintainers.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ process and in particular, the branching strategy. We also point out Cloud Haske
various bits of infrastructure as they stand at the moment.

Perhaps the most important thing to do as a maintainer, is to make other developers
aware of what you're working on by assigning the Jira issue to yourself!
aware of what you're working on by assigning the github issue to yourself!

----
#### Releases
Expand Down Expand Up @@ -132,7 +132,7 @@ you've finished and uploaded the release. If you build and tag three projects,
only to find that a subsequent dependent package needs a bit of last minute
surgery, you'll be sorry you didn't wait. With that in mind....

Before releasing any source code, make sure that all the jira tickets
Before releasing any source code, make sure that all the github tickets
added to the release are either resolved or remove them from the
release if you've decided to exclude them.

Expand Down