Win32 packages released on sourceforge
jakov at vmlinux.org
Mon Mar 22 10:20:03 CST 2004
Dimitrie O. Paun wrote:
>Now, when do we build? I don't think we should trigger the build based
>upon CVS commits, we need it a bit more controlled for a variety of
>reasons. Here is what I propose:
> -- decide on a time at night when the tree is very unlikely to change
> (say 4am).
> -- every day, at 4:10am we do:
> cvs up -D YYYYMMDD0400
> (this way we know _precicely_ what we built, and we can reporduce it)
> -- do the build (fix WINE_BUILD), check if the winetest.exe really changed.
> -- if it changed, edit WINE_BUILD and set it to YYYYMMDD0400.
> -- publish the result as winetest-YYYYMMDD0400.zip via the CGI script
Excellent! Nitpicking, but could we publish winetest-YYYYMMDD0400.exe,
As small as zip and no unpacking needed.
>But the main point here is that we can't build based on CVS committs, we
>need a well known, controlled point where we build so that developers
>can reproduce the build and investigate problems.
Agreed. Good you spent some thought on this.
More information about the wine-devel