Hi all,

QA was not intent to bring a surprise of Xwalk bug migration from Github to 
JIRA, instead we discuss the JIRA purpose and bug migration work in weekly 
meeting during past weeks. 

Apologize that we didn't send out a notification to the public before starting 
the bug migration task. We started yesterday afternoon, and 43 open bugs (with 
Bug Label in Github) have been migrated to JIRA already, with clear component, 
priority, severity, version info attached. Besides we also observed that 2 
Xwalk features have been uploaded to JIRA as well.

BTW, QA is also preparing a public wiki for Xwalk Testing Home which includes 
QA dashboard, Bug reporting tool, and Bug scrub meeting, etc.

Thanks,
Tina


-----Original Message-----
From: [email protected] 
[mailto:[email protected]] On Behalf Of 
Balestrieri, Francesco
Sent: Tuesday, October 22, 2013 7:35 PM
To: Menard, Alexis; Tiago Vignatti
Cc: <[email protected]>
Subject: Re: [Crosswalk-dev] Migration to JIRA?

Hi,

I believe QA was waiting to complete the migration before announcing the move. 
The 502 error is because of a crash in the server that is being investigated, 
and is obviously an impediment to starting to use Jira.

> - Should we stop using github?

QA will report bugs in Jira, and we will be asking community members and 
anybody else who has a bug for Crosswalk to do the same. Obviously it's easier 
to use a single tracker tool, but if anybody finds Github useful for e.g. task 
tracking, there is nothing preventing that. 

> - Will the website be updated so that we redirect correctly to the 
> right bug report tool

Yes, that's the intention.

Regards,

Francesco

> -----Original Message-----
> From: [email protected] 
> [mailto:crosswalk- [email protected]] On Behalf 
> Of Menard, Alexis
> Sent: Tuesday, October 22, 2013 1:36 PM
> To: Tiago Vignatti
> Cc: <[email protected]>
> Subject: Re: [Crosswalk-dev] Migration to JIRA?
> 
> Hi,
> 
> - Should I archive the github issues?
> - I also have 502 errors?
> - Should we stop using github?
> - Will the website be updated so that we redirect correctly to the 
> right bug report tool?
> 
> Thanks.
> 
> Software Engineer @
> Intel Open Source Technology Center
> 
> On Oct 22, 2013, at 7:22 AM, Tiago Vignatti 
> <[email protected]>
> wrote:
> 
> > On 10/22/2013 01:03 PM, Raphael Kubo da Costa wrote:
> >> I'm seeing a ton of comments to GitHub issues indicating they have 
> >> been moved to JIRA, but I don't see any emails here announcing the 
> >> migration or giving any more details about the plans other than 
> >> Francesco's message that JIRA would start being used "soon".
> >>
> >> Since this is an open project with potentially non-Intel 
> >> contributors at least watching the mailing list, it would be good 
> >> if the people involved could give more details on the whys, whens 
> >> and whats of this
> migration.
> >
> > +1
> >
> > and I'm only getting "502 Bad Gateway" for every jira entry.
> >
> > Tiago
> >
> > _______________________________________________
> > Crosswalk-dev mailing list
> > [email protected]
> > https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
> 
> _______________________________________________
> Crosswalk-dev mailing list
> [email protected]
> https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
---------------------------------------------------------------------
Intel Finland Oy
Registered Address: PL 281, 00181 Helsinki Business Identity Code: 0357606 - 4 
Domiciled in Helsinki 

This e-mail and any attachments may contain confidential material for the sole 
use of the intended recipient(s). Any review or distribution by others is 
strictly prohibited. If you are not the intended recipient, please contact the 
sender and delete all copies.

_______________________________________________
Crosswalk-dev mailing list
[email protected]
https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
_______________________________________________
Crosswalk-dev mailing list
[email protected]
https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev

Reply via email to