trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: September 2012

Re: [trinity-devel] 3.5.13.1 finishing

From: Slávek Banko <slavek.banko@...>
Date: Sun, 23 Sep 2012 16:51:06 +0200
On Wednesday 19 of September 2012 07:02:42 Francois Andriot wrote:
> Le 18/09/2012 21:50, Slávek Banko a écrit :
> > François, David, all,
> >
> > After incorporation of patches to change the path to the 
documentation, the
> > current state of the GIT branches v3.5.13-sru seems to be ready to 
release
> > 3.5.13.1. Please, are there any other patches that should be included? 
Errors
> > that should be resolved? Anything else for what should be a release
> > postponed?
> Good news! On my side, I have no patch to include to 3.5.13.1 at the 
moment.
> 
> >
> > For example:
> >
> > Should I incorporate the latest patches from Darrell for KPDF?
> > + http://trinity-devel.pearsoncomputing.net/?0::10089
> > + http://trinity-devel.pearsoncomputing.net/?0::10090
> I think these patches are too young to be included in 3.5.13.1 .
> 
> > It should first resolve bugs reported by François? As:
> > + http://bugs.pearsoncomputing.net/show_bug.cgi?id=1151
> > + http://bugs.pearsoncomputing.net/show_bug.cgi?id=1159
> These ones are build issue, I can live without them, other people did 
> not even mention them.
> 
> >
> > Furthermore, I would like to ask: François, David, can you test build 
using
> > GIT branch v3.5.13-sru or you need first tarballs? Note: With updated 
scripts
> > and branch v3.5.13-sru on meta-project 'tde' is now easy switching GIT 
to
> > branch v3.5.13-sru.
> I'd prefer to have final tarballs to test in real conditions.
> 
> >
> > I look forward to hearing your opinions and comments.
> >
> > Slávek
> 
> Thanks
> Francois
> 

François, you can find tarballs on:
http://ppa.quickbuild.pearsoncomputing.net/trinity/releases/3.5.13.1/

Are named with "~rc1" to have the possibility to add some latest patches 
before the final release. Currently, one patch, which will be included 
surely => setting the version number. A further two new patches that I 
would like included. Please, can you also test this patches?

All of these patches are attached to the report:
http://bugs.pearsoncomputing.net/show_bug.cgi?id=1130

Thanks,
Slávek
--