The "Clojure JIRA Workflow" page you linked to has several links on it to 'saved JIRA searches', which show only JIRA tickets matching specific criteria. In the "Dev patch" section there are ones for all "Needs a patch" tickets, for example, or all "Incomplete" tickets. For writing patches, the "Needs a patch" list are the ones scheduled for the next release where a patch is desired. That list is empty right now, I believe, because all of the ones that were in that state have had patches written for them, and are waiting to be screened (state "Screenable") or for Rich Hickey's approval (state "Screened").
Any tickets that are not currently marked with a "Fix version" of 1.7 are unlikely to be part of Clojure 1.7, and that list is 19 ticket right now, I believe (look at the links of saved JIRA searches for "Screened", "Screenable", and "Incomplete" tickets). You can save searches as your favorite when you are logged into JIRA, and when you are logged in there is an "Issues" menu near the top left that has a choice "Manage Filters" in it, that will show you all of your favorite filters with a count of how many tickets match them. The last time I made a guess of "probably within 2 to 6 months" for the release of Clojure 1.7, Alex Miller, who is much closer to these things, said it would likely be closer to the low end of that range. I don't think dates are a driving factor. The activity of JIRA tickets tends to be that Clojure contributors create tickets or write and attach patches, add comments, etc., whenever they wish. Alex Miller and other screeners evaluate screenable tickets to decide whether they should become Screened or not, on their schedule, and Rich Hickey tends to pick a day roughly every month or two to look at a bunch of screened tickets all at once (or earlier in a release cycle, to look at a bunch of triaged tickets to decide whether to mark them Vetted or not). I'm not sure whether having a "ticket of the week" would generate much interest, but I haven't seen it tried, either. Probably the most useful feedback for the alpha/beta releases are "this seems to be a bug in this release that wasn't in a previous release" and "performance for this commonly used construct is much worse in this release than in previous ones". Also useful is "we tried the latest Clojure release on Clojure code base X, and everything is working as expected." Andy On Tue, Dec 30, 2014 at 2:01 PM, David James <davidcja...@gmail.com> wrote: > I'm curious about the future Clojure 1.7 release. I recently looked over > these pages: > > - Clojure JIRA Workflow > <http://dev.clojure.org/display/community/JIRA+workflow> > - Contributing to Clojure > <http://dev.clojure.org/display/community/Contributing> > - Next Release Planning > <http://dev.clojure.org/display/design/Release.Next+Planning> > - Clojure Changelog > <https://github.com/clojure/clojure/blob/master/changes.md> > - Screening Tickets > <http://dev.clojure.org/display/community/Screening+Tickets> > - JIRA Road Map > > <http://dev.clojure.org/jira/browse/CLJ#selectedTab=com.atlassian.jira.plugin.system.project%3Aroadmap-panel> > (currently showing that 54 of 73 issues have been resolved) > > My questions are: (Please let me know if I've overlooked links to read.) > > - Does Rich or Clojure Core have rough dates in mind for the 1.7 > release? Any idea? (I wouldn't be surprised at all if dates were not at all > a driving factor.) From what I can tell, bug fixes, a fixed set of new > features, performance, and stability are the driving factors. > - Do the above links about cover it and/or are there additional > suggestions where community help is most needed? > - Is there a good "I want to help, what do I do next?" page? I see > that http://clojure.org/contributing has some suggestions; namely, > using the mailing list. Also, the "Screening Tickets" link above is a > great > example. > - An idea: I suspect there may be value for a link or blurb (from > the Clojure home page) that would focus attention onto one or two "hot" > issues each week. I say this because JIRA does not seem to be geared > towards driving a critical mass to one ticket at a time -- but sometimes > this is a great way to get the eyes you need on an issue. > - Clojure 1.7 is alpha now. I'm curious: how much feedback does our > BDFL like/need to move across the various stages (alpha, beta, release > candidate, release)? > - Just for fun, if we were to make a data-driven prediction on the > next release, what parts of JIRA do you think are most important to > consider? This is probably the best summary I've seen so far: Clojure > JIRA Clojure Text Board for Release 1.7 > > <http://dev.clojure.org/jira/secure/TaskBoard.jspa?selectedBoardId=&pageType=ChartBoard&subType=ArchiveChartBoard&type=ACB&selectedProjectId=10010&colPage=1> > . > > P.S. I'm building a useful list of terms/acronyms: > > - BDFL: Benevolent Dictator For Live (a.k.a Rich) > - JIRA: "We originally used Bugzilla for bug tracking and the > developers in the office started calling it by the Japanese name for > Godzilla, Gojira ... then it became an issue tracker, the name stuck, but > the Go got dropped - hence JIRA! ... Further investigation into the > name has revealed that Gorira is Japanese for "gorilla", whilst Kujira is > Japanese for "whale". So Gojira is roughly translated to mean "*gorilla > the size of a whale*" (from What does JIRA mean? > <https://confluence.atlassian.com/pages/viewpage.action?pageId=223219957> > ) > > -- > You received this message because you are subscribed to the Google > Groups "Clojure" group. > To post to this group, send email to clojure@googlegroups.com > Note that posts from new members are moderated - please be patient with > your first post. > To unsubscribe from this group, send email to > clojure+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/clojure?hl=en > --- > You received this message because you are subscribed to the Google Groups > "Clojure" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to clojure+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
