Thanks for this! :) On Sunday, December 21, 2014 10:26:09 Paul Wise wrote: > On Sun, Dec 21, 2014 at 7:21 AM, Shawn Sörbom wrote: > > I accepted. Now I am wondering, since I will now be doing both upstream > > and > > downstream work, what general guidelines should I use for determining when > > the next release is "ready" for Debian? > > First think about whether the release is ready for people who run the > software, since they are the primary audience. > > Second think about whether the release is ready for all > redistributors, not just Debian. > > Further tips for upstream development: > > Debian recommendations for upstreams are here, please also read the > external advice section. > > https://wiki.debian.org/UpstreamGuide > > You can use check-all-the-things to run various static analysis tools > (and other checkers) over the codebase: > > https://anonscm.debian.org/cgit/collab-maint/check-all-the-things.git > > You can use whohas (I recommend the version in git for now) to find > bugs reported by downstream users, patches created by downstreams, > workarounds for upstream issues in downstream packaging and so on. > > https://github.com/whohas/whohas/ > > I don't have any solution for monitoring mention of the software on > tech sites, forums and social media but maybe you can use web search > engines for this. In the past I have found useful patches in places > like Youtube for example.
-- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/1556725.vcnBPJTXTF@medusa
