| Peter has already chimed in about and provided the link to the bug guidelines (thanks Peter!).
I have also added a short blurb to the status page’s overview to explain the goal and hopes for this information.
Sincerely,
Charles Rivet
Senior Product Manager, Papyrus-RT product lead
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?
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 _______________________________________________ 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 listpapyrus-rt-dev@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visithttps://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev
|
