[OGo-Users] Backporting and contributing bugfixes to released OGo version(s)

[Adam Tauno Williams]

--=-9sdoq97p/NEaeUAopuh6
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

> >> I am using r1987, so I guess the bug is in that version. I'll see if=20
> >> updating to trunk version is possible. Otherwise I'll just remove the=20
> >> selection from preferences.
> >> Btw. is there really any difference between the current trunk version=20
> >> and some released version like 1.1.7?=20
> > Bug fixes. :)  Depends on what features you use, but there are no
> > radical differences.
> Ok, that's what I though. We've conventionally used the released=20
> versions for maximum stability. Now we are in the process of building=20
> our own OGo development environment to backport bugfixes from the trunk=20
> to the released versions of OGo (currently 1.1.7).

FYI, you could probably diff 1.1.7 and TRUNK and just bring 1.1.7 up to
TRUNK if you wanted - but then you'd really be using trunk. :)

I've committed most of the patches between 1.1.7 and now, and I can
assure you there is probably nothing you don't want.  The bulk of the
patches have been to zOGI, which if you don't use doesn't affect you.
Beyond that the only *feature* update I can recall is adding qualifiers
AND/OR to the project document search form,  which was a pretty minor
change  (and a change to the sky account CLI tool, but very minor).

If stability is your primary concern probably the one you want to test
most is the change to LSDateAssignmentCommand since changes to Logic
obviously has the most far reaching consequences.  (but we've been
heavily using a version with that change in production for awhile can
haven't had any problems we've noticed since r2036).

see:
http://bugzilla.opengroupware.org/bugzilla/show_bug.cgi?id=3D1915
http://bugzilla.opengroupware.org/bugzilla/show_bug.cgi?id=3D1922

> How can we contribute these forthcoming bugfixes back to 1.1.7 branch=20
> and/or the trunk? We'd rather not spend unnecessary time maintaining=20
> private bugfixes... is it possible to get svn commit rights or should we=20
> just create bugreports and attach our patches there?


--=-9sdoq97p/NEaeUAopuh6
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4-svn0 (GNU/Linux)

iD8DBQBHLx1PLRePpNle04MRAkiJAJ9T4zi+Yi99VZck6vN9PW+yJlPMdgCeMbfv
zK22X2K4+y+xqfJeKZWmVyk=
=kUik
-----END PGP SIGNATURE-----

--=-9sdoq97p/NEaeUAopuh6--