THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Page History
...
- For installation and usage problems, send to cloudstack-users@incubatorusers@cloudstack.apache.org. There are developers who can help you there. Do not send to cloudstack-dev@incubatordev@cloudstack.apache.org.
- For development discussions, send to cloudstack-dev@incubatordev@cloudstack.apache.org.
- For requirements on features, send to both cloudstack-users@incubatorusers@cloudstack.apache.org and cloudstack-dev@incubatordev@cloudstack.apache.org.
- On replying, if you've determined a certain list is not necessary, strip it from the TO/CC line.
...
Tag | Meaning | ||
|---|---|---|---|
DISCUSS | Discuss a certain topic. Use this tag if you're proposing a feature and is collecting requirements. | ||
VOTE | Voting on a a topic. Use this sparingly and it should be after a discussion has taken place. Before using VOTE, please read the bylaws on what it means. <ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="32ef4272-d4d6-4ffc-9589-3fa253fa4725"><ac:plain-text-body><![CDATA[ | ||
ACS[Release #] | Message regarding a certain release in progress. | ]]></ac:plain-text-body></ac:structured-macro> | |
AWSAPI | Email is regarding the AWS API component of CloudStack | ||
DOCS | Email is regarding CloudStack documentation | ||
EVENT | Email is announcing a CloudStack event | ||
MERGE | Use to discuss merging a branch into another branch | ||
PROPOSAL The list has propose that the DISCUSS tag replaces the PROPOSAL tag. I'm not quite sure why. If anyone knows the reason, please add to this | Use this tag if you are proposing a functional spec, test plan for a feature, and other related documentation. | ||
QA | Email is regarding CloudStack QA effort. <ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="bc2a9956-9df5-4739-bf6f-22267694cae6"><ac:plain-text-body><![CDATA[ | ||
RESULT | This tag is used with the VOTE tag to indicate the voting has concluded and the tallying is indicated in this email. The subject line should look like [VOTE][RESULT]. | ]]></ac:plain-text-body></ac:structured-macro> | <ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="7a653b23-36fb-4637-8930-53906ab3b3cd"><ac:plain-text-body><![CDATA[ |
RESOLVED | This tag is used with other tags to indicate that the original poster believes the discussion has been resolved. The subject line should look like [VOTE][RESOLVED]. | ]]></ac:plain-text-body></ac:structured-macro> | |
OFFLINE | An email message to indicate a contributor is offline from the mailing list for a certain period of days and replies should not be expected. | ||
WIKI | Emails to discuss Wiki content | ||
CI/INFRA | Anything related to the continuous integration systems - build, jenkins, automated tests | ||
SOLVED | When your issue has been resolved by responses to your question please add the SOLVED tag for those searching the archives |
Dealing with the List
- Always use "Reply to All", to keep everyone and mailing list in the thread. Don't be afraid to make a correction if you used "Reply" to single people involved by mistake.
- Rude behavior is not appreciated on the mailing list. Always remember that words in email can sound harsher than the intent when you're reading or writing emails.
- Setup filters on tags will help the traffic flow.
- You may not get a reply. Don't be afraid to resend your email after a few days.
- If you're expecting someone to see your email, include them in the CC/TO line after you sent out the initial email and didn't get a reply.
- Communicate often.
Configuring email clients to work better with the mailing list
| Page Tree | ||||||
|---|---|---|---|---|---|---|
|
Overview
Content Tools
Apps