Whacky idea - is there a way for people to submit snippets which are run as part of the CI process? The obvious answer is do expect each developer to do this themselves but not everybody has that possibility and it provides very very little feedback to the clojure team.
I am thinking a service which allows me to upload a small clojure project (made using lein for example) which is then run as part of the CI process on Git clojure checkins. Failures wouldn't stop the build but it would notify the submitter that their code no longer worked as expected... The main benefit to clojure is that failures in those snippets/mini projects *might* indicate an untested but valid usecase. It might also indicate that somebody is doing something wrong :). Regardless, I do think knowing that a significant number of uploaded projects failed is very interesting....indicating either a bug in clojure or the need to community training... As an aside, it might also be an excellent library of examples... Dunno - what do you think? Sent from my iPad On 30 Oct 2011, at 15:52, Bill Robertson <billrobertso...@gmail.com> wrote: > I'm new, so forgive me if this is a bad question. Are the snapshots > announced here? Or is it a continuous process? I cloned the repo from > github, and it built as 1.4.0 snapshot, if a maven/ivy/lein user > wanted that they should target the same thing correct? Then the next > questions are, how would you like problems reported? If the process is > continuous, or if all jar files are 1.4.0 snapshot (i.e. version > slippage) how would somebody encountering a problem identify the > specific build in the report? > > I would also suggest a more prominent place for the "contributing" > link on the front page of http://clojure.org. Its way down there on > the bottom of the right hand column. That page (http://clojure.org/ > contributing) might also benefit from a plea such as the one you just > gave, and more information about how to contribute in different ways. > For example, how to help with documentation/website, how to submit a > bug report/patches, etc... > > Thanks. > > On Oct 30, 10:52 am, Rich Hickey <richhic...@gmail.com> wrote: >> It was nice to get some feedback on the changes in 1.3. It was a bit >> frustrating though to get them after release, and especially to get them on >> code that has been available for over 16 months. This after regular Maven >> releases of alphas starting over a year ago and betas since June. It's a >> fair amount of effort to produce these - should we not bother? >> >> If you are going to use free software, please consider giving something back >> by dedicating some resources for evaluation of new versions prior to their >> release. This will help keep quality up, help ensure it meets your needs, >> and give you less to do when it comes time to migrate in production. >> >> Thanks, >> >> Rich > > -- > 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 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
