| Re: [AD] Tests to verify if a RC is fine? |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: alleg-developers@xxxxxxxxxx
- Subject: Re: [AD] Tests to verify if a RC is fine?
- From: Thomas Fjellstrom <tfjellstrom@xxxxxxxxxx>
- Date: Fri, 2 Sep 2005 15:39:13 -0600
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:from:to:subject:date:user-agent:references:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; b=JZqDVvsjsc5Ck77F2O6I6K4NXmu89nrke6bp5PyA7K8Xrr4kJrH+9GjXemZVAtJ9IxJd6ca+shmxcVl6icoZ3hnLNacrrpPPseTmPZkC0DFz5+b6Jr+JSj9cnbl6ZBb3B5B4esj7UWa6t8TPnc+4RbMiAqYx48Bfu8TpeCbG7xc=
On September 2, 2005 03:34 pm, Evert Glebbeek wrote:
> > > I'm wondering if apart from installing 4.2.0, maybe we should
> > > "require" at least 20 popular games which worked with 4.0.x to
> > > compile and work with 4.2.0 out of the box? Just to make sure it's
> > > really source compatible?
>
> Yes, this sounds like a reasonable idea. It will also help to highlight
> bugs that do not show up in a limited test-case environment.
>
> > At the very minimum I think all of the pre zipup steps should have been
> > run, I
> > have a person in #allegro who couldn't build any of the 4.2 releases
> > because
> > the asm def files and the allegro.def files didnt exist...
> >
> > Maybe make a nice little script on the server that does all of the
> > needed
> > steps to make a release mostly automatically?
>
> It is mostly automatic already. The def files should be generated
> automatically by the zipup.sh script (and fixdll.sh, for allegro.def - but
> you don't want to rerun that for the stable branch because doing so breaks
> ABI compatibility, reportedly).
> Is this the RC2 release? Or an earlier one?
I'm not 100% sure the errors were with RC2 or some earlier version, but The
person had problems with all of the ones he tried, rc2 included.
> Evert
--
Thomas Fjellstrom