| | 1 | = Release Coordination = |
| | 2 | |
| | 3 | This page acts as a status whiteboard for this release of Haiku. It should contain a list of tasks that need to be completed. |
| | 4 | == Task List == |
| | 5 | |
| | 6 | This is a list of tasks that need to be done in preparation for the alpha 1 release. Do you see a task that still needs someone to take care of it? Drop a line on the [http://www.haiku-os.org/community/ml Haiku-Development] mailing list. |
| | 7 | |
| | 8 | === Build Tasks === |
| | 9 | ||'''task'''||'''due'''||'''assignee'''||'''notes'''|| |
| | 10 | ||Assign buildmeister|| - || - || |
| | 11 | ||Determine distribution structure|| - || - || |
| | 12 | ||Determine optional packages to be included|| - || - || - || |
| | 13 | ||Set up a test framework/formal list of requirements|| - || - || |
| | 14 | |
| | 15 | === Release Preparation === |
| | 16 | ||'''task'''||'''due'''||'''assignee'''||'''notes'''|| |
| | 17 | ||Find mirrors|| - || - || |
| | 18 | ||Write release notes|| - ||everyone||See wiki page ReleaseNotes || |
| | 19 | ||Write press release|| - || - || |
| | 20 | ||Determine press plan|| - || - || |
| | 21 | |
| | 22 | === Website === |
| | 23 | ||'''task'''||'''due'''||'''assignee'''||'''notes'''|| |
| | 24 | |
| | 25 | |
| | 26 | === Release === |
| | 27 | ||'''task'''||'''due'''||'''assignee'''||'''notes'''|| |
| | 28 | ||Branch the source tree|| - || - || |
| | 29 | ||Backport important bug fixes|| - || - || |
| | 30 | ||Tag the final build|| - || - || |
| | 31 | ||Make source available|| - || - || |
| | 32 | ||Test final build|| - || - || |
| | 33 | ||Distribute final build to mirrors|| - || - || |
| | 34 | |
| | 35 | Note, dates are in dd-mm-yyyy format. |
| | 36 | |
| | 37 | == Release Schedule == |
| | 38 | |
| | 39 | * Branching trunk : - |
| | 40 | * Final testing before tagging branch : - |
| | 41 | * Tagging branch : - |
| | 42 | |
| | 43 | The testing of the build is expected to take a few days (pending any unforeseen problems). The website team will also require a few days to upgrade the website in order to support the release. The expected release date is around '''DATE'''. |
| | 44 | |
| | 45 | |
| | 46 | == Proposals == |
| | 47 | |
| | 48 | There was a discussion, then followed a vote, and now we have a list of proposals for this release. Below is the final list of accepted proposals. |
| | 49 | |
| | 50 | |
| | 51 | == Status Updates == |
| | 52 | |
| | 53 | The status updates give an overview of the progress that is made towards this release. |
| | 54 | |
| | 55 | |
| | 56 | == Blocker issues == |
| | 57 | |
| | 58 | These need to be fixed in order to release the alpha. |
| | 59 | |
| | 60 | '''EDIT TicketQuery:'''[[TicketQuery(priority=blocker&status=new|assigned|reopened&milestone=R1/alpha1)]] |
| | 61 | |
| | 62 | '''EDIT TicketQuery:''' Total of [[TicketQuery(status=new|assigned|reopened&priority=blocker&milestone=R1/alpha1,count)]] open ticket(s). |
| | 63 | |
| | 64 | == Critical issues == |
| | 65 | |
| | 66 | If all the ''blocker'' items are resolved, these should be evaluated whether or not they block the alpha release. |
| | 67 | |
| | 68 | '''EDIT TicketQuery:'''[[TicketQuery(priority=critical&status=new|assigned|reopened&milestone=R1/alpha1)]] |
| | 69 | |
| | 70 | Total of '''EDIT TicketQuery:'''[[TicketQuery(status=new|assigned|reopened&priority=critical&milestone=R1/alpha1,count)]] open ticket(s). |
| | 71 | |
| | 72 | == High priority issues == |
| | 73 | |
| | 74 | This is a list of items with things that would be very much appreciated for this release, but they will not delay the release. |
| | 75 | |
| | 76 | '''EDIT TicketQuery:'''[[TicketQuery(priority=high&status=new|assigned|reopened&milestone=R1/alpha1)]] |
| | 77 | |
| | 78 | Total of '''EDIT TicketQuery:'''[[TicketQuery(status=new|assigned|reopened&priority=high&milestone=R1/alpha1,count)]] open ticket(s). |
| | 79 | |
