Re: [papyrus-rt-dev] Papyrus-RT v0.8 Release Status

[Peter Cigéhn <peter.cigehn@xxxxxxxxx>]

Hi,

I can answer what I did, and that was to verify those Bugzillas that I was assigned as QA. I only put the Bugzilla into verified state, but did not take the the closed state, since I was not the reporter/originator of those Bugzillas, and I felt that it was better to let the reporter/originator to decide that it could be closed. This is how I have interpreted our Bug Guidelines.

/Peter Cigéhn

On 6 October 2016 at 15:47, Christian Damus <give.a.damus@xxxxxxxxx> wrote:

Hi, Charles,

The only bugs for which I am either reporter or QA contact are bugs that I was assigned to fix.  Do you want us to verify and close our own fixes?  Or to assign ourselves as QA contact to volunteer to verify other bugs?

Or else what exactly is being asked?

Thanks,

Christian

On 6 October, 2016 at 09:22:49, charles+zeligsoft.com (charles@xxxxxxxxxxxxx) wrote:

Hello everyone,

Images and PDFs are not always the best way to send status information and it’s too much work to convert to plain text in a legible format…So I moved it to the wiki!

You can find this morning’s release status here.

Sincerely,

Charles Rivet
Senior Product Manager, Papyrus-RT product lead

charles@xxxxxxxxxxxxx

_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev

_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev