-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
As a staff member, I want to be sure that the email is ready, so I know we can send the final version #61
Comments
@bruquevedo please ask the team to put the feedback here, so everyone can discuss it. |
hey @vjpixel @JoshuSantos and @tiagobugarin I just sent the e-mail test. As soon as possible please give your feedback here. Tks :) |
I received the e-mail in the inbox. Link is working and everthing is ok to me |
The email reached the inbox and the link worked. |
There are two things I noticed, both in this paragraph.
|
I reopened issue #57 and commented there my new suggestion to your observation |
the problem here is that it was not made in to a link from within the MailChimp system, then it goes out as a normal text and then the mail client interprets it as a link. always remember that |
PROs:
CONs:
|
Since we're testing the final email, there's no way to point it to the alpha version. Pretend the link you're receiving is |
I received feedback from everybody and already changed what you suggested. So we can consider that the email is ready to be sent to testers on monday 8am |
@vjpixel could you please review this issue? |
Can you please send it again so I can review the new version? @bruquevedo |
ok |
I received the email in the inbox and everthing is ok |
inbox and link tracked working as it should. |
@vjpixel could you please review the issu? |
There's a bug on our emails, described in #85. I propose that we fix the bug and send the test again. |
@vjpixel can I already send it? |
We agreed to discuss before sending it. |
We fixed the problem in the issue #85 as you can check there. |
email received at the inbox. the two links to |
|
Same here. |
Since we decided to create the image for the next week in this Sprint, I put the deadlines for both products in the description. |
Since the revision protocol will be implemented inside this issue, I included it (and deadline) in the description. |
@tiagobugarin and @vjpixel I sent the email test for sprint 0.0.5 yesterday. Please follow this steps to check the email (this is my suggestion of revision protocol): 1- Did you receive the email in the inbox?; |
1 - Yes; |
1 - Yes; I'll wait for the link so I can review it again. I propose you just ask for people to review after you have reviewed yourself and consider it done. |
Concerning to the second email:
|
@vjpixel could you please review this issue? |
I checked, and it's working great! |
0.0.4 Deadline: Tue 10:00
0.0.5 Deadline: Thu 16:00
Revision protocol deadline: Fri 12:00
Test with different people if the email is arriving and looking/working as it should.
We need to send a test email to the team so everyone can review it before we send the final version.
We want to improve this issue including a revision protocol.
The text was updated successfully, but these errors were encountered: