It would be unprofessional of us to publish a roadmap of features that everyone wants then later tell you that we had to change plans.
As a software developer with 30 years experience I would counter that it 'is' totally professional to publish a roadmap. Using Agile development as an example various features are selected. Some of those features are core features and some are a stretch or on a 'would be nice' list. Some team members will be occupied with a 'spike' which to non programmers is a research project which 'may or may not' succeed, Usually all of these things will be communicated to the client and as a stake holder their input will be considered on prioritising future features. As a small team I understand that things could be way less formal but there must be some sort of direction and vision driving development. All we're asking for is a little more transparency. We understand that producing something like AFS2 is hard and because you've already produced such an amazing product we're totally cool with falls and stumbles along the way. We'd just like to feel that we're on the journey together