release.tem 8.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237
  1. # $Id$
  2. # St. Task Person Date/Time
  3. # [5] 8-59 61-69 71-78
  4. # Status: A - assigned & scheduled
  5. # W - waiting for late predecessors (will be rescheduled after
  6. # predecessor rescheduling/completion)
  7. # R - must be revised, because at least one of predecessors
  8. # has/had to be corrected (executed again)
  9. # N - will _not_ be done this time
  10. # X - finished
  11. # Points with subpoints are finished at the moment, when all subpoints
  12. # are finished.
  13. # Subpoints don't need to have a person and date/time filled in, unless
  14. # different persons are responsible for the main point and some subpoint(s)
  15. # (person and completion time should be either both omitted, or both
  16. # filled in).
  17. # St. Task Person Date/Time
  18. 0 [A] FPC ?.?.? release core team YYMMDDHH
  19. a [A] celebrate the release ;-)
  20. - (30 31)
  21. 1 [ ] Check and update all .msg files
  22. a [ ] errore.msg
  23. b [ ] errord.msg
  24. c [ ] errorf.msg
  25. d [ ] errorn.msg
  26. e [ ] errorr.msg
  27. f [ ] errorrw.msg
  28. g [ ] errores.msg
  29. 2 [ ] New directories
  30. a [ ] Create new directories on FTP and set permission to 700
  31. (using a script ...?)
  32. b [ ] Copy the extra files (asld*.zip, gdb*.zip,
  33. make*.zip, util*.zip) from the old release
  34. 3 [ ] Check tools
  35. - (2)
  36. a [ ] Check version of the above mentioned tools (GNU
  37. tools, helper DLLs, UPX, etc.), and decide whether
  38. it isn't time to update some of these tools
  39. b [ ] Repackage and upload additional tools where needed
  40. 4 [ ] Update version number in the appropriate CVS branch
  41. a [ ] /compiler/version.pas
  42. b [ ] /install/doc/readme.txt
  43. c [ ] /install/fpinst/install.dat (header + cfg template)
  44. d [ ] /install/fpinst/install.pas (installer version)
  45. e [ ] /install/fpc-docs.spec
  46. f [ ] /install/fpc.spec
  47. g [ ] /install/install.sh
  48. h [ ] /html/faq.fp (things like "the latest version
  49. is ...")
  50. i [ ] convert /html/faq.fp to /install/doc/faq.htm and
  51. /install/doc/faq.txt
  52. j [ ] /docs/fpc.sty (macro fpcversion)
  53. 5 [ ] Update whatsnew.txt (/install/doc/whatsnew.txt)
  54. 35 [ ] Finishing all source file updates for the release core team
  55. 6 [ ] Tag CVS with RELEASE_?_?_?
  56. - (1 4 5 35)
  57. 7 [ ] Create and upload zip files for GO32v2
  58. - (2 6)
  59. 8 [ ] Create and upload zip files for OS/2
  60. - (2 6)
  61. 9 [ ] Create and upload zip files for Win32
  62. - (2 6)
  63. 10 [ ] Create and upload tar files for FreeBSD
  64. - (2 6)
  65. 11 [ ] Create and upload tar files for Linux
  66. - (2 6)
  67. 12 [ ] Create and upload Linux RPMs
  68. - (2 6)
  69. 13 [ ] Create and upload Linux DEBs (ask DEB maintainer)
  70. - (2 6)
  71. 14 [ ] Create and upload the documentation
  72. a [ ] docs-pdf.zip
  73. b [ ] doc-html.zip
  74. c [ ] doc-htm.zip
  75. d [ ] docs-txt.zip
  76. 15 [ ] Create and upload source zips
  77. - (7 8 9 10 11)
  78. 16 [ ] Create and upload source tars
  79. - (7 8 9 10 11)
  80. 17 [ ] Run makereleasezips
  81. - (3 14 15 16)
  82. 18 [ ] Test the GO32v2 release
  83. - (17)
  84. a [ ] dos???.zip installation
  85. b [ ] dos???full.zip installation (over the previously
  86. installed dos???.zip to simulate updates)
  87. c [ ] make sure readme.txt & whatsnew.txt are for the
  88. current version
  89. d [ ] run all executables in /bin/go32v2 (no params)
  90. e [ ] make cycle with newly installed binaries and sources
  91. f [ ] run testsuite
  92. g [ ] open the installed hello.pp in IDE
  93. h [ ] make a minor change in the demo in IDE & save it
  94. i [ ] view documentation in IDE, traverse 2-3 pages
  95. (at least one with screenshots)
  96. j [ ] compile the demo file in IDE
  97. k [ ] run the demo within the IDE (debugger)
  98. 19 [ ] Test the OS/2 release
  99. - (17)
  100. a [ ] os2???.zip installation
  101. b [ ] os2???full.zip installation (over the previously
  102. installed os2???.zip to simulate updates)
  103. c [ ] make sure readme.txt & whatsnew.txt are for the
  104. current version
  105. d [ ] run all executables in /bin/os2 (no params)
  106. e [ ] make cycle with newly installed binaries and sources
  107. f [ ] run testsuite
  108. g [ ] open the installed hello.pp in IDE
  109. h [ ] make a minor change in the demo in IDE & save it
  110. i [ ] view documentation in IDE, traverse 2-3 pages
  111. (at least one with screenshots)
  112. j [ ] compile the demo file in IDE
  113. k [ ] run the demo within the IDE (debugger)
  114. 20 [ ] Test the Win32 release
  115. - (17)
  116. a [ ] w32???.zip installation
  117. b [ ] w32???full.zip installation
  118. c [ ] dosw32???full.zip installation (over the previously
  119. installed w32???full.zip to simulate updates)
  120. d [ ] make sure readme.txt & whatsnew.txt are for the
  121. current version
  122. e [ ] run all executables in /bin/win32 and /bin/go32v2
  123. (without parameters)
  124. f [ ] make cycle with newly installed binaries and sources
  125. g [ ] run testsuite
  126. h [ ] open the installed hello.pp in IDE
  127. i [ ] make a minor change in the demo in IDE & save it
  128. j [ ] view documentation in IDE, traverse 2-3 pages
  129. (at least one with screenshots)
  130. k [ ] compile the demo file in IDE
  131. l [ ] run the demo within the IDE (debugger)
  132. 21 [ ] Test the FreeBSD release
  133. - (17)
  134. a [ ] FreeBSD tar installation
  135. b [ ] make sure readme.txt & whatsnew.txt are for the
  136. current version
  137. c [ ] run all executables in /bin/freebsd (no params)
  138. d [ ] make cycle with newly installed binaries and sources
  139. e [ ] run testsuite
  140. f [ ] open the installed hello.pp in IDE
  141. g [ ] make a minor change in the demo in IDE & save it
  142. h [ ] view documentation in IDE, traverse 2-3 pages
  143. (at least one with screenshots)
  144. i [ ] compile the demo file in IDE
  145. j [ ] run the demo within the IDE (debugger)
  146. 22 [ ] Test Linux DEBs
  147. - (17)
  148. a [ ] Linux DEBs installation
  149. b [ ] make sure readme.txt & whatsnew.txt are for the
  150. current version
  151. c [ ] run all executables in /bin/linux (no params)
  152. d [ ] make cycle with newly installed binaries and sources
  153. e [ ] run testsuite
  154. f [ ] open the installed hello.pp in IDE
  155. g [ ] make a minor change in the demo in IDE & save it
  156. h [ ] view documentation in IDE, traverse 2-3 pages
  157. (at least one with screenshots)
  158. i [ ] compile the demo file in IDE
  159. j [ ] run the demo within the IDE (debugger)
  160. 23 [ ] Test Linux RPMs
  161. - (17)
  162. a [ ] Linux RPMs installation
  163. b [ ] make sure readme.txt & whatsnew.txt are for the
  164. current version
  165. c [ ] run all executables in /bin/linux (no params)
  166. d [ ] make cycle with newly installed binaries and sources
  167. e [ ] run testsuite
  168. f [ ] open the installed hello.pp in IDE
  169. g [ ] make a minor change in the demo in IDE & save it
  170. h [ ] view documentation in IDE, traverse 2-3 pages
  171. (at least one with screenshots)
  172. i [ ] compile the demo file in IDE
  173. j [ ] run the demo within the IDE (debugger)
  174. 24 [ ] Test Linux tar release
  175. - (17)
  176. a [ ] Linux tar installation
  177. b [ ] make sure readme.txt & whatsnew.txt are for the
  178. current version
  179. c [ ] run all executables in /bin/linux (no params)
  180. d [ ] make cycle with newly installed binaries and sources
  181. e [ ] run testsuite
  182. f [ ] open the installed hello.pp in IDE
  183. g [ ] make a minor change in the demo in IDE & save it
  184. h [ ] view documentation in IDE, traverse 2-3 pages
  185. (at least one with screenshots)
  186. i [ ] compile the demo file in IDE
  187. j [ ] run the demo within the IDE (debugger)
  188. 25 [ ] Check PDF documentation (open all files)
  189. - (14)
  190. 33 [ ] Check HTML documentation
  191. - (14)
  192. 34 [ ] Check TXT documentation
  193. - (14)
  194. 26 [ ] Read updated text files as distributed in release
  195. zip files
  196. - (17)
  197. a [ ] readme.txt
  198. b [ ] faq.txt
  199. c [ ] whatsnew.txt
  200. 27 [ ] Make new files on FTP available to wide public
  201. - (18 19 20 21 22 23 24 25 26 33 34)
  202. a [ ] open new directories for public access
  203. b [ ] update symlinks
  204. c [ ] move the old version to the olddist/<version>
  205. 28 [ ] Update WWW pages
  206. - (27)
  207. a [ ] /html/news.fp
  208. b [ ] /html/download.fp (links to all individual files
  209. & file sizes)
  210. c [ ] /html/fpc.fp
  211. 29 [ ] Check the WWW pages
  212. - (28)
  213. a [ ] make sure http://www.freepascal.org contains the new
  214. version already
  215. b [ ] read news.html
  216. c [ ] read fpc.html
  217. d [ ] read download.html and check _all_ links
  218. to individual files
  219. 30 [ ] Send announcement to our mailing lists
  220. - (29)
  221. 31 [ ] Post announcement on the community site
  222. - (29)
  223. 32 [ ] Revise / update /html/future.fp after major versions
  224. (?.?.0)
  225. - (28)
  226. #
  227. # $Log$
  228. # Revision 1.2 2001-01-11 16:34:07 florian
  229. # + version must be changed for installer and docs too
  230. # + util*.zip must be copied and checked as well
  231. #
  232. #