Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Cordova Wiki" for 
change notification.

The "CuttingReleases" page has been changed by AndrewGrieve:
http://wiki.apache.org/cordova/CuttingReleases?action=diff&rev1=32&rev2=33

   1. Start a VOTE thread on the Cordova mailing list. See 
http://markmail.org/message/fzmlzbvt3dgdpfrc and 
http://mail-archives.apache.org/mod_mbox/stdcxx-dev/200601.mbox/%[email protected]%3e
 for good examples.
   1. People review the release candidate and cast their votes accordingly. See 
http://www.apache.org/dev/release.html#approving-a-release and 
http://www.apache.org/dev/release.html#what-must-every-release-contain for 
things to consider.
   1. A majority of at least three +1 votes from the (P)PMC is needed for the 
vote to pass.
-  1. Make the approved release available at 
http://www.apache.org/dist/incubator/cordova/ ( also see 
https://dist.apache.org/repos/dist/release/cordova/ )
+  1. Make the approved release available at 
https://dist.apache.org/repos/dist/release/cordova/
     * TODO: How to do this?
+ 
+ == Final Details ==
+ 
+ === Update cordova.apache.org ===
+ 
+  * Refer to 
[[http://svn.apache.org/viewvc?view=revision&revision=r1478146|this commit]] 
(also includes updating the DOAP file)
+  * And the instructions at UpdatingTheWebsite
+ 
+ === Update the Docs ===
   1. Upload the new docs to http://cordova.apache.org/docs
     * Website README.md explains 
[[https://svn.apache.org/repos/asf/cordova/site/README.md|How to update the 
docs]]
-  1. Update the project website cordova.apache.org to point to the new release 
& new docs
-    * Via UpdatingTheWebsite
-  1. Update the DOAP file at 
http://svn.apache.org/repos/asf/cordova/site/infra/doap_Cordova.rdf to update 
the pointer to the latest release.
+    * Commit should look like 
[[http://svn.apache.org/viewvc?view=revision&revision=r1478171|this one]]
+  1. Ask Michael Brooks to update the docs.cordova.io redirect.
+ 
+ === Announce It! ===
+  1. Be sure to wait 24 hours after uploading the release before announcing in 
order to let the Apache mirrors pick up the file.
   1. Announce the release to the world!
     * TODO: Through what channels?
  

Reply via email to