That migration route will certainly be supported. > -----Original Message----- > From: Clay Andres [mailto:[EMAIL PROTECTED]] > Sent: Friday, January 18, 2002 11:05 AM > To: TechRocks Support > Subject: [support] RE: How to get started > > > This is both useful information and helpful advice. I'll assume that we > are better off starting our database in 1.03 and then migrating to 2.0 > in a couple of weeks when it's finished. Feb 2, seems soon, but I think > we need to start entering data somewhere and this seems like the safest > route. > > On Friday, January 18, 2002, at 10:43 AM, Bob Schmitt wrote: > > > Hi! > > > > Clif and I are exploring "extreme programming" techniques this week > > and came up for air long enough to catch this thread. > > > > As we've gone through the code consolidation and clean-up process > > (and at the same time tested some of the v2 beta assumptions), we've > > had to change a significant number of fields and one or two key > > procedures (e.g. how to assign a primary location for a contact > > record; how to track an organization or family as well as > > individuals, and so on). > > > > Many key fields have been renamed for consistency and > > comprehensibility (we've changed some pedagogical metaphors), and > > some have been consolidated to make things a little more manageable. > > > > In short, you should be looking at the v2 beta as a sketch of what we > > were think instead of the final product. > > > > At this point I think we're done messing with what's there, and we'll > > only be adding fields and features from here on out (unless we find > > other major glitches, particularly in the incremental find procedure). > > > > We're embarking on the last "feature" push over the next couple of > > weeks and will be releasing a "feature complete" version to > > developers on Feb. 2 (or the Monday after) that will have the fields > > locked down. > > > > That said, when we release v2, we will also produce a "change report" > > that lists the field changes from v2 beta to v2. It would be best if > > you could hold off using the v2 beta in production, but if you > > absolutely can't, we will provide a some documentation to help you > > map the move from v2 beta to ebase 2.0. > > > > Hope this helps, > > > > bob > > > Clay Andres > Director of Development > Connecticut Conservatory of the Performing Arts > www.ctconservatory.com > 860.868.4002 (home office) > > > ------------------ > Reminder to each recipient: To change your list account preferences, go to > http://email.sparklist.com/scripts/lyris.pl?enter=support and > enter the email address you used to subscribe to the ebase > support list:: [EMAIL PROTECTED] > > To unsubscribe send a blank email to [EMAIL PROTECTED] > --------------------------------------------------------------------- > ebase - Relationship Management for Nonprofits, http://www.ebase.org > --------------------------------------------------------------------- > > >
------------------ Reminder to each recipient: To change your list account preferences, go to http://email.sparklist.com/scripts/lyris.pl?enter=support and enter the email address you used to subscribe to the ebase support list:: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] --------------------------------------------------------------------- ebase - Relationship Management for Nonprofits, http://www.ebase.org ---------------------------------------------------------------------
