File: new_release.html

package info (click to toggle)
releaseforge 1.1-1
  • links: PTS
  • area: main
  • in suites: etch, etch-m68k
  • size: 2,088 kB
  • ctags: 1,239
  • sloc: python: 13,801; makefile: 68; sh: 32
file content (160 lines) | stat: -rw-r--r-- 4,666 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
</head>
<body bgcolor=white>

<table width=100% border=0>
<tr>
<td width="25%" valign=top>
<p>
<h3>Help Sections</h3>
<p>
<ul>
<li><a href="mainwindow.html">Main Window</a>
<li><a href="login.html">Login</a>
<li><a href="config.html">Configuration File</a>
</ul>
<p>

<h3>Create Release</h3>
<ul>
<li><a href="new_release.html">New Release</a>
<li><a href="file_selection.html">File Selection</a>
<li><a href="progress.html">Progress</a>
</ul>
<p>

<h3>Edit Release</h3>
<ul>
<li><a href="edit_release.html">Select Release</a>
<li><a href="edit_release_details.html">Details</a>
<li><a href="edit_release_files.html">File Selection</a>
<li><a href="release_status.html">Edit Release Status</a>
</ul>

<h3>Other</h3>
<ul>
<li><a href="preferences.html">Preferences</a>
<li><a href="news.html">Submit News</a>
<li><a href="freshmeat_setup.html">Freshmeat Setup</a>
<li><a href="freshmeat_release.html">Freshmeat Release</a>
<li><a href="email_setup.html">Email Address Setup</a>
<li><a href="email_announcement.html">Email Announcement</a>
</ul>

</td>
<td width="75%">
<h1>Creating a New Release</h1>

To create a new release you must first select a project and a package from the Main Window and then press the 
<i>Create new release</i> button (<b>note:</b> you can also create a new release by <i>double clicking</i> on 
a package name).
<p>

The release entry wizard will guide you through the steps required to create a new release on SourceForge.  
These steps will be similar to the steps you would normally take when creating a new release on the SourceForge 
website, however, ReleaseForge has streamlined the process and you will benefit from this greatly.

<p>
<center>
<img src="new_release.png"><br>
<font size="-1">Creating a new release</font>
</center>
<p>

The first page of the release wizard provides you the opportunity to:
<br>
<ol>
<li>Enter the name of the new release
<li>Inform SourceForge users that are monitoring this package
<li>Add release notes about this release
<li>Add a change log describing this new release
</ol>

Before you can proceed to the <a href="file_selection.html">next wizard page</a> you must provide a name for 
this new release.  A release name is typically a version number of the package but you are free to use whatever 
name you feel would be meaningful to the users of your SourceForge project.

<p>
<center>
<img src="release_name.png"><br>
<font size="-1">Naming your release</font>
</center>
<p>

You can also choose to notify SourceForge users that are monitoring your project of the impending release.  
The release notification checkbox is <i>checked</i> by default.  If you do not wish to notify SourceForge users 
of this new release, simply <i>uncheck</i> this field.

<p>
<b>Note:</b> The actual notification email will not be sent until the release is succesfully uploaded and 
entered into the SourceForge system.</b>  

<p>
<center>
<img src="release_notification.png"><br>
<font size="-1">Notifying users monitoring the package</font>
</center>
<p>

If you'd like, you can also enter release notes describing this new release.  You have the ability to enter the 
notes manually into the <i>release notes</i> entry field.  The releases notes will automatically word-wrap to 
fit the entry area.

<p>
<center>
<img src="release_notes.png"><br>
<font size="-1">Entering release notes</font>
</center>
<p>

Alternatively, you can import the release notes from a text file.  If you choose to import the release notes you 
can still edit the text manually, as before, however, word-wrapping will be disabled to preserve your desired 
formatting.


<p>
<center>
<img src="release_notes_import.png"><br>
<font size="-1">Importing release notes</font>
</center>
<p>

Similarly, you can enter your <i>change log</i> in the designated entry field.  As in the case of the release 
notes, word-wrapping will automically be applied.

<p>
<center>
<img src="change_log.png"><br>
<font size="-1">Entering the change log</font>
</center>
<p>

Alternatively, you can import the change log from a text file.  If you choose to import the change log you 
can still edit the text manually, as before, however, word-wrapping will be disabled to preserve your desired 
formatting.

<p>
<center>
<img src="change_log_import.png"><br>
<font size="-1">Importing a change log</font>
</center>
<p>

To proceed to the next wizard step, press the <i>next</i> button

<p>
<center>
<a href="file_selection.html"><img src="next.png" border="0"></a><br>
<font size="-1">Advance to the next step</font>
</center>
<p>


</td>
</tr>
</table>
</body>
</html>