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

[Adam Tauno Williams]

--=-FS6zxWN373HhMsYoV9rZ
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).
> 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...=20

Of course.

> is it possible to get svn commit rights or should we=20
> just create bugreports and attach our patches there?

Everything should go through bugzilla;  if you upload patches I'll get
an email (usually).  I try to do my best in verifying and committing
patches.  If you submit a patch and don't hear anything for awhile feel
free to rattle my chain @ awilliam@whitemiceconsulting.com

Also there is the OGo-Devel list for development / hacking related
questions.

--=-FS6zxWN373HhMsYoV9rZ
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)

iD8DBQBHKezqLRePpNle04MRAgXqAJ9vIGGmWmu2NmSNNa/N6TjKJMXAxwCeKs3A
IFce/HKD9U4qXTX/1m2K5sk=
=v42o
-----END PGP SIGNATURE-----

--=-FS6zxWN373HhMsYoV9rZ--