Re: AnyData2/DBD::AnyData2 co-maint
"H.Merijn Brand" <[email protected]>
| Newsgroups | gmane.comp.lang.perl.modules.dbi.sybase.devel |
|---|---|
| Message-ID | <[email protected]> |
On Fri, 24 Apr 2015 09:19:03 -0500, David Nicol <[email protected]> wrote: > I look forward to being able to brag that DBIx::bind_param_inline is > "Approved by the Berlin DBI Committee" or equivalent. As there is no, never was, nor will there be a "Berlin DBI Committee" feel free to brag as you wish :P What *will* be published is a document with advisories on how module authors are expected to behave once there modules are "hot". The document will have three levels of advice * New modules should do/have/follow/... * Modules that are heavily depended on should do/have/follow/... * Core- and toolchain modules should do/have/follow/... The document is there to serve a list of Best Practices and make the module authors maintainers and co-maintainer be more aware of what their changes might/will cause downriver. -- H.Merijn Brand http://tux.nl Perl Monger http://amsterdam.pm.org/ using perl5.00307 .. 5.21 porting perl5 on HP-UX, AIX, and openSUSE http://mirrors.develooper.com/hpux/ http://www.test-smoke.org/ http://qa.perl.org http://www.goldmark.org/jeff/stupid-disclaimers/
signature.asc
(application/pgp-signature, 490 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJVOlfrAAoJEAOhR6E+XcCY2LQIAKG6dQamn4j2IQ2JLayY9yeb /yTyMj04jEOr4RZavHgXunLx1chily6Sun5Pt9JUNmP0FaEJ1FYW+r6VTtjf7DMT +rHziM6sunsv3wRZq6k21o5oRw5p+WlG+b2ErA2BczEjfwhwejn6KdDEoIEd+nkf YEGXhLX9VCEPhMhtavDXEX36aPa4ORNThG8LAUtcrPbkzLcEthJzcpWWC4d59a8L wwNcMidjytjAFSlolLMsPBtt1mmIHOeRwEEWkTdV9VhdzedyfA1zJibFWkrjRjrb 7YOz49f9gXfnOAbWVvP/A5Jz9o+EJlGNMPOWDNRRo/T9rU3xSTJ4abfjmyN0uOI= =hCZj -----END PGP SIGNATURE-----