Sounds good. -A On Mon, Jul 23, 2012 at 12:04 PM, Mark Gardner <[email protected]> wrote: > I like the idea. > > Mark > > On Mon, Jul 23, 2012 at 11:23 AM, Josh Thompson <[email protected]> > wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> I'd like to branch from the 2.3 release to prepare for a bug fix release, >> allowing for 2.4 features to be checked in to trunk. It would make cutting >> 2.3.1 much easier because we wouldn't need to worry about pulling parts out >> or >> testing that new (smallish) features are stable enough to be in a release. >> However, this requires us to apply any bug fixes we make to trunk and to the >> branch. Are others okay with having a branch? I'd suggest that anything >> that >> is actually a bug be filed in JIRA as such, and that those are the only >> things >> we'd check in to the branch. We wouldn't need to be completely strict on >> this. If there was a small feature that would be really helpful to have that >> can be tested well enough, that could be added too if people want it. >> >> Thoughts? >> >> Josh >> - -- >> - ------------------------------- >> Josh Thompson >> VCL Developer >> North Carolina State University >> >> my GPG/PGP key can be found at pgp.mit.edu >> >> All electronic mail messages in connection with State business which >> are sent to or received by this account are subject to the NC Public >> Records Law and may be disclosed to third parties. >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG v2.0.17 (GNU/Linux) >> >> iEYEARECAAYFAlANbG4ACgkQV/LQcNdtPQNhggCeKWXI52pMnU0z/68BlYjHY1/n >> IT4An0b14Eo6aAWIXi8XiHFGV6SBQ+Ah >> =s3Ns >> -----END PGP SIGNATURE----- >> > > > > -- > Mark Gardner > --
-- Aaron Peeler Program Manager Virtual Computing Lab NC State University All electronic mail messages in connection with State business which are sent to or received by this account are subject to the NC Public Records Law and may be disclosed to third parties.
