Makes sense. On Aug 5, 2011, at 3:24 PM, Roger L. Whitcomb wrote:
> What if we do this? > - We need a tag for a release version, so do a "2.0.1" tag, > - We will need continued work on further 2.0.x releases, so make a 2.0.x > branch > - Change trunk to be the 2.1 working version > > Roger Whitcomb | Architect, Engineering | [email protected] | > Ingres | 500 Arguello Street | Suite 200 | Redwood City | CA | 94063 | > USA +1 650-587-5596 | fax: +1 650-587-5550 > > -----Original Message----- > From: Sandro Martini [mailto:[email protected]] > Sent: Friday, August 05, 2011 12:21 PM > To: [email protected] > Subject: Re: Propose 2.0.1 release > > Thinking on it I think that we could start next week the proposal for > the > 2.0.1 , but please don't create a branch in svn, maybe create a tag > instead, > so in the meantime we can continue to work on 2.0.x ... do you like this > ? > What others think ? > > Bye > Il giorno 05/ago/2011 20:12, "Roger L. Whitcomb" > <[email protected]> > ha scritto: >> I'd like to propose we release 2.0.1 ASAP. I know there are a few >> things Sandro still has on his plate, but I'm thinking they are not >> crucial to have in 2.0.1 necessarily. >> >> >> >> Can I get help testing to make sure everything is stable? I've been >> testing with our app for literally months now, tracking head revs of >> "trunk" and it is certainly very stable for us, and I'd like to get a >> released version with the crucial bug fixes, etc. that are contained > in >> it. >> >> >> >> Comments? Thanks. >> >> >> >> Roger Whitcomb >> >> Architect, Engineering >> >> Ingres Corporation >> >> [email protected] <mailto:[email protected]> >> >> >> >> PHONE +1 650.587.5596 >> >> FAX +1 650.587.5550 >> >> >> >> www.ingres.com <http://www.ingres.com/> >> >> >> >> This transmission is confidential and intended solely for the use of > the >> recipient named above. It may contain confidential, proprietary, or >> legally privileged information. If you are not the intended recipient, >> you are hereby notified that any unauthorized review, use, disclosure > or >> distribution is strictly prohibited. If you have received this >> transmission in error, please contact the sender by reply e-mail and >> delete the original transmission and all copies from your system. >> >> >>
