Jira (PUP-6135) change type mismatch errors in past tense to present tense
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6135 change type mismatch errors in past tense to present tense Change By: Henrik Lindberg Release Notes Summary: The messages about type mismatch errors have been modified to use more consistent wording for different kinds of mismatches. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6135) change type mismatch errors in past tense to present tense
Title: Message Title Eric Thompson commented on PUP-6135 Re: change type mismatch errors in past tense to present tense i'm not sure if this needs a release notes blurb or not, nor what type it would be... "bug fix"? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6135) change type mismatch errors in past tense to present tense
Title: Message Title William Hopper assigned an issue to qa Puppet / PUP-6135 change type mismatch errors in past tense to present tense Change By: William Hopper Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6135) change type mismatch errors in past tense to present tense
Title: Message Title Craig Gomes updated an issue Puppet / PUP-6135 change type mismatch errors in past tense to present tense Change By: Craig Gomes Sprint: PDS 2016-09-21 , PDS 2016-10-05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6135) change type mismatch errors in past tense to present tense
Title: Message Title Henrik Lindberg commented on PUP-6135 Re: change type mismatch errors in past tense to present tense merged to master at: f4b86e0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6135) change type mismatch errors in past tense to present tense
Title: Message Title Henrik Lindberg commented on PUP-6135 Re: change type mismatch errors in past tense to present tense After a bit of discussion I think we concluded that we should say "expects" as that should work in all cases since they expectancy still exists in all cases. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6135) change type mismatch errors in past tense to present tense
Title: Message Title Thomas Hallgren commented on PUP-6135 Re: change type mismatch errors in past tense to present tense The description uses mixed tense in that 'has' is present tense, but 'expected' is past tense. I think that makes sense. It's however very common to use past tense overall. So while fixing this bug, do we want to consequently use mixed tense throughout with wording like "X has/Z returns/X references/ zzz, expected xxx, got yyy"? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6135) change type mismatch errors in past tense to present tense
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-6135 change type mismatch errors in past tense to present tense Change By: Thomas Hallgren Sprint: PDS Triage 2016-09-21 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6135) change type mismatch errors in past tense to present tense
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-6135 change type mismatch errors in past tense to present tense Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6135) change type mismatch errors in past tense to present tense
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6135 change type mismatch errors in past tense to present tense Change By: Henrik Lindberg Fix Version/s: PUP 4.6.0 Fix Version/s: PUP 4.7.0 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6135) change type mismatch errors in past tense to present tense
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6135 change type mismatch errors in past tense to present tense Change By: Henrik Lindberg Sprint: Language Triage, Language 2016-05-04 , Language 2106-06-01 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6135) change type mismatch errors in past tense to present tense
Title: Message Title Steve Barlow updated an issue Puppet / PUP-6135 change type mismatch errors in past tense to present tense Change By: Steve Barlow Fix Version/s: PUP 4.5.0 Fix Version/s: PUP 4.6.0 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6135) change type mismatch errors in past tense to present tense
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6135 change type mismatch errors in past tense to present tense Change By: Henrik Lindberg Sprint: Language 2016-05-04, Language 2016 2106 - 05 06 - 18 01 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6135) change type mismatch errors in past tense to present tense
Title: Message Title Steve Barlow updated an issue Puppet / PUP-6135 change type mismatch errors in past tense to present tense Change By: Steve Barlow Sprint: Language 2016-05-04 , Language 2016-05-18 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6135) change type mismatch errors in past tense to present tense
Title: Message Title Sean Griffin updated an issue Puppet / PUP-6135 change type mismatch errors in past tense to present tense Change By: Sean Griffin QA Risk Assessment: Low QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6135) change type mismatch errors in past tense to present tense
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-6135 change type mismatch errors in past tense to present tense Issue Type: Improvement Assignee: Unassigned Created: 2016/04/06 5:33 PM Fix Versions: PUP 4.5.0 Priority: Normal Reporter: Henrik Lindberg Errors like attribute 'a' had wrong type, expected a Type value, got Integer/ are weird, because they allude to that the thing was wrong in the past as opposed to still being wrong, which it is (unless it was corrected by magic intervention). There is no problem in saying "attribute 'a' has wrong type, expected a Type value, got Integer" since the test was performed in the past (a small amount of time ago). This is however painful to change as there are quite a few tests that are based on matching on the error messages.
