This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-06-21
Channels
- # announcements (9)
- # beginners (222)
- # boot (11)
- # calva (40)
- # cider (1)
- # clj-kondo (10)
- # cljs-dev (1)
- # cljsrn (8)
- # clojars (4)
- # clojure (50)
- # clojure-dev (4)
- # clojure-ecuador (1)
- # clojure-europe (4)
- # clojure-italy (3)
- # clojure-madison (2)
- # clojure-nl (26)
- # clojure-spec (86)
- # clojure-uk (34)
- # clojurescript (11)
- # clr (1)
- # cursive (46)
- # datomic (19)
- # emacs (4)
- # events (1)
- # fulcro (22)
- # graalvm (4)
- # graphql (2)
- # jobs-discuss (40)
- # leiningen (10)
- # luminus (6)
- # nrepl (7)
- # off-topic (18)
- # onyx (6)
- # overtone (1)
- # pedestal (2)
- # planck (1)
- # re-frame (5)
- # reagent (3)
- # reitit (8)
- # rewrite-clj (2)
- # shadow-cljs (139)
- # sql (4)
- # tools-deps (42)
This page may still have some details specific to old version of JIRA, perhaps: https://clojure.org/dev/workflow In particular, it says 'changing "Patch" attribute to "Code" or "Code and Test"' under the 'Dev patch' heading, but there doesn't seem to be a "Patch" attribute in newer JIRA. There is certainly no rush on updating anything here for me -- just wanted to ask if it is known how I could update the instructions on when a dev adds a patch to a ticket, if that is known yet.
Yeah, there are more changes coming so I’m waiting
Also the creating tickets page says you don't need a Jira account to create a ticket in paragraph one but in paragraph three it says you do need one