<div dir="ltr"><br><div>Valid points, but I'd like to counter that it would be a very good idea to build the releases on the build bot and then let the developer re-upload it as a release. Thus both verifying that the build bot environment is kept from rotting and avoiding problems with a volatile development environment.</div>
<div><br></div><div>A reoccurring issue with hobby development on small platforms is that you might have to make experimental changes to gcc/binutils/libc/other to get a specific project working. If you don't keep impeccable notes and parallel compilation environments you end up not having access to the environment tested for project A (say ScummVM) after having worked on project B for a couple of months. Just pulling something from the bot and testing it would be nice.</div>
<div><br></div><div>NB: I'm not a ScummVM developer, just an occasional tester and contributor to the Dreamcast port.</div><div><br></div><div>-- </div><div>Peter Bortas</div><div><br></div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Sat, Jul 6, 2013 at 9:17 AM, Travis Howell <span dir="ltr"><<a href="mailto:kirben@optusnet.com.au" target="_blank">kirben@optusnet.com.au</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5">On 6/07/2013 2:58 PM, Eugene Sandulenko wrote:<br>
> A thing which was bothering me for a while. Would it be possible to use<br>
> our buildbot for building release packages?<br>
><br>
> We have a nice collection of platforms represented there, and some of<br>
> them have their maintainer inactive. Also this would let to release much<br>
> broader set of packages by time of the release.<br>
><br>
> So, are there any technical obstacles to this?<br>
<br>
</div></div>An extremely bad idea, since release builds are meant to be well tested<br>
for a wider range of users. For ports which aren't maintained, we don't<br>
know how functional those ports still are, even if they continue to<br>
compile and build. For ports which are maintained, there is still a<br>
lower risk of build environment differences compared to the maintainer,<br>
which could mean a difference in features offered, or cause additional<br>
bugs in the worst case.<br>
<br>
Users always have the choice to using a recent snapshot, but we<br>
shouldn't be offering these build if we can't be sure of their quality.<br>
<br>
If you really want to go this way, you might as well just drop releases,<br>
since we only offer minimum testing for releases now.<br>
<br>
------------------------------------------------------------------------------<br>
This SF.net email is sponsored by Windows:<br>
<br>
Build for Windows Store.<br>
<br>
<a href="http://p.sf.net/sfu/windows-dev2dev" target="_blank">http://p.sf.net/sfu/windows-dev2dev</a><br>
_______________________________________________<br>
Scummvm-devel mailing list<br>
<a href="mailto:Scummvm-devel@lists.sourceforge.net">Scummvm-devel@lists.sourceforge.net</a><br>
<a href="https://lists.sourceforge.net/lists/listinfo/scummvm-devel" target="_blank">https://lists.sourceforge.net/lists/listinfo/scummvm-devel</a><br>
</blockquote></div><br></div>