#230: Fix 'release' target
-------------------------------------+--------------------------------------
Reporter: mrenzmann | Owner: mrenzmann
Type: task | Status: assigned
Priority: minor | Milestone: version 0.9.0 - move to
new codebase
Component: madwifi: makefiles | Version: trunk
Resolution: | Keywords:
Patch_attached: 1 |
-------------------------------------+--------------------------------------
Changes (by mrenzmann):
* patch_attached: 0 => 1
Comment:
== Request for comments ==
The attached patch implements the needed "release" target, please review
and give feedback.
It works like this:
Joe Developer, who needs to have write access to the Subversion repository
of our project, calls "make release" from the top-level directory of his
working copy. make then calls a Bash-script (make-release.bash) which does
the main work:
1. determining the desired type of release (I tried to make this as
comfortable as possible)
2. tagging the new release in the repository (changes to release.h
regarding the release type and release version are applied in this step)
3. exporting the new tag to local disk for packaging
4. creating two tarballs
Joe then has to manually handle the rest of the release procedure, such as
uploading the files to the sourceforge.net File Release System.
When the tag is created in the repository, a new "version" will be added
to Trac. So, as soon as the new release is tagged, users will be able to
file tickets for this release version.
== Give it a test ==
Those of you who have write access to the madwifi.org repository can play
with the script in the playground I've set up at http://trac.madwifi-
test.otaku42.de and http://svn.madwifi-test.otaku42.de.
Check out a working copy from the playground's latest trunk, then run
"make release" inside the working copy. Use the same login credentials
that you use for the main repository. Looking at the playground's Trac
installation you will see that new releases will immediately be available
in the "version" field for new tickets, for example.
== Release planned for Monday (2006-05-29) ==
Given that there are no objections regarding the script/target and given
that no-one speaks up and lets us know about things we have forgotten, I
plan to commit the needed changes to the main repository next Monay (May
29th) and package our first release (yay!)
--
Ticket URL: <http://madwifi.org/ticket/230>
MadWifi <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity
