<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 16/04/15 17:12, shirish wrote:<br>
</div>
<blockquote cite="mid:552FDF6A.5040409@hamaralinux.org" type="cite">
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
<font face="Century Schoolbook L">at bottom :-</font><br>
<br>
<div class="moz-cite-prefix">On 04/16/2015 09:27 PM, aparna wrote:<br>
</div>
<blockquote cite="mid:552FDBEF.809@hamaralinux.org" type="cite"> <br>
On 04/10/2015 03:39 PM, Vikas Tara wrote: <br>
<blockquote type="cite">On 10/04/15 10:35, aparna wrote: <br>
<blockquote type="cite"> <br>
<br>
<blockquote type="cite"> <br>
On 04/08/2015 07:00 PM, Vikas Tara wrote: <br>
<blockquote type="cite">Please respond here, if you can
help test. </blockquote>
I will pick up the testing for new iso and will update
accordingly. <br>
<br>
</blockquote>
I have tested the recent iso, bug no 101,bug no 105,bug no
51 seems to be resolved however bug no 115 is not resolved .
As I can still see the firefox version 36.0.1 although it
has got hamara branding. <br>
Please check the attachment. <br>
</blockquote>
No probs, firefox 37 has not been pushed to the main repo yet
- so that bug is still open. <br>
<br>
I have ran the firefox live build jobs - but there seems to be
a problem will the repo pull script. <br>
<br>
Can anyone take a look at that? <br>
</blockquote>
I have downloaded the iso from jenkins and tested it against <br>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://bugs.hamaralinux.org/buglist.cgi?f1=version&list_id=699&o1=equals&product=Hamara%20Linux&query_format=advanced&resolution=---&v1=1.0.1">http://bugs.hamaralinux.org/buglist.cgi?f1=version&list_id=699&o1=equals&product=Hamara%20Linux&query_format=advanced&resolution=---&v1=1.0.1</a>
and everything is working fine now. <br>
</blockquote>
<br>
@Aparna, are you saying all the 5 bugs have been looked at and all
of them are fixed or what ? Please clarify. Also if they have
been fixed, they should be marked fixed in the bug list as well. <br>
<br>
A good way/practise when you are marking a bug as resolved is to
share the test you did which told you that the bug is resolved so
others can also confirm it if need be. <br>
<br>
Looking forward to hear from you.<br>
</blockquote>
<br>
I am planning to merge these changes and tag/release tonigh.<br>
<br>
Aparna tested the same issues on the dev release last week - so I am
going to assume we are clear to launch.<br>
<br>
Shout if anyone disagrees and I'll hold the release.<br>
<br>
<br>
</body>
</html>