2013-01-29 - Re: [GRASE-Hotspot] 3.7.7.6 To be released shortly

Header Data

From: Zubair Riaz Amazai <sa***r@gmail.com>
Message Hash: 382fffb737673c8319fdf61335c1a04564e1fa10b72ee4322698012ee596dec2
Message ID: <51078281.5020608@gmail.com>
Reply To: <51077886.1050505@gmail.com>
UTC Datetime: 2013-01-29 01:04:17 UTC
Raw Date: Tue, 29 Jan 2013 11:04:17 +0300

Raw message 

HI.

I never found the squid running.
any one sees something with
tail -f /var/log/squid3/access.log
?
Thanks

**********************************************
*					     *
*		Best Regards		     *
*					     *
*	    Muhammad Zubair Riaz	     *
*	Computer  network Consultant	     *
* 	      Linux + Windows		     *
*	     http://amazai.net		     *
*	     sa***r@gmail.com		     *
*	      966 544 43 0701		     *
*	    Saudi Arabia Jeddah		     *
*					     *
*					     *
**********************************************

On 01/29/2013 10:21 AM, Tim White wrote:
> On 29/01/13 17:06, Tim White wrote:
>> To everyone who hasn't been testing the dev versions, 3.7.7.6 will be
>> pushed to stable shortly.
>>
>> If you don't want it to automatically update, see
>> http://trac.grasehotspot.org/wiki/FAQ_T1_F3 for how to disable.
>>
>> HOWEVER, I strongly advise you update as there is a security fix in
>> 3.7.7.6
>>
>> Tim
> I should also note, that after this release I'm planning for more
> frequent but smaller releases. This release has been way too long in the
> coming, with some big fixes that haven't been released for 6 months.
> What this will probably mean is that I'll do a few minor point releases
> (3.7.7.x) to the dev repo, and then a point release (3.7.x) to the
> stable repo. "Major" release won't really happen, although if something
> major changes, then I might make it a major release. Alternatively, when
> all the features I feel like putting in the major release are done, I'll
> release the 3.x release, however it won't have many changes from it's
> point release, just the the version number has gone major.
>
> I do know that the risk is for many people that they have Grase in
> production and a minor release will break something, however it's
> probably better for lots of minor release and small breakage, than every
> 6 months a major release that potentially breaks a few things because we
> haven't had the minor things tested by enough people.
>
> At the end of the day, I need the community to be testing minor
> releases, as the places I'm running Grase are not a good sample of all
> the places the community are running it. For example, I only do time
> tracking at one location, not data, so some of the data tracking
> features get less testing than the time tracking (and visa versa)
>
> Tim
>
> ------------------------------------------------------------------------------
> Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
> MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
> with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
> MVPs and experts. ON SALE this month only -- learn more at:
> http://p.sf.net/sfu/learnnow-d2d
> _______________________________________________
> Grase-hotspot mailing list
> Gr***t@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/grase-hotspot

Thread