Changes between Version 13 and Version 14 of DeveloperInformation


Ignore:
Timestamp:
Aug 15, 2007, 10:51:18 AM (15 years ago)
Author:
Jari Häkkinen
Comment:

Adding release procedures, refs ticket:656

Legend:

Unmodified
Added
Removed
Modified
  • DeveloperInformation

    v13 v14  
    55Documentation needed for the BASE developer is available through [http://base.thep.lu.se/chrome/site/doc/html/developerdoc/developerdoc.html developer information] and
    66[http://base.thep.lu.se/chrome/site/doc/api/index.html BASE 2 API Javadoc].
     7
     8== Release procedure ==
     9
     10ReleaseProcedure -- instructions on how to perform a new release
    711
    812== Test data ==
     
    1620The development plan is available in the [http://base.thep.lu.se/roadmap Roadmap] section above.
    1721
    18 == I want to contribute ==
    19 
    20 Please send an email to the [mailto:basedb-devel@lists.sourceforge.net] mailing list! If you are not subscribed to the list, you should first [http://lists.sourceforge.net/lists/listinfo/basedb-devel register your email address]. Tell us what you want to do, download the source using subversion and hack away. There is a growing [http://base.thep.lu.se/chrome/site/doc/development/ideas.html list of ideas for future development] in BASE.
    21 
    22 From the [http://svnbook.red-bean.com/ Subversion book]: ''If you think that your work is usable for the rest of the community, you should donate your changes to the project After making your modifications to the source code, compose a clear and concise log message to describe those changes and the reasons for them. Then, send an email to the developers list containing your log message and the output of svn diff (from the top of your Subversion working copy). If the community members consider your changes acceptable, someone who has commit privileges (permission to make new revisions in the Subversion source repository) will add your changes to the public source code tree. Recall that permission to directly commit changes to the repository is granted on merit - if you demonstrate comprehension of Subversion, programming competency, and a "team spirit", you will likely be awarded that permission.''
    23 
    2422== Plugin examples ==
    2523
     
    2927the BASE documentation.
    3028
     29== I want to contribute ==
     30
     31Please send an email to the [mailto:basedb-devel@lists.sourceforge.net] mailing list! If you are not subscribed to the list, you should first [http://lists.sourceforge.net/lists/listinfo/basedb-devel register your email address]. Tell us what you want to do, download the source using subversion and hack away. There is a growing [http://base.thep.lu.se/chrome/site/doc/development/ideas.html list of ideas for future development] in BASE.
     32
     33From the [http://svnbook.red-bean.com/ Subversion book]: ''If you think that your work is usable for the rest of the community, you should donate your changes to the project After making your modifications to the source code, compose a clear and concise log message to describe those changes and the reasons for them. Then, send an email to the developers list containing your log message and the output of svn diff (from the top of your Subversion working copy). If the community members consider your changes acceptable, someone who has commit privileges (permission to make new revisions in the Subversion source repository) will add your changes to the public source code tree. Recall that permission to directly commit changes to the repository is granted on merit - if you demonstrate comprehension of Subversion, programming competency, and a "team spirit", you will likely be awarded that permission.''
     34
    3135== robots.txt ==
    3236