=================
DEVELOPMENT NOTES
=================
:Last update: $Date: 2007-12-18 14:32:42 +0100 (Di, 18 Dez 2007) $
:Revision: $Revision: 8 $
:Contact: p@rdus.de
Development
-----------
If you want to follow development you should run
dev-pardalys
The tool can be found in the 'bin' subdirectory (or in /usr/bin if you
installed pardalys in your system). It will checkout the master branch
of pardalys from github.com and place it in
/usr/share/pardalys/dev-pardalys.
If you want to be able to commit your fixes you can fork the main
repository from http://github.com/wrobel/pardalys/tree/master to your
own github.com account.
Then use
dev-pardalys -u YOUR_ACCOUNT -s
in order to retrieve your forked version over ssh (Note: You will have
to put your public SSH key on github.com for this to work).
After that you can start modifying the sources and commit to your
fork. Once you are pleased with the results you may send a pull requst
to the main repository on github.com. If your changes have the
required quality they will get integrated in the main repository.
Changes
-------
1) Any change should get a short ChangeLog entry.
2) Bigger changes, feature enhancements and closed bugs go into
CHANGES
3) The RELEASE_NOTES should contain a summary for the current release
as well as a list of enhancements and closed bugs.
Versions
--------
The version number is being recorded in the Makefile
The version number for release packages has three numbers.
CVS versions have the date of the last commit appended.
Authors
-------
Please do not forget to add new authors or contributors within
AUTHORS.
Release management
------------------
No instructions yet.
Branches
--------
No branches yet.
Documentation
-------------
No documentation yet.
Testing
-------
No tests yet.
Release
-------
1) README, INSTALL and HACKING up-to-date?
2) Make sure ChangeLog is up-to-date
3) Update CHANGES for the next release
4) Copy CHANGES to RELEASE_NOTES (short or long)?
5) Write a release comment in RELEASE_NOTES, set focus
6) Commit to git
7) Commit to subversion
8) Run "make release"
9) Prepare the sourceforge release
10) Prepare the freshmeat announcement
11) Prepare the ebuild
12) Announce the package on the forum/blog
