[Feedhenry-raincatcher] Testing RainCatcher on upstream

[Jameel Briones]

+1 That sounds good to me. I think tickets should always be created though
in order to track the work done no matter the size of release.

JAMEEL BRIONES

ASSOCIATE SOFTWARE ENGINEER

Red Hat Mobile

<https://www.redhat.com/>

Communications House, Cork Road

Waterford City, Ireland X91NY33

jbriones at redhat.com
<https://red.ht/sig>
TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

On Wed, Oct 11, 2017 at 4:27 PM, Wojciech Trocki <wtrocki at redhat.com> wrote:

> Hi everyone
>
> I would like to imitate conversation about testing aproach for upstream
> releases.
> We inherited really good patterns from RedHat testing team.
> My proposition will be to use the same testing plan as before:
>
> https://trello.com/b/BlKPjRoB/test-plan-wfm-raincatcher
>
> This test plan is now open. We can move this to our documentation if
> needed.
>
> Proposed testing procedure:
>
> 1. Prerelease our 3 apps.
> 2. Testing is being carried by team (tickets can be created if needed,
> depending on the size of the release)
> 3. After testing is finished we can push proper tags and force push
> version to master.
>
> WDYT?
>
> Regards
> --
>
> WOJCIECH TROCKI
>
> Red Hat Mobile <https://www.redhat.com/>
>
> IM: wtrocki
> <https://red.ht/sig>
>
> _______________________________________________
> Feedhenry-raincatcher mailing list
> Feedhenry-raincatcher at redhat.com
> https://www.redhat.com/mailman/listinfo/feedhenry-raincatcher
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/feedhenry-raincatcher/attachments/20171011/e1053b09/attachment.htm>