i do look at it (as do others) but this year with all the integration work we are doing, we've focused more on the integration work and maintenance releases to fix defects. since the loyalty database is what is/was used with WorldPerks, that's required a LOT of testing to ensure that functionality that exists continues to exist. rather that further complicate all the regression testing with lots new features and enhancements (there are some though), the focus is regression regression regression.

one thing that i hope everyone understands is that just because it seems straightforward and/or easy to do, doesn't mean it is. the most recent example i can think of was with stored preferred trips and the changes to loyalty. what we thought should be fairly easy and maybe an hour or three, once we "lifted the hood" turned into something that i ended up jumping in to help on and took me about 2 days to properly handle all the conditions where it is available.