Re: [coLinux-devel] RE: autobuild can't communicate

[Henry N. <Henry.Ne@Arcor.de>]

Stable part should be stable, and any developer should check the binary 
before make it public.

If we find a error in devel branch, we can think to correct them also in 
stable branch. But not all futures are an error.

I think also, that branch "devel" is enouth for autobuild. It do only 
compile and put binaries with source for more testers. Not all testers 
can compile colinux, so autobuild help them to.

Autobuild do also test a minimal install of riquired tools. I check all 
times the "./configure", liddle bit of missing files and fatal errors on 
gcc make.

-- 
Henry Nestler


Sam Moffatt wrote:

> Its quite simple, if its stable, it should be easily publicly
> available, typically via sourceforge. anything built out of monotone
> can be missing something. A commit may be made on a file that is
> required for a commit created on another file. A problem could exist
> in this case with one file being updated and looking for another file,
> but missing the required update (as it wasn't there when monotone
> started).
> 
> The autobuild appears to be useful for creating binaries to save
> recompiling. Thats what I use it for, I'd much rather have someone
> else compile it and then go from there. I know its going to break, I'm
> a developer, I know some of my CVS commits have the text "This will
> probably break" in it from time to time.
> 
> So simply put, autobuild will produce binaries that have issues, it
> says that "These haven't been tested." If we can find a bug, then we
> can track it down and fix it. If I don't have to wait for my computer
> to recompile colinux until I find a bug, then I'm much more inclined
> to go bug hunting or new feature testing.
> 
> Thats my two cents anyway,
> 
> Sam
> 
> 
> On Sun, 13 Feb 2005 12:03:33 +0000, Nuno Lucas <li...@xp...> wrote:
> 
>>Ian Bonnycastle, dando pulos de alegria, escreveu :
>>
>>>This brings up the question.. is Henry's autobuild process going to
>>>create both stable and unstable autobuilds?
>>
>>It doesn't need to build "stable", because now stable is used only for
>>bug fixes, so a change there will be reflected in the release on site to
>>be updated (at least that's the idea, i think).
>>
>>What probably needs to be defined is what a bug fix is, as experimental
>>features like cofs may not be comtemplated.
>>
>>Regards,
>>~Nuno Lucas
>>
>>-------------------------------------------------------
>>SF email is sponsored by - The IT Product Guide
>>Read honest & candid reviews on hundreds of IT Products from real users.
>>Discover which products truly live up to the hype. Start reading now.
>>http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
>>_______________________________________________
>>coLinux-devel mailing list
>>coL...@li...
>>https://lists.sourceforge.net/lists/listinfo/colinux-devel
>>
> 
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> coLinux-devel mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-devel
>