Re: Please try the alphas and betas!
On Wed, Nov 2, 2011 at 10:00 AM, Chas Emerick wrote: [snip] > Yes; this is called "locking" snapshots in the Maven world, and there are > commands there that can lock any snapshot dependencies to the current > snapshot. > > If you are using Leiningen, there are no corollary commands, but you can use > the same concrete snapshot version numbers. e.g. looking at Clojure 1.4.0 > snapshots here: > > https://oss.sonatype.org/content/repositories/snapshots/org/clojure/clojure/1.4.0-master-SNAPSHOT/ > > You can use a version number like "1.4.0-master-20111025.230825-6" to fix > against that particular snapshot instead of continually updating to HEAD. > > That said, if alphas are going to be emitted at a steady pace, then updating > to them as desired may suit your use case better (i.e. it's easier to know to > revert to -alpha8 [or whatever] than it is to revert to > 1.4.0-master-20111025.230825-6). > > The maven snapshot metadata is only maintained for the latest snapshot so > version numbers that include SNAPSHOT can resolve to a particular concrete > artifact. Explicitly using a concrete snapshot version (like > "1.4.0-master-20111025.230825-6") resolves directly to the artifact in > question, so the metadata isn't relevant. Thanks to all who responded! This is really good to know. -John -- 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
Re: Please try the alphas and betas!
> Is there a way to peg a particular snapshot? If we find that > something breaks, we'd want to roll back to a previous version until > the problem is fixed. It looks like the maven metadata only has the > latest snapshot recorded (I may be wrong... I'm certainly not a Maven > guru). > > -John Yes; this is called "locking" snapshots in the Maven world, and there are commands there that can lock any snapshot dependencies to the current snapshot. If you are using Leiningen, there are no corollary commands, but you can use the same concrete snapshot version numbers. e.g. looking at Clojure 1.4.0 snapshots here: https://oss.sonatype.org/content/repositories/snapshots/org/clojure/clojure/1.4.0-master-SNAPSHOT/ You can use a version number like "1.4.0-master-20111025.230825-6" to fix against that particular snapshot instead of continually updating to HEAD. That said, if alphas are going to be emitted at a steady pace, then updating to them as desired may suit your use case better (i.e. it's easier to know to revert to -alpha8 [or whatever] than it is to revert to 1.4.0-master-20111025.230825-6). The maven snapshot metadata is only maintained for the latest snapshot so version numbers that include SNAPSHOT can resolve to a particular concrete artifact. Explicitly using a concrete snapshot version (like "1.4.0-master-20111025.230825-6") resolves directly to the artifact in question, so the metadata isn't relevant. - Chas -- 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
Re: Please try the alphas and betas!
http://bit.ly/clojure-releases Stuart Halloway wrote: I'd like to second what Bill said...I don't really have the time to setup a clojure build process to test out the 1.4 Alphas/Betas, but if there was a way for me to get to it via lein...I would just target 1.4 for all my day-to-day development. This should work: :repositories [["sonatype-snapshots" "https://oss.sonatype.org/content/repositories/snapshots/";]] :dependencies [[org.clojure/clojure "1.4.0-master-SNAPSHOT"] ...] Is there a way to peg a particular snapshot? If we find that something breaks, we'd want to roll back to a previous version until the problem is fixed. It looks like the maven metadata only has the latest snapshot recorded (I may be wrong... I'm certainly not a Maven guru). -John This is the reason the we release such a large number of alphas and betas, so we have something more reliable than snapshots to peg to. The following search on maven central will show you all the Clojure releases: http://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22org.clojure%22%20AND%20a%3A%22clojure%22 Does anybody know a better link that automatically shows this same info? If not, I will add this link in the wiki. Stu -- 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
Re: Please try the alphas and betas!
>>> I'd like to second what Bill said...I don't really have the time to >>> setup a clojure build process to test out the 1.4 Alphas/Betas, but if >>> there was a way for me to get to it via lein...I would just target 1.4 >>> for all my day-to-day development. >> >> This should work: >> >> :repositories [["sonatype-snapshots" >> "https://oss.sonatype.org/content/repositories/snapshots/";]] >> :dependencies [[org.clojure/clojure "1.4.0-master-SNAPSHOT"] ...] > > Is there a way to peg a particular snapshot? If we find that > something breaks, we'd want to roll back to a previous version until > the problem is fixed. It looks like the maven metadata only has the > latest snapshot recorded (I may be wrong... I'm certainly not a Maven > guru). > > -John This is the reason the we release such a large number of alphas and betas, so we have something more reliable than snapshots to peg to. The following search on maven central will show you all the Clojure releases: http://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22org.clojure%22%20AND%20a%3A%22clojure%22 Does anybody know a better link that automatically shows this same info? If not, I will add this link in the wiki. Stu -- 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
Re: Please try the alphas and betas!
On Mon, Oct 31, 2011 at 4:25 PM, Sean Corfield wrote: > On Mon, Oct 31, 2011 at 8:06 AM, Timothy Baldridge > wrote: >> I'd like to second what Bill said...I don't really have the time to >> setup a clojure build process to test out the 1.4 Alphas/Betas, but if >> there was a way for me to get to it via lein...I would just target 1.4 >> for all my day-to-day development. > > This should work: > > :repositories [["sonatype-snapshots" > "https://oss.sonatype.org/content/repositories/snapshots/";]] > :dependencies [[org.clojure/clojure "1.4.0-master-SNAPSHOT"] ...] Is there a way to peg a particular snapshot? If we find that something breaks, we'd want to roll back to a previous version until the problem is fixed. It looks like the maven metadata only has the latest snapshot recorded (I may be wrong... I'm certainly not a Maven guru). -John -- 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
Re: Please try the alphas and betas!
I'm with Phil on this one. The alphas and betas are synced to maven central. You don't need any additional repositories in your project file. They are announced on the list when they are cut and always have a brief list of changes since the last release. They are easy to find if you follow this list. You can also just look in maven central to find the latest. Cheers, Aaron Bedra -- Clojure/core http://clojure.com On Mon, Oct 31, 2011 at 8:11 PM, Phil Hagelberg wrote: > On Mon, Oct 31, 2011 at 4:57 PM, JMatt wrote: > > Everyone that I know who writes clojure professionally or on a daily > basis > > uses lein to start. The simplest way to expose far more people to alphas > and > > betas is to add the sonatype repo to the default-repos function in lein: > > > https://github.com/technomancy/leiningen/blob/1.x/src/leiningen/core.clj#L128 > > Is there a reason that lein shouldn't / doesn't support the new repos? > > Adding snapshot repositories to the default repo list incurs an > additional cost for checking every single snapshot dependency you add. > I would rather have folks call out explicit usage of snapshots. > Leiningen 2.0 will probably even remove Clojars snapshots by default. > > -Phil > > -- > 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
Re: Please try the alphas and betas!
On Mon, Oct 31, 2011 at 4:57 PM, JMatt wrote: > Everyone that I know who writes clojure professionally or on a daily basis > uses lein to start. The simplest way to expose far more people to alphas and > betas is to add the sonatype repo to the default-repos function in lein: > https://github.com/technomancy/leiningen/blob/1.x/src/leiningen/core.clj#L128 > Is there a reason that lein shouldn't / doesn't support the new repos? Adding snapshot repositories to the default repo list incurs an additional cost for checking every single snapshot dependency you add. I would rather have folks call out explicit usage of snapshots. Leiningen 2.0 will probably even remove Clojars snapshots by default. -Phil -- 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
Re: Please try the alphas and betas!
I expect this discussion isn't what Rich had in mind so let's draw it to a close. If any one else thinks there is merit in a vehicle that provides the clojure team with access to many real life examples of how clojure is being used in the wild and equally providing those submitters with early feedback on any broken changes then drop me an email/start another thread. I assume Kevin, that you won't be hammering on my door to lead this idea? To be honest I won't be doing anything about it either, it was just an idea. Let's agree to disagree and allow this one to die gracefully :) Sent from my iPad (one of many Internet connected devices which allow me to be ridiculed :)) On 31 Oct 2011, at 23:45, Kevin Downey wrote: > On Mon, Oct 31, 2011 at 2:57 PM, Colin Yates wrote: >> Don't want to feed the trolls but can you justify "ridiculous"? >> Rather a strong term.or maybe your definition is "I don't >> understand the value". > > The value of having people piece together ad-hoc test suites vs. > adding tests to Clojure (and the Clojure build) is in some sense the > same. > > The tests will flush out undesired behavior regardless. > > In another sense the value of having your own test suite is higher > because you have it test what you care about and don't have to jump > through hoops to get it into Clojure's suite. > > In yet another sense the value of having tests in Clojure's test suite > is higher because some failures will be detected early (and fixing it > early is some how less expensive). > > The idea is not ridiculous. The circumstances that would drive to it's > implementation would be. > > It would make Clojure, to my knowledge, the only open source project > were contribution of test cases is so difficult the community more or > less forks the tests suite from the controlling body and runs it > themselves. > > Your email starts off "Whacky idea… ", so maybe I should have said > "which is whack." > > My guess is rich wrote this in response (at least in some part) to > nathan's recent thread about the change to box ints as Longs in > Clojure 1.3. > > This change would cause tests written to detect the boxed type of > numbers to fail, but so what? The change is deliberate and planned so > of course tests will fail, the tests just no longer reflect what you > want. > > My understanding is what rich wants is use cases to guide changes in > the semantics of the language. > > e.g. "I used to do X in clojure version N, but in the latest snapshot > with change C, X isn't as easy to do, is there some C' that would make > this better?" > > e.g. "I used to stick ints into collections and turn around and use > them for interop in clojure version 1.2, but in 1.3 with changes to > how clojure boxes numbers, interop isn't as easy to do, is there some > other change we could use to enforce clojure's semantics in > collections that would make this better?" > > >> Maybe you are right, maybe we should provide an easy way to submit >> test cases which are automatically run as part of a CI buildno >> wait, that was my ridiculous suggestion. >> >> Please ask yourself how your response added anything at all to this >> thread or community other than making it just a little harder for >> people to suggest things for fear of being ridiculed without any form >> of justification. A much better response would have been "I don't get >> it, please explain". Based on your ability to read Rich's thoughts >> maybe you have already had that conversation with me telepathically. >> Dunno. > > Keeping up with the state of play is hardly mind reading, and I don't > think it is too much to ask of people who want to participate in > discussions. > > I will not pretend to know rich's mind (I still don't understand why > Clojure can't take pull requests) but absent clarification by rich and > given the "whacky" idea of yours, the "use case" interpretation is the > only thing that makes sense. > >> >> My (I.e. this) response hasn't added anything except to flag up a very >> unhelpful and negative comment (and been just a little therapeutic) >> >> Sent from my iPad > > If you cannot deal with having an idea you profess to be "whacky" > called "ridiculous" by someone on the internet, you might need fewer > internet connected devices. > >> >> On 31 Oct 2011, at 21:42, Kevin Downey wrote: >> >>> the responses to rich here sort of read like "lets make an ad-hoc test >>> suite for clojure and everyone can run it" which is ridiculous. >>> >>> tests should be contributed back to clojure. >>> >>> if contributing tests is so difficult people instead create their own >>> test suites and report results then we need to stream line the >>> contribution process. >>> >>> I cannot imagine this the kind of response rich was looking for, maybe >>> he will clarify. >>> >>> On Mon, Oct 31, 2011 at 2:08 PM, Stuart Sierra >>> wrote: Yes, the Sonatype repositories have every Clojure development snapshot since 1.3. -Stuart Sie
Re: Please try the alphas and betas!
It can still be difficult to find the right repo and documentation for alpha and betas. Especially for the new contrib. It really doesn't have anything to do with the Core team or the actual documentation (when it's finally found). To me the problem is sifting through the countless highly ranked old and/or bad information. On Monday, October 31, 2011 1:25:30 PM UTC-7, Sean Corfield wrote: > > :repositories [["sonatype-snapshots" > "https://oss.sonatype.org/content/repositories/snapshots/";]] > :dependencies [[org.clojure/clojure "1.4.0-master-SNAPSHOT"] ...] > Everyone that I know who writes clojure professionally or on a daily basis uses lein to start. The simplest way to expose far more people to alphas and betas is to add the sonatype repo to the default-repos function in lein: https://github.com/technomancy/leiningen/blob/1.x/src/leiningen/core.clj#L128 Is there a reason that lein shouldn't / doesn't support the new repos? Rich and Core team, thanks for pointing out the importance of using alphas and betas. Sometimes it's not clear what we can do to help with the project. Posts like this that are actionable definitely provide guidance and transparency as to how all of us can give back. JMatt -- 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
Re: Please try the alphas and betas!
On Mon, Oct 31, 2011 at 2:57 PM, Colin Yates wrote: > Don't want to feed the trolls but can you justify "ridiculous"? > Rather a strong term.or maybe your definition is "I don't > understand the value". The value of having people piece together ad-hoc test suites vs. adding tests to Clojure (and the Clojure build) is in some sense the same. The tests will flush out undesired behavior regardless. In another sense the value of having your own test suite is higher because you have it test what you care about and don't have to jump through hoops to get it into Clojure's suite. In yet another sense the value of having tests in Clojure's test suite is higher because some failures will be detected early (and fixing it early is some how less expensive). The idea is not ridiculous. The circumstances that would drive to it's implementation would be. It would make Clojure, to my knowledge, the only open source project were contribution of test cases is so difficult the community more or less forks the tests suite from the controlling body and runs it themselves. Your email starts off "Whacky idea… ", so maybe I should have said "which is whack." My guess is rich wrote this in response (at least in some part) to nathan's recent thread about the change to box ints as Longs in Clojure 1.3. This change would cause tests written to detect the boxed type of numbers to fail, but so what? The change is deliberate and planned so of course tests will fail, the tests just no longer reflect what you want. My understanding is what rich wants is use cases to guide changes in the semantics of the language. e.g. "I used to do X in clojure version N, but in the latest snapshot with change C, X isn't as easy to do, is there some C' that would make this better?" e.g. "I used to stick ints into collections and turn around and use them for interop in clojure version 1.2, but in 1.3 with changes to how clojure boxes numbers, interop isn't as easy to do, is there some other change we could use to enforce clojure's semantics in collections that would make this better?" > Maybe you are right, maybe we should provide an easy way to submit > test cases which are automatically run as part of a CI buildno > wait, that was my ridiculous suggestion. > > Please ask yourself how your response added anything at all to this > thread or community other than making it just a little harder for > people to suggest things for fear of being ridiculed without any form > of justification. A much better response would have been "I don't get > it, please explain". Based on your ability to read Rich's thoughts > maybe you have already had that conversation with me telepathically. > Dunno. Keeping up with the state of play is hardly mind reading, and I don't think it is too much to ask of people who want to participate in discussions. I will not pretend to know rich's mind (I still don't understand why Clojure can't take pull requests) but absent clarification by rich and given the "whacky" idea of yours, the "use case" interpretation is the only thing that makes sense. > > My (I.e. this) response hasn't added anything except to flag up a very > unhelpful and negative comment (and been just a little therapeutic) > > Sent from my iPad If you cannot deal with having an idea you profess to be "whacky" called "ridiculous" by someone on the internet, you might need fewer internet connected devices. > > On 31 Oct 2011, at 21:42, Kevin Downey wrote: > >> the responses to rich here sort of read like "lets make an ad-hoc test >> suite for clojure and everyone can run it" which is ridiculous. >> >> tests should be contributed back to clojure. >> >> if contributing tests is so difficult people instead create their own >> test suites and report results then we need to stream line the >> contribution process. >> >> I cannot imagine this the kind of response rich was looking for, maybe >> he will clarify. >> >> On Mon, Oct 31, 2011 at 2:08 PM, Stuart Sierra >> wrote: >>> Yes, the Sonatype repositories have every Clojure development snapshot since >>> 1.3. >>> >>> -Stuart Sierra >>> clojure.com >>> >>> -- >>> 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 >> >> >> >> -- >> And what is good, Phaedrus, >> And what is not good— >> Need we ask anyone to tell us these things? >> >> -- >> 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
Re: Please try the alphas and betas!
Don't want to feed the trolls but can you justify "ridiculous"? Rather a strong term.or maybe your definition is "I don't understand the value". Maybe you are right, maybe we should provide an easy way to submit test cases which are automatically run as part of a CI buildno wait, that was my ridiculous suggestion. Please ask yourself how your response added anything at all to this thread or community other than making it just a little harder for people to suggest things for fear of being ridiculed without any form of justification. A much better response would have been "I don't get it, please explain". Based on your ability to read Rich's thoughts maybe you have already had that conversation with me telepathically. Dunno. My (I.e. this) response hasn't added anything except to flag up a very unhelpful and negative comment (and been just a little therapeutic) Sent from my iPad On 31 Oct 2011, at 21:42, Kevin Downey wrote: > the responses to rich here sort of read like "lets make an ad-hoc test > suite for clojure and everyone can run it" which is ridiculous. > > tests should be contributed back to clojure. > > if contributing tests is so difficult people instead create their own > test suites and report results then we need to stream line the > contribution process. > > I cannot imagine this the kind of response rich was looking for, maybe > he will clarify. > > On Mon, Oct 31, 2011 at 2:08 PM, Stuart Sierra > wrote: >> Yes, the Sonatype repositories have every Clojure development snapshot since >> 1.3. >> >> -Stuart Sierra >> clojure.com >> >> -- >> 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 > > > > -- > And what is good, Phaedrus, > And what is not good— > Need we ask anyone to tell us these things? > > -- > 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
Re: Please try the alphas and betas!
the responses to rich here sort of read like "lets make an ad-hoc test suite for clojure and everyone can run it" which is ridiculous. tests should be contributed back to clojure. if contributing tests is so difficult people instead create their own test suites and report results then we need to stream line the contribution process. I cannot imagine this the kind of response rich was looking for, maybe he will clarify. On Mon, Oct 31, 2011 at 2:08 PM, Stuart Sierra wrote: > Yes, the Sonatype repositories have every Clojure development snapshot since > 1.3. > > -Stuart Sierra > clojure.com > > -- > 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 -- And what is good, Phaedrus, And what is not good— Need we ask anyone to tell us these things? -- 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
Re: Please try the alphas and betas!
Yes, the Sonatype repositories have every Clojure development snapshot since 1.3. -Stuart Sierra clojure.com -- 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
Re: Please try the alphas and betas!
On Mon, Oct 31, 2011 at 8:06 AM, Timothy Baldridge wrote: > I'd like to second what Bill said...I don't really have the time to > setup a clojure build process to test out the 1.4 Alphas/Betas, but if > there was a way for me to get to it via lein...I would just target 1.4 > for all my day-to-day development. This should work: :repositories [["sonatype-snapshots" "https://oss.sonatype.org/content/repositories/snapshots/";]] :dependencies [[org.clojure/clojure "1.4.0-master-SNAPSHOT"] ...] -- Sean A Corfield -- (904) 302-SEAN An Architect's View -- http://corfield.org/ World Singles, LLC. -- http://worldsingles.com/ Railo Technologies, Inc. -- http://www.getrailo.com/ "Perfection is the enemy of the good." -- Gustave Flaubert, French realist novelist (1821-1880) -- 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
Re: Please try the alphas and betas!
I'd like to second what Bill said...I don't really have the time to setup a clojure build process to test out the 1.4 Alphas/Betas, but if there was a way for me to get to it via lein...I would just target 1.4 for all my day-to-day development. Timothy On Mon, Oct 31, 2011 at 10:00 AM, Joel Gluth wrote: > Worth pointing out that the Clojure team don't have to do this > necessarily - a motivated person could set up a CI server that > monitors pre-release SNAPSHOTS on one side, and takes code > snippets/lein projects/gists/test-is packages on the other? > > On Sun, Oct 30, 2011 at 4:04 PM, Colin Yates wrote: >> Whacky idea - is there a way for people to submit snippets which are >> run as part of the CI process? > -- > [what were the skies like when you were young?] > > -- > 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 -- “One of the main causes of the fall of the Roman Empire was that–lacking zero–they had no way to indicate successful termination of their C programs.” (Robert Firth) -- 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
Re: Please try the alphas and betas!
Worth pointing out that the Clojure team don't have to do this necessarily - a motivated person could set up a CI server that monitors pre-release SNAPSHOTS on one side, and takes code snippets/lein projects/gists/test-is packages on the other? On Sun, Oct 30, 2011 at 4:04 PM, Colin Yates wrote: > Whacky idea - is there a way for people to submit snippets which are > run as part of the CI process? -- [what were the skies like when you were young?] -- 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
Re: Please try the alphas and betas!
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 interestingindicating 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 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 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
Re: Please try the alphas and betas!
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 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
Please try the alphas and betas!
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
