[ros-users] [Discourse.ros.org] [General] Community Software Release Announcements - Guideline

Daniel Stonier ros.discourse at gmail.com
Sun Feb 12 12:40:52 UTC 2017




**About**

Do you have a shiny new release you'd like to announce to the community or are you just interested in keeping track of what is new and shiny? This guideline is to help provide us (the community) with a convention that will make this easier.

**Announcing**

* Post in the **General Category**
* Add the tag **release**

An announcement thread should be primarily focused on pointing people at the right places and getting them started.

Both source and binary (e.g. OSRF build farm) release announcements are encouraged. Provide a small introduction, some indicator of its status, pointers to links showing how people can get started with your release. You might also like to mention what you're looking for as well - e.g. are you looking for collaboration or use cases to help drive some experimental design or feedback to decide whether there's interest enough to support a source release as a binary release? This can help users more readily align with you.

It *should not* contain documentation or instructions (point to links elsewhere) nor technical questions/answers (redirect to issue trackers, ros answers or similar).

**Tracking**

If you do not wish to track the high volume general category itself, simply set your preferences to follow the *release* tag. 

**Browsing**

You can [browse](https://discourse.ros.org/tags/release) all previously release announcements by searching for the *release* tag.

----------
_Looking forward to hearing about your latest and greatest!_

----------

> This is a culmination of the discussions in [this thread](https://discourse.ros.org/t/new-software-release-announcements/1203/28) in which it was recognised that alot of great software was being written in the community, but these were not readily being found.






-- 
[Visit Topic](https://discourse.ros.org/t/community-software-release-announcements-guideline/1305/1) or reply to this email to respond.




More information about the ros-users mailing list