Difference between revisions of "Release Procedure: Text Files, Documentation and PR"

From Scribus Wiki
Jump to: navigation, search
(Getting the message out)
(Updating documentation files)
Line 4: Line 4:
  
 
==Updating documentation files==
 
==Updating documentation files==
 +
Some doc files need to be updated and translated for every new release, most notably:
 +
 +
* specs.html
 +
* readme.html
 +
* releases.html
 +
specs.html is a complex HTML file and should be edited with LibreOffice Writer Web.
 +
 +
Depending on new/altered/removed features, documentations files, as well as the content.xml file, may require updates or removals.
  
 
==Creating and uploading PDF data sheet==
 
==Creating and uploading PDF data sheet==

Revision as of 07:57, 18 March 2016


Updating text files in the source tree

Updating documentation files

Some doc files need to be updated and translated for every new release, most notably:

  • specs.html
  • readme.html
  • releases.html

specs.html is a complex HTML file and should be edited with LibreOffice Writer Web.

Depending on new/altered/removed features, documentations files, as well as the content.xml file, may require updates or removals.

Creating and uploading PDF data sheet

Creating a Wiki page

Updating the website

Updating the Wiki

Getting the message out

Send out the release notes from the Wiki page minus the logos and in plain text form to the recipients (partners, potential multipliers, press) in the distribution list (currently handled by Christoph). Be careful to separate the three categories, in other words: send one email to all press contacts (using CC or BCC), one to partners etc.

Updating external resources

The most important external resource that needs to be updated is Wikipedia. Note that many of Wikipedia's Scribus pages haven't been updated for years, but some are up to date, especially the major ones (English, German, French, Italian etc.).