What is involved in being a "release manager" in your opinion? And what qualifications does one need?
-Stuart-
Geoffrey Talvola wrote:
IMHO, entering a patch is fine. Before our next release we'll review both the open bugs and open patches.Speaking of a next release, does anyone want to be a release manager for an 0.8 release? It's been so long since our last release that I think we should cut one soon, even though there are still some things in progress like reworking the documentation. Unfortunately, I don't have the time to do it myself. - Geoff-----Original Message----- From: Stuart Donaldson [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 12, 2002 9:44 PM To: Webware devel Subject: [Webware-devel] sourceforge patches vs bugs? I realized that I have put a couple of patches up on sourceforge.net in the patch area that actually fix bugs. In the interest of completeness, should I enter bugs against these? Or is having the patch in the patch database sufficient to get them looked at, and incorporated into the CVS tree? There was talk a short while back about coming out with a 0.8 release pretty soon, and it would be nice to get some of the reported bugs and patches either incorporated, or marked as deferred or rejected for that upcoming release... In summary, the two issues I submitted patches on are: [ 641312 ] addContext call of contextInitialize http://sourceforge.net/tracker/index.php?func=detail&aid=64131 2&group_id=4866&atid=304866 This deals with the a bug where if a module is imported before it is loaded via addContext, the contextInitialize will never get called. [ 642612 ] FancyTraceback fails if source missing http://sourceforge.net/tracker/index.php?func=detail&aid=642612&group_id=4866&atid=304866 This one addresses a problem in the function which returns the source filename of modules in a traceback. If the source file is not in sys.path, or in my case was not in the absolute path it was in when the .pyc file was compiled, then the function failed to return a value which caused the fancytraceback to fail. Note: this is the case for redhat 7.3 python library rpm's because the .pyc files are generated while the .py files are in a temporary location. Anyway, should I enter bugs against these to get them into a queue to be looked at prior to a release? Or is having them in the patch database sufficient? -- Stuart Donaldson -- ------------------------------------------------------- This sf.net email is sponsored by: With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel http://hpc.devchannel.org/ _______________________________________________ Webware-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-devel
