Comment 3 for bug 1050384

Hmm, since the solution proposed here is to add the example PINES views by default for new installations, I might suggest that this is not necessarily a bug fix that's to be backported to previous versions, but a new feature that these PINES example views are now to be included by default from now on in Evergreen.next (in this case, 2.9).

The question is, should we add a note in the version-upgrade script to tell folks to go ahead and run the example view sql on their systems for consistency? Or would that be presumptuous? What about users who have already taken the example views and customized them to fit their personal needs? Asking them to run the script now would overwrite anything that they have set up locally. I only mention that possibility because I know we've done it.

For consistency, I agree that it'd be nice to include these by default for new installations, but moving forward past that point, once they are considered default views, we need to come up with a strategy for supporting them and maintaining these views from now on.

Removing pullrequest and targets pending further discussion on approaches for this bug...