Hi, On 26 August 2011 12:18, Dave Martin <dave.mar...@linaro.org> wrote: > Hi there > > A few questions-- > > a) Is the omission of the "Developers and Community Builds" links from > http://www.linaro.org/downloads/ intentional?
Yes, it is. We made the choice to promote only the officially supported builds on the downloads page. Developers and Community Builds (DCBs) are not officially supported. > This is a concern,because these links contain the _only_ deliverables for > certain platform and filesystem combinations. Thanks for raising your concern. I don't have a good answer yet. The website is being worked on and the goal is to get rid of the wiki release page, which is a convenient way to present the release and get the related information today. We'll see in which way the website could be improved to resolve your concern. > The wiki release page itself is not easily findable without going to the wiki. Really? It's clearly mentionned on the release announcement, posted on planet. Obviously, if somebody miss the announce and goes directly to the website downloads page, he won't get the DCBs. Is it your point? > b) The release page on the wiki contains important information like > the list of known issues.Shouldn't this page be linked from > http://www.linaro.org/downloads/ or some other prominent location? It can probably be added to the block on the right. IMO the known issues are part of the release notes, I don't see them on the downloads page. > I don't see how to get to it at present. A visitor won't know that they > have to go to the wiki for this information. I think that the main problem here is that we use the release notes as the main portal for the release. In your use case, somebody using the website downloads page to get into Linaro won't get the release notes and will miss important information (DCBs, known issues, etc...). > c) The known issues list on the wiki release page doesn't seem include > all the issues reported during testing. Will these get propagated, or > is it the responsibility of testers to add the relevant information to > the known issues list themselves? The known issues list includes all the critical/high issues raised to the release team. It means that any individual need to subscribe linaro-release to the issue to have it under our radar. Also, I go through the testing reports to gather the known issues. Medium/low issues are skipped because the list could be quite long with the number of components we have. > d) For vexpress specifically, there is no link from the release pages > or downloads to the specific installation instructions applicable to > this board. Even I find these difficult to find without bookmarking. > Because that information is very board-specific, I don't think it > needs to be included on > https://wiki.linaro.org/Platform/DevPlatform/Ubuntu/ImageInstallation > -- but can we at least have a link on there pointing to the > appropriate page? I have the same concern. We have per board instructions: * on the forms used for testing. e.g. http://bit.ly/pFnQQh * on releases.l.o e.g. http://releases.linaro.org/platform/linaro-n/ubuntu/leb-panda/11.08/ IMO, the image installation should be board specific. The generic instructions are good but I would prefer to have the following workflow: 1. I have this board (identify board) 2. I need these images (identify images for the board) 3. Here's the correct step by step instructions to flash my board Now, we need to the improve the image installation to achieve that... > Cheers > ---Dave _______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
