Hi John,
LeMoyne Castle wrote (15-06-11 13:01)
On Wed, Jun 15, 2011 at 1:02 AM, Cor Nouws oo...@nouenoff.nl
mailto:oo...@nouenoff.nl wrote:
...
What I am more looking for, is sometimes the hints related to (some
of) the vast amount of code clean-ups/improvements, that possibly
have
Hi *,
Cor Nouws wrote (19-06-11 11:51)
And thanks to you and others for pointing to the current summaries as a
good starting point for that, anyway as far as I am concerned. I
understand the limitations now too.
Since there is much on the route in our QA-process/work, we can see if
there shows
On Sun, Jun 19, 2011 at 3:45 PM, Cor Nouws oo...@nouenoff.nl wrote:
Hi *,
Is there a script available, or a combination of git-commands, or ... that
is used to extract certain information for the summaries?
If so, I could use/adapt that to get information on certain weeks,
branches, ...
Hi John,
John LeMoyne Castle wrote (12-06-11 00:29)
I think the Weekly Development Summary might do what u want.
Not exactly, but maybe it is closest to.
It tends to slide by unnoticed because no one replies to it
( Well there are exceptions ;-) )
as they are all plowing straight
Hi Yifan,
Yifan Jiang wrote (13-06-11 12:47)
Great thanks for the message! Sorry I overlooked your mail at first glance,
No need to apologise. As you can see, I'm not always fast too ;-)
our regression testing is organized here:
https://tcm.documentfoundation.org/
Here is the instruction
Cor Nouws píše v St 15. 06. 2011 v 09:08 +0200:
Petr Mladek wrote (13-06-11 11:47)
:-(
You might find some ideas at http://wiki.documentfoundation.org/QA
I know that, thanks. In my experience (many years OOo) working with the
product random, is a very valuable good way of testing too.
On Wed, Jun 15, 2011 at 1:02 AM, Cor Nouws oo...@nouenoff.nl wrote:
Hi John,
...
...
What I am more looking for, is sometimes the hints related to (some of) the
vast amount of code clean-ups/improvements, that possibly have influence on
area A or B. (In the commit-logs for master)
Maybe
Hi Cor,
Cor Nouws píše v So 11. 06. 2011 v 02:58 +0200:
Hi all,
Quite regular I have the feeling that at least me would be helped a bit
by doing QA if there is some hint-list..
It sounds great! We are still looking for more QA people.
You might find some ideas at
On Mon, Jun 13, 2011 at 11:47:18AM +0200, Petr Mladek wrote:
Also Sophie and Yi Fan are trying to organize testing of beta and rc
builds. There is used Litmus server to coordinate the work between the
various testers. I am sure that they are looking for more testers and
test case writers.
Hi
Le 13/06/2011 12:47, Yifan Jiang a écrit :
On Mon, Jun 13, 2011 at 11:47:18AM +0200, Petr Mladek wrote:
Also Sophie and Yi Fan are trying to organize testing of beta and rc
builds. There is used Litmus server to coordinate the work between the
various testers. I am sure that they are looking
Hi Cor,
I think the Weekly Development Summary might do what u want. It tends to
slide by unnoticed because no one replies to it as they are all plowing
straight ahead. Here is an easy way to find it...
Go to top/thread view of dev list in Nabble --
Hi all,
Quite regular I have the feeling that at least me would be helped a bit
by doing QA if there is some hint-list..
I mean, it is not often that I make time to install a nightly build and
really start using it.
And then it feels a bit pointless just to do some often easy work -
after
12 matches
Mail list logo
