[RESENT] tarballs, revision control

Am Donnerstag, den 05.01.2006, 16:48 +0100 schrieb Christian Neumair:
> I wonder whether there is any policy on how/when pages on
> developer.gnome.org should be updated, considering that there were some
> bug reports (inter alia [1,2]) on the structure of particular documents.
> The guides are partially available in multiple formats (gzipped HTML,
> postscript), but not all of them.
> Shouldn't we agree on one (hopefully iterative) method of writing
> documents and get a build-system running automatically putting releases
> in various formats for us? gtk-doc seems to be quite powerful, for
> instance.
> I also think we should either finally ditch the old 1.0 API docs, or
> write a huge "OUTDATED" warning header above them, to not confuse
> developers with bitrotten API descriptions. Google often offers matches
> in both the 2.0 and the 1.0 docs, and its not obvious that the outdated
> ones shouldn't be used.
> [1] http://bugzilla.gnome.org/show_bug.cgi?id=108030
> [2] http://bugzilla.gnome.org/show_bug.cgi?id=108044
> _______________________________________________
> gnome-doc-list mailing list
> gnome-doc-list gnome org
> http://mail.gnome.org/mailman/listinfo/gnome-doc-list
Christian Neumair <chris gnome-de org>

Attachment: signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]