My understanding is that if you've gotten sufficient positive feedback (by your standards) on the package, then you can request to have it migrated, which effectively means that somebody with commits access will put the .info/.patch files into stable.
So you've basically done what's required. Alexander K. Hansen Associate Research Scientist, Columbia University visiting MIT Plasma Science and Fusion Center Levitated Dipole Experiment 175 Albany Street, NW17-219 Cambridge, MA 02139-4213 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steven Tamm Sent: Tuesday, June 03, 2003 10:50 AM To: [EMAIL PROTECTED] Subject: [Fink-devel] vnc-3.3.7-1 migrating to stable Hi *, I'm the package maintainer for vnc-3.3.7, and a couple people were asking me how to get it migrated from unstable to stable. The list archives appear to be down so I couldn't find out for myself. The documentation talks nebulously about how the packages need to be "tested" first. How can I get a package moved into stable? Thanks, -Steven ------------------------------------------------------- This SF.net email is sponsored by: eBay Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel ------------------------------------------------------- This SF.net email is sponsored by: eBay Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
