Hi David! On Tuesday, December 30, 2014 4:01:27 PM UTC-6, David James wrote: > > 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. > > We don't work from fixed dates. I think we are currently on a track towards a 1.7 final release in Q1. Everything currently targeted towards 1.7 can be seen in this report: http://dev.clojure.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=10519 which is what I am currently working from on a daily basis. There are some tickets in that list that I have added without Rich's approval, but that I believe are essential to other vetted tickets or established goals. Some of those may be removed in the next round of review with Rich.
At this point the major "feature" drivers are transducers and feature expressions. The majority of the tickets remaining revolve around shoring up various aspects of transducers. > > - 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. > > Things change enough on a daily basis that it's hard for there to be a concrete list pointing to specific tickets. I sometimes ask for help on the clojure-dev mailing list when I need that kind of focus. Some things that come to mind right now for 1.7: - review or feedback of any patch still on the 1.7 list is useful, particularly ones that have not yet been screened - CLJ-979 and CLJ-1544 are not related to any of our release goals but are imho important enough to consider for addition at this time. These are the most likely to be chopped out of this list when Rich reviews it. Having a) a list of places where they help and b) a list of places where they don't hurt is particularly important. Review or alternative approaches would also be useful. - Test and use of feature expressions would be particularly helpful - see: https://github.com/levand/fx-hello-world for probably the best way to try them out Beyond 1.7, I recently re-prioritized the Triaged <http://dev.clojure.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=10370> list for 1.8 and anything at the higher-priority ends of Defects and Enhancements are good places to work on patches or give feedback for 1.8. Feature work for 1.8 is likely to be anything on the Releases.Next page that's not currently in or planned for 1.7 but it's pretty hard to suggest a useful way to work on most of that right now. > > - 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)? > > We work with the following meanings: Alpha - in dev, not yet "feature complete", may make breaking changes in new features Beta - "feature complete" - we think all new features are in, may still fix bugs found RC - all tickets fixed, potential release pending critical bugs At the moment, I think feature expressions is the long pole for beta, although I believe the patches currently cover the majority of what's proposed. My personal hope is that we can go beta in mid-January. I expect a period to contemplate the fx changes and drive enough tooling updates to consider it further and see what comes out. > > - 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://www.google.com/url?q=http%3A%2F%2Fdev.clojure.org%2Fjira%2Fsecure%2FTaskBoard.jspa%3FselectedBoardId%3D%26pageType%3DChartBoard%26subType%3DArchiveChartBoard%26type%3DACB%26selectedProjectId%3D10010%26colPage%3D1&sa=D&sntz=1&usg=AFQjCNHGflUEaukqXKUMUsJbXkvrxBlOnA> > . > > I'd refer to the 1.7 report I linked above as that's what Rich, Stu, and I are working from. Alex -- 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.
