using scan-line polygon conversion for constructing wxregion

[wxWidgets.git] / docs / tech / tn0022.txt

diff --git a/docs/tech/tn0022.txt b/docs/tech/tn0022.txt
index 7bcac24c83f92c26c7be80eb3b40b3df39941ba3..65bfbb1c876716687a8e33ec372ad8e55a886eab 100644 (file)
--- a/docs/tech/tn0022.txt
+++ b/docs/tech/tn0022.txt
@@ -11,6 +11,8 @@ Put a date on the release line in docs/changes.txt.
 
 Update the date in the manual (docs/doxygen/mainpages/manual.h).
 
 
 Update the date in the manual (docs/doxygen/mainpages/manual.h).
 

+Update the release announcement post in docs/publicity/announce.txt.
+

 
 Creating release files
 ----------------------
 
 Creating release files
 ----------------------


@@ -68,13 +70,36 @@ Uploading
 
 Upload the files to SourceForge. This can be done via the web interface or just
 scp to sfusername,wxwindows@frs.sf.net:/home/frs/project/w/wx/wxwindows/x.y.z
 
 Upload the files to SourceForge. This can be done via the web interface or just
 scp to sfusername,wxwindows@frs.sf.net:/home/frs/project/w/wx/wxwindows/x.y.z

+The following files need to be uploaded:
+
+    wxMSW-Setup-2.9.3.exe
+    wxWidgets-x.y.z.7z
+    wxWidgets-x.y.z.tar.bz2
+    wxWidgets-x.y.z.zip
+    wxWidgets-x.y.z_Headers.zip
+    wxWidgets-docs-chm-x.y.z.zip
+    wxWidgets-docs-html-x.y.z.tar.bz2
+    wxWidgets-docs-html-x.y.z.zip
+

 You will need to use the web interface to mark the latest uploaded files as
 being "default downloads" for the appropriate platforms (.zip or .exe for MSW,
 .tar.bz2 for everything else) as otherwise SourceForge would continue to suggest
 people to download old files.
 
 You will need to use the web interface to mark the latest uploaded files as
 being "default downloads" for the appropriate platforms (.zip or .exe for MSW,
 .tar.bz2 for everything else) as otherwise SourceForge would continue to suggest
 people to download old files.
 

-Also upload docs/release_files.mdwn as README.md to display it by default when
-its directory is viewed on the web.
+Next, update (at least the versions and SHA1 sums, but maybe more) and upload
+docs/release_files.mdwn and docs/release_binaries.mdwn files. They need to be
+renamed to README.md on SF to be shown when the directory is viewed, i.e. do:
+
+    scp docs/release_files.mdwn \
+        sfuser,wxwindows@frs.sf.net:/home/frs/project/w/wx/wxwindows/x.y.z/README.md
+    scp docs/release_binaries.mdwn \
+        sfuser,wxwindows@frs.sf.net:/home/frs/project/w/wx/wxwindows/x.y.z/binaries/README.md
+
+And upload the change log too:
+
+    scp docs/changes.txt \
+        sfuser,wxwindows@frs.sf.net:/home/frs/project/w/wx/wxwindows/x.y.z
+

 
 Also upload the files to the FTP mirror at ftp.wxwidgets.org (ask Chris for
 access if you don't have it).
 
 Also upload the files to the FTP mirror at ftp.wxwidgets.org (ask Chris for
 access if you don't have it).


@@ -85,13 +110,15 @@ Create http://docs.wxwidgets.org/x.y.z/ (ask Bryan to do it if not done yet).
 Announcement
 ------------
 
 Announcement
 ------------
 

-Post announcement at least to wx-announce@googlegroups.com.
+Post docs/publicity/announce.txt at least to wx-announce@googlegroups.com.

 
 TODO: where else to announce it?
 
 Update www.wxwidgets.org, usually a news item is enough but something more can
 be called for for major releases.
 
 
 TODO: where else to announce it?
 
 Update www.wxwidgets.org, usually a news item is enough but something more can
 be called for for major releases.
 

+Also update downloads/index.html to mention the new latest release.
+

 Post to wxBlog if necessary.
 
 
 Post to wxBlog if necessary.