Re: NetSurf 3.1 AmigaOS build

2014-04-30 Thread Chris Young
On Wed, 30 Apr 2014 21:55:28 +0100, Michael Drake wrote: > > I was under the impression that Jenkins was going to build this but as > > it didn't seem forthcoming I built it manually myself. > > Yep, sorry, it took us a while to get it sorted. The Jenkins build of > 3.1 should now be available

Re: NetSurf 3.1 AmigaOS build

2014-04-30 Thread Michael Drake
Hi Chris, On 28/04/14 18:05, Chris Young wrote: I was under the impression that Jenkins was going to build this but as it didn't seem forthcoming I built it manually myself. Yep, sorry, it took us a while to get it sorted. The Jenkins build of 3.1 should now be available from: http://www.

NetSurf 3.1 AmigaOS build

2014-04-28 Thread Chris Young
Is here: http://www.os4depot.net/share/network/browser/netsurf.lha I was under the impression that Jenkins was going to build this but as it didn't seem forthcoming I built it manually myself. I'll replace it with the Jenkins build if we get one later, otherwise the above archive can be taken for

Re: NetSurf 3.1 last call

2014-04-08 Thread Chris Young
On Sat, 5 Apr 2014 10:29:00 +0100, Vincent Sanders wrote: > Last call for the 3.1 release. If you have any fixes or updates that > ought to go in this release now is the time. I'm sure you've seen this, but just in case: https://www.openssl.org/news/secadv_20140407.txt It's probably a very good

NetSurf 3.1 last call

2014-04-05 Thread Vincent Sanders
Last call for the 3.1 release. If you have any fixes or updates that ought to go in this release now is the time. I will be tagging the release and start generating release tarballs for libraries and NetSurf during the weekend 12th and 13th April. The CI system will be used to build release binar

Re: NetSurf 3.1 Change Log

2014-04-02 Thread Chris Young
On Wed, 2 Apr 2014 09:00:12 +0300, Daniel Silverstone wrote: > > > http://www.netsurf-browser.org/temp/ChangeLog.txt > > > > > > Anyone see anything wrong/missing? > > > > No, not unless sombody wants to merge my branches before the 3.1 > > release. > > I think we want more time to review your

Re: NetSurf 3.1 Change Log

2014-04-01 Thread Daniel Silverstone
On Tue, Apr 01, 2014 at 18:09:37 +0100, Chris Young wrote: > On Tue, 01 Apr 2014 08:16:36 +0100, Michael Drake wrote: > > > http://www.netsurf-browser.org/temp/ChangeLog.txt > > > > Anyone see anything wrong/missing? > > No, not unless sombody wants to merge my branches before the 3.1 > release.

Re: NetSurf 3.1 Change Log

2014-04-01 Thread Chris Young
On Tue, 01 Apr 2014 08:16:36 +0100, Michael Drake wrote: > http://www.netsurf-browser.org/temp/ChangeLog.txt > > Anyone see anything wrong/missing? No, not unless sombody wants to merge my branches before the 3.1 release. Chris

Re: NetSurf 3.1 Change Log

2014-04-01 Thread François Revol
On 01/04/2014 09:16, Michael Drake wrote: > > http://www.netsurf-browser.org/temp/ChangeLog.txt > > Anyone see anything wrong/missing? Looks good for my part. I just checked that HEAD still builds on Haiku. François.

NetSurf 3.1 Change Log

2014-04-01 Thread Michael Drake
http://www.netsurf-browser.org/temp/ChangeLog.txt Anyone see anything wrong/missing? Cheers, Michael

NetSurf 3.1

2014-03-16 Thread Michael Drake
We're planning to create the NetSurf 3.1 release fairly soon. Could front end maintainers ensure things are ready for release? Particularly, could you make sure the Docs/BUILDING-* document for your platform is up-to-date and correct? Cheers, Michael

Re: NetSurf 3.1 alert

2013-12-03 Thread Chris Young
On Tue, 03 Dec 2013 12:27:09 + (GMT), Michael Drake wrote: > The core developers are gathering for a development weekend on 4/5th Jan. > We plan to get things sorted out so that a release of NetSurf 3.1 can be > made shortly after. > > So the message to front end maintaine

NetSurf 3.1 alert

2013-12-03 Thread Michael Drake
The core developers are gathering for a development weekend on 4/5th Jan. We plan to get things sorted out so that a release of NetSurf 3.1 can be made shortly after. So the message to front end maintainers is to try to get anything outstanding tidied up and ready for release by then. Cheers