On Mon, Aug 13, 2012 at 9:35 AM, Bill Erickson <erick...@esilibrary.com> wrote: > > Hi All, > > I'm planning on cutting 2.3.beta2 this Friday 8/17. Keep the bug fixes > rolling! > > After that comes the 2.3.rc1 release candidate on August 31st. I'm not > anticipating an RC2, but we can certainly squeeze one in if necessary. > > <policy> > How do we characterize bug fixes that are allowed to be merged between RC1 > and GA? I assume we should limit to showstoppers only? > </policy>
IMO (and likely debatable), we shouldn't cut RC until showstoppers are in, and post-RC bug fixes should be limited to low-impact or high-priority fixes. Thoughts? -- Mike Rylander | Director of Research and Development | Equinox Software, Inc. / Your Library's Guide to Open Source | phone: 1-877-OPEN-ILS (673-6457) | email: mi...@esilibrary.com | web: http://www.esilibrary.com
