EWOSP/Release manual: Difference between revisions
From Nasqueron Agora
< EWOSP
No edit summary |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
'''This page seems outdated and contain historical information.''' | |||
== Release steps == | == Release steps == | ||
# Check everything is okay - 3 checklists | # Check everything is okay - 3 checklists | ||
| Line 63: | Line 65: | ||
You can generate them on [http://support.google.com/analytics/bin/answer.py?hl=en&answer=1033867&topic=1032998&ctx=topic this Google support page]. | You can generate them on [http://support.google.com/analytics/bin/answer.py?hl=en&answer=1033867&topic=1032998&ctx=topic this Google support page]. | ||
== See also == | |||
=== GitHub releases API == | |||
See https://github.com/blog/1645-releases-api-preview | |||
[[Category:Notes]] | [[Category:Notes]] | ||
[[Category:Espace Win Open Source Project]] | [[Category:Espace Win Open Source Project]] | ||
Latest revision as of 18:52, 20 September 2021
This page seems outdated and contain historical information.
Release steps
- Check everything is okay - 3 checklists
- Check the infrastructure checklist
- Check the release checlist
- If it's your first release, check the guidelines
- Archive the source in a folder Software-Version you zip (Windows) or tar.gz (Unix)
- Upload
- Blog the new release
- Announce the new release on identi.ca and Twitter and ask RT by our EWOSP account
Infrastructure checklist
- A code repository
- SVN -> On Espace Win this is the link (ask Dereckson to resume this service, it's currently disabled)
- Git -> GitHub (please create an organization account EWOSP) or BitBucket (we already have a EWOSP team, add Dereckson to be added in)
- Mercurial -> Bitbucket
- An entry on cia.vc (currently offline)
- A component in Bugzilla (check here)
Release checklist
- Release should contain a README file with:
- with a link to the bug tracker
- with a link to your software homepage
- with a note about the IRC channel Freenode #EWOSP (you can use http://irc.lc/Freenode/EWOSP as link)
- If this is a binary application, did you compile x64 and x86?
- If this is a .Net application, did you compile it with the smallest framework version required by your code (e.g. 2.0)?
Software EWOSP guidelines checklist
About box
It should contain a link to http://www.espace-win.org/EWOSP.
The link could has as text:
- the URL (with or without http://, without the query string)
- EWOSP
- Espace Win Open Source Project
Add to the link relevant utm parameters:
| Parameter description | Parameter name | Value | e.g. |
| Campaign source | utm_source | the software name | Base64ToolBox |
| Campaign medium | utm_medium | the source | software-aboutbox |
| Campaign term | utm_term | (not used) | |
| Campaign content | utm_content | (not used) | |
| Campaign name | utm_campaign | the campaign name | from-products |
Please always use:
- software-aboutbox for about box
- software-bugreport for a link in the bug report wizard
Document here any software-* keyword you add.
So in fact, you can use this link if you replace Quux by your product name: http://www.espace-win.org/EWOSP/?utm_source=Quux&utm_medium=software-aboutbox&utm_campaign=product
You can generate them on this Google support page.
