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

[Michał B. <ba...@tl...>]

in a true continous integration evironment the nightly build does mean 
something different, but a true nightly build has no reason being 
publicly distributed in this case I think. the problem is the wait 
before a bugfix being commited, and a minor release with the fix being 
available. if you intend to release all the bug fix commits as they are 
made, there's no need for anything more I think. but in the case of 
delays like the one happening right now with 1.4.2 being quite buggy I 
could be serving players the fixes sooner.

On 11-09-22 18:45, Stefan Frey wrote:
> In my understanding the inclusion of new stuff is the defining difference
> between nightly builds and bug-fix releases to the latest stable release, but
> opinions might differ here.
>
> And I would try for a bug fix release only to apply those changes to the
> latest stable release which are clear fixes and not new features etc.
>
> This is something that the change to git makes much easier to accomplish.
>
> Stefan
>
> On Thursday, September 22, 2011 06:36:32 pm Michał Bażyński wrote:
>> 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