Netatalk 1.5 Release Hacking Party ================================== Version 1.1.1 2001-11-22 Corrections, suggestions, and disagreement welcome. Please write to netatalk-devel@lists.sourceforge.net or directly to srittau@debian.org. Date/Place ---------- Sat, 24th November 2001 5pm (17:00) UTC. Feel free to show up earlier or later. Channel #netatalk-devel on irc.openprojects.net. Overview -------- The Netatalk project meets in IRC at the date and place given above to prepare for the next stable release. We will mainly try to build a release that compiles and works on all supported platforms. We will also try to discuss a few points concerning the future development and release coordination of netatalk (see below). Everybody is welcome to join us and help in the release effort. To Do ----- * Testing Main point of this meeting is to create a semi-stable tar-ball that compiles fine and works on all our supported platforms. See below for the platforms that netatalk will be tested on. * Roadmap We should try to come up with a roadmap of what features should be in future versions of netatalk and should be concentrated on. We should also collect problem and bug reports of users. Things that didn't work in the past and that should be worked on. * Sourceforge Tracker Review Netatalk's Sourceforge page employs several trackers: a bug tracker, a support request tracker, and a patch tracker. We should go through these reports, check their validity, and possibly fix or close them. * Release Defaults We still have to agree on some of the default configuration with the new release. While it seems sensible to use the "last" DID scheme by default, we still have to discuss if we want to enable flock locks by default, and there may be further options that could be enabled by default. * Discussion on release management There is still need to discuss the future release management. This concerns mainly the versioning scheme that should be employed in future (it was suggested to make this similar to the Linux kernel's versioning scheme) and the CVS branching and committing policies. Testing Procedure ----------------- The suggested testing procedure is as follows: * I will create a first tar-ball out of the current semi-stable CVS tree. This should be downloaded by all testers and tried out. * We will then collect all problems, try to come up with patches and I will integrate these patches into my local copy of netatalk and come up with another tar-ball. * This will be repeated until compilation works for all tested platforms. * Then I will check in all generated patches into CVS, set a tag and create release candidate 1. The first testing tar-ball (1.5rc0.1) is now available at http://me.in-berlin.de/~jroger/netatalk/. Please report problems with this at the IRC meeting. Participants ------------ The following people are likely to participate in the meeting. Please note that everybody is welcome, and no registration in advance is required. * Dallas Antley Solaris 8 on Sparc 32bit (Sun Workshop 5), possibly NetBSD * Stew Benedict Solaris 7 on Sparc20 (gcc) * Joe Clarke FreeBSD * Steve Freitas Mandrake (Linux) * Gus Holcomb Solaris * Paul Krohn Solaris 8 on Ultra 5, Solaris 2.6 on Ultra 2 (dual processor) (gcc) * Daniel Lautenschleger SuSE Linux * Alain Richard RedHat 7.2, Yellowdog Linux 2.1 PPC * Sebastian Rittau Debian GNU/Linux * Burkhard Schmidt Tru64 * Karen Swanberg OpenBSD 2.9 and 3.0 * Axel Yu RedHat Linux * Craig Zimmerman MacOS X 10.1.1 We are still looking for volunteers for AIX, Ultrix, and SunOS. Changes since 1.0.0 ------------------- * Adjusted participants list. * Roadmap: Do also collect problem and bug reports. * New To Do list entry: Sourceforge Tracker Review. * Test tar balls now available.