Re: qatrack: Beginning QATrack 2.0

Hi Per,

Bouncer links are created manually within the Bouncer
administration 
page. This is not automated. A file is added to Bouncer by
selecting a 
profile that is to be used to identify the build by it's
file name, 
path, version and the MD5SUM to allow a checksum test by
Bouncer. Then 
after Bouncer found a corresponding file on the mirror
network the 
Bouncer URL works for resolving this file. As distribution
of a file and 
testing the Bouncer link before it's linked from a download
page is 
something that happens in parallel the entry for
"distributed" or 
"published" status in QA-Track should be set
afterwards.

> 
> About the bouncer links, I don't quite understand
completely how the
> works. If you'd like to start a "qatrack: Bouncer
links" and make a
> technical suggestion, it would make it a lot easier for
myself.
> 

Kind regards, Joost

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribeqa.openoffice.org
For additional commands, e-mail: dev-helpqa.openoffice.org

Hi Joost,

What would be good if it existed inside QAT? Is it an
additioanl address
field or a certain behaviour?

Per


Joost Andrae skrev:
> Bouncer links are created manually within the Bouncer
administration
> page. This is not automated. A file is added to Bouncer
by selecting a
> profile that is to be used to identify the build by
it's file name,
> path, version and the MD5SUM to allow a checksum test
by Bouncer. Then
> after Bouncer found a corresponding file on the mirror
network the
> Bouncer URL works for resolving this file. As
distribution of a file and
> testing the Bouncer link before it's linked from a
download page is
> something that happens in parallel the entry for
"distributed" or
> "published" status in QA-Track should be set
afterwards.
> 
>>
>> About the bouncer links, I don't quite understand
completely how the
>> works. If you'd like to start a "qatrack:
Bouncer links" and make a
>> technical suggestion, it would make it a lot easier
for myself.
>>
> 
> Kind regards, Joost

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribeqa.openoffice.org
For additional commands, e-mail: dev-helpqa.openoffice.org

On 10/8/07, Per Eriksson <pererikssonopenoffice.org> wrote:
> Hi Joost,
>
> What would be good if it existed inside QAT? Is it an
additioanl address
> field or a certain behaviour?
>
> Joost Andrae skrev:
> > Bouncer links are created manually within the
Bouncer administration
> > page. This is not automated. A file is added to
Bouncer by selecting a
> > profile that is to be used to identify the build
by it's file name,
> > path, version and the MD5SUM to allow a checksum
test by Bouncer. Then
> > after Bouncer found a corresponding file on the
mirror network the
> > Bouncer URL works for resolving this file. As
distribution of a file and
> > testing the Bouncer link before it's linked from a
download page is
> > something that happens in parallel the entry for
"distributed" or
> > "published" status in QA-Track should be
set afterwards.

The Bouncer links could be added to the QATrack page, so the
QA
managers would use QATrack instead of the Joost's comment on
the Issue
Tracker to keep track of the Bouncer links.

Maybe it could use the same parser it uses to identify
version,
language, etc. from the file name to generate the Bouncer
links, since
the Bouncer uses a regular URL structure, based on the file
name.

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribeqa.openoffice.org
For additional commands, e-mail: dev-helpqa.openoffice.org

Hi,

As I am not confortable with the Bouncer system, it's hard
for me to
discuss how it should be implemented.

It sounds like its a more complex behaviour in QATrack that
is requested.

I suggest that we bring it up again soon.

Per

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribeqa.openoffice.org
For additional commands, e-mail: dev-helpqa.openoffice.org