Re: Bug#197049: ITP: conglomerate -- an XML editor for GNOME
On Sun, Jun 15, 2003 at 08:14:57AM -0500, Manoj Srivastava wrote:
> On Sat, 14 Jun 2003 09:33:02 +0200, Sven Luther <sven.luther@wanadoo.fr> said:
>
> > On Fri, Jun 13, 2003 at 04:54:23PM -0500, Manoj Srivastava wrote:
> >> On Fri, 13 Jun 2003 16:49:15 +0200, Sven Luther
> >> <sven.luther@wanadoo.fr> said:
> >>
> >> > On Thu, Jun 12, 2003 at 11:48:10AM -0500, Manoj Srivastava wrote:
> >> >> On Thu, 12 Jun 2003 18:12:03 +0200, Sven Luther
> >> >>
> >> >> > So it should be ok if i upload the package to unstable, even
> >> >> > if the package crashes often, and thus, since it is an XML
> >> >> > editor, the user can loose part of its work ?
> >> >>
> >> >>
> >> >> *Sigh*. Rules of thumb are no subst=itute for common sense or
> >> >> thinking.
> >> >>
> >> >> Did I not say data loss is reason enough for experimental?
> >> >>
> >> >> > At least i should add a warning in the long description then
> >> >> > or something such ?
> >> >>
> >> >> If it causes data loss, you should use experimental.
> >>
> >> > Well, the difference is between data loss on the disk and loss of
> >> > currently editing stuff.
> >>
> >> Is it your contention that it is useful for us to make that
> >> distinction? Why?
>
> > Because if it crashes before you have had time to enter any
> > meaningfull data, as it was doing, it is less grave as when it
> > crashed after hours of work. Also, i think you can distinguish
> > between an app causing random data loss of other data and an app
> > causing loss of his own data.
>
> I beg to differ. In geberal, after I spend 12 hours
> painstakingly entering data, and it is all lost, I am more likely to
> be annoyed than if it corrupted some data on the disk and I had to
> just restore from the nightly backup.
Ah, but the current problem would happen in the first minute, always, so
unless you type/click/whatever exceptionnaly fast, you don't loose much.
0.5.3 closed this problem though, will test the now release 0.5.4 also.
I am of two minds about this, on one side, conglomerate is now in
experimental, but maybe it could also go into unstable, now that it does
not crash anymore.
Friendly,
Sven Luther
Reply to: