Upon testing a feature server, I expected admin/build/features to also check for updates against the feature server. Considering it displays "checking..." and takes a decent amount of time to run through all of your enabled features, this doesn't seem like an unrealistic expectation.
I'd recommend either some simple documentation to say that updates to features are shown on admin/reports/updates or actually working on showing the available updates within the admin/build/features interface. The second approach seems to make the most sense as features would then be checking the validity of the code against the database and against the feature server.. the user experience for features would then be centralized around admin/build/features.
Upon testing a feature server, I expected admin/build/features to also check for updates against the feature server. Considering it displays "checking..." and takes a decent amount of time to run through all of your enabled features, this doesn't seem like an unrealistic expectation.
I'd recommend either some simple documentation to say that updates to features are shown on admin/reports/updates or actually working on showing the available updates within the admin/build/features interface. The second approach seems to make the most sense as features would then be checking the validity of the code against the database and against the feature server.. the user experience for features would then be centralized around admin/build/features.