From: brett l. <bre...@gm...> - 2011-09-22 18:40:47
|
I understand, and apologize for the frustration our release delays have caused. This time around, the situation was somewhat unique. I don't plan on moving cross-country again. (at least, not for quite a while) ;-) I've also taken steps to ensure that at least two people have access to all parts of the project. The project has grown to the point where it truly is a community effort. So, I am now no longer the sole keeper of any part of the project. This should help avoid any single person's absence from the project preventing the project from moving forward, including my own. With that said, I've been involved to varying degrees in open source projects for the last 12-13 years or so. One of the worst things that far too many projects do, is fragmenting themselves across multiple web and service providers. This provides an inconsistent and often sub-par experience to users of the project. We're a small enough project as-is. I want to make sure that downloading our code and our packaged app is as easy as possible, especially for our less technically savvy users. I'm totally on board with providing automated nightly builds. I think it's a great idea, and one I've had myself. However, I want to put those builds in a place users already know about. This assures that they'll be easy to find and easy to obtain for anyone. ---Brett. On Thu, Sep 22, 2011 at 2:24 PM, Chris Shaffer <chr...@gm...> wrote: > I don't really care where it happens, I just would like to see > something that allows non-technical players to get a copy of the bug > fixes so their games aren't on hold for weeks at a time waiting for a > new release. > > -- > Chris > > Please consider the environment before printing this e-mail. > > > > On Thu, Sep 22, 2011 at 10:35 AM, brett lentz <bre...@gm...> wrote: >> Mike - >> >> I appreciate the suggestion, but a Dropbox folder is not an >> appropriate location for nightly builds. I don't want to confuse >> people by requiring them to got to different locations to find >> different copies of our work. >> >> Sourceforge gives us some shell space that might be able to host a >> script to generate nightly builds that are then posted to >> http://rails.sf.net and hosted by Sourceforge. Though, honestly with >> the low level of activity, we could probably be fine with weekly >> builds. >> >> You've been a semi-regular contributor for a while now, I'd be open to >> providing you with sufficient access to the sourceforge resources to >> allow you to set this up. >> >> ---Brett. >> >> >> >> 2011/9/22 Michał Bażyński <ba...@tl...>: >>> >>> I could take on the task of providing nightly builds in between releases >>> in a public dropbox folder. >>> I thought a sourceforge site was a better place for it so didn't >>> volunteer, but if this being served on dropbox and not sourceforge I can >>> do it. (I am assuming only patches that have bug fixes would be served >>> publicly, not newly developed stuff). >>> >>> as to your change log for the next release why not mention 1830 wabash >>> is now working? if someone tried playing that and gave up he might be >>> interested it is now working... >>> >>> mike >>> >>> On 11-09-22 18:32, Stefan Frey wrote: >>>> Chris: >>>> as already stated I like the idea of more frequent builds. However for nightly >>>> builds I would prefer an automated setup: To my knowledge there is no public >>>> build server for java projects (e.g. using Hudson/Jenkins) yet, but I have >>>> never looked actively for something like that. >>>> >>>> Publishing a build via Dropbox sounds somehow strange, but maybe the right >>>> solution for those playing Rails via Dropbox anyway. However I do not >>>> volunteer to providing such a solution. >>>> But maybe a more frequent publication of bug-fix releases will be a solution, >>>> but possibly I should not to give too much promises before I really know how >>>> difficult it will be to get the built up to Sourceforge. >>>> >>>> Stefan >>> >>> >> >> ------------------------------------------------------------------------------ >> All the data continuously generated in your IT infrastructure contains a >> definitive record of customers, application performance, security >> threats, fraudulent activity and more. Splunk takes this data and makes >> sense of it. Business sense. IT sense. Common sense. >> http://p.sf.net/sfu/splunk-d2dcopy1 >> _______________________________________________ >> Rails-devel mailing list >> Rai...@li... >> https://lists.sourceforge.net/lists/listinfo/rails-devel >> > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2dcopy1 > _______________________________________________ > Rails-devel mailing list > Rai...@li... > https://lists.sourceforge.net/lists/listinfo/rails-devel > |