All, So far the 1.6.0 RC2 Testathon seems to be going quite well. Very few bugs have been found, and those found have been minor and easily fixable.
*Code Freeze: March 2* Based on the good results from the Testathon so far, Stuart Lewis & I would like to schedule a complete *code freeze* for Tuesday, March 2 at 15:00 UTC. A complete code freeze means that all code and documentation for 1.6.0 must be committed by that date/time. The current plan is to release 1.6.0 final later that day. If anyone encounters large issues with 1.6.0rc2 that warrant delaying this code freeze, please notify both Stuart ([email protected]) and I ([email protected]) via email. We are willing to delay the code freeze if major issues require the delay. *Committing outstanding code / documentation* This is just a reminder that we are currently under a feature-freeze. This means that no new features should be committed to the Trunk code. However, bug fixes may still be committed assuming the following conditions apply: (1) The bug fix is well tested, stable and necessary (necessary = significant bug, and the fix is approved) (2) Bug fixes should be approved by at least 3 DSpace Committers before committing them (per our current Voting Procedures). If you need quick approval and no one is in #dspace IRC, email Stuart & I, and we can give approval as necessary. (3) Necessary documentation fixes can be committed as they come in, assuming you have the approval of Documentation Guru Jeff Trimble (or are Jeff). *Next Week - No DSpace Developers Mtg* As an FYI, Stuart & I will both be out of town next week (Feb 22-26). However we will be available via email. So, if issues arise, notify us via email and we can help out. As both dev8D and code4lib are going on next week, I have also canceled the DSpace Developers Meeting on Weds, Feb 24. Thanks everyone for all your hard work in the 1.6.0 release! We're definitely in the home stretch now. Let Stuart & I know if you have any questions, concerns or encounter any issues with applying fixes before the code freeze. - Tim -- Tim Donohue Technical Lead for DSpace Project DuraSpace.org ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Dspace-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-devel
