We always provide upgrade paths from one released version (stable or
beta) to the next. The exceptions to this are the alpha releases, where
we clearly state that upgrades may not be possible, and XML should be
used to upgrade.
However, if we had to guarantee that every time we checked in code to
our source code repository that we maintained full upgrade capability,
work on the program would come to a screeching halt.=20
Each developer depends on changes made by the other developers. Many
times a developer can only take code to a certain (and possibly broken)
point before another developer has to provide additional work. The first
developer cannot continue until the second has accomplished his/her
This is just like running Debian SID - yes, it works 99% of the time,
but every once it a while, it gets really broken for a short period of
time. This is the price that has to be paid if you want to run the up to
the second code that the developers are hacking on.
On Fri, 2006-08-18 at 10:43 +0200, Micha=C3=ABl Van Dorpe wrote:
> On Thu, 2006-08-17 at 22:56 -0700, Alex Roitman wrote:
> > There has been another minor change in grdb format.
> > However, the data created by the svn code in the
> > last two days is garbage again :-)
> Am I fooling myself if I think that I can just checkout an svn revision
> from a couple of days ago, open a file that was created by gramps from a
> revision from the last two days ("garbage"), export it to a .gramps
> file, update my local copy again, and import the .gramps file?
> If so... I'm a little speechless... Is this all the breakage I will ever
> get? :-)
> (I'm not giving up on taking a backup every now and then just yet of
> Closing this e-mail with the official line:=20
> "use non-stable versions for testing only!"
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job ea=
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronim=
> Gramps-devel mailing list