On Mon, 2016-02-22 at 10:04 -0800, Adam Williamson wrote: > This hasn't been a problem so far, because I actually built Wikitcms > and fedfind kinda backwards - their conception of how composes should > be identified is actually derived directly from how we name release > validation events. :P In A World Where my tools don't control the > compose naming concept, and for all the reasons stated above we might > want to give composes very uninformative 'names', this doesn't work any > more. Sorry, I should expand on this. Technically speaking, of course, it still "works". We *can* still do it. The problem is that a page name like: Test Results: Fedora 20160401.n.2 Installation isn't great for humans; it gives you no idea of the meaning of that compose, what testing process it's actually a part of. Even worse would be: Test Results: Fedora 864356 Installation to which the human response is...huh. In a *sane* manual testing system, of course, the compose ID would simply be an internal property that a certain set of validation tests could be mapped to in all sorts of exciting and interesting ways, you can put all kinds of abstraction in there to handle all the possibilities in terms of how we want to relate test instances to composes and what we want to be able to show the user in the UI. But it's a problem in the current Wikitcms design because the page name is where we maintain the mapping between the compose and the event as things stand. (There are various ways I can fix this, all of them fitting in nicely with Wikitcms' general level of stupidity. :>) -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: http://lists.fedoraproject.org/admin/lists/test@xxxxxxxxxxxxxxxxxxxxxxx
