Re: [Rails-devel] New release coming out tonight

[brett l. <bre...@gm...>]

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
>
>