|
View:
New views
12 Messages
—
Rating Filter:
Alert me
|
|
|
status gtk-doc towards 1.9hi,
I reviewed, commented and applied several patches. yeti goes wild with submitting more and I've started a testsuite to help us improving without regressions. In order to get the best gtk-doc ever, please checkout from svn and test it, reply to the bugs, submit more reports and patches. cu Stefan _______________________________________________ gtk-doc-list mailing list gtk-doc-list@... http://mail.gnome.org/mailman/listinfo/gtk-doc-list |
|
|
Re: status gtk-doc towards 1.9On Wed, Jul 18, 2007 at 01:47:12PM +0200, Stefan Kost wrote:
> and I've started a testsuite to help us improving > without regressions. How to add a test case for getting a WARNING when one wants one? IMO this is equally important to not getting WARNINGS on valid code and documentation. Yeti -- http://gwyddion.net/ _______________________________________________ gtk-doc-list mailing list gtk-doc-list@... http://mail.gnome.org/mailman/listinfo/gtk-doc-list |
|
|
Re: status gtk-doc towards 1.9On Wed, 2007-07-18 at 13:47 +0200, Stefan Kost wrote:
> hi, > > I reviewed, commented and applied several patches. yeti goes wild with > submitting more and I've started a testsuite to help us improving > without regressions. In order to get the best gtk-doc ever, please > checkout from svn and test it, reply to the bugs, submit more reports > and patches. I'm afraid I don't really want to spend much time on gtk-doc these days. So you guys will have to take over maintainership, at least for a while. Though please test changes before committing them, at least with the GTK docs. (i.e. copy the xml directory, and see if any changes to gtk-doc affect the xml files badly). Damon _______________________________________________ gtk-doc-list mailing list gtk-doc-list@... http://mail.gnome.org/mailman/listinfo/gtk-doc-list |
|
|
Re: status gtk-doc towards 1.9Hi David,
David Nečas (Yeti) wrote: > On Wed, Jul 18, 2007 at 01:47:12PM +0200, Stefan Kost wrote: >> and I've started a testsuite to help us improving >> without regressions. > > How to add a test case for getting a WARNING when one wants > one? IMO this is equally important to not getting WARNINGS > on valid code and documentation. > The current test suite has two suites right now gobject - this should be an example that demonstrates all capabillities bugs - have examples that failed before to catch regressions Maybe we need another that has samples that should not causes warnings. This suite should run with a different driver-script (one that fails if there are no warnings). Stefan > > Yeti > > -- > http://gwyddion.net/ > _______________________________________________ > gtk-doc-list mailing list > gtk-doc-list@... > http://mail.gnome.org/mailman/listinfo/gtk-doc-list _______________________________________________ gtk-doc-list mailing list gtk-doc-list@... http://mail.gnome.org/mailman/listinfo/gtk-doc-list |
|
|
Re: status gtk-doc towards 1.9Hi Damon,
Damon Chaplin wrote: > On Wed, 2007-07-18 at 13:47 +0200, Stefan Kost wrote: >> hi, >> >> I reviewed, commented and applied several patches. yeti goes wild with >> submitting more and I've started a testsuite to help us improving >> without regressions. In order to get the best gtk-doc ever, please >> checkout from svn and test it, reply to the bugs, submit more reports >> and patches. > > I'm afraid I don't really want to spend much time on gtk-doc these days. > So you guys will have to take over maintainership, at least for a while. > still. Can you still do the releases? I could prepare the changelog etc. > > Though please test changes before committing them, at least with the GTK > docs. (i.e. copy the xml directory, and see if any changes to gtk-doc > affect the xml files badly). > Right now I build the docs for gstreamer and my own projects. I'll add gtk+ to that too. Problem with gtk+ is that without the index-generation patch applied it takes ages :/ > Damon > > Stefan _______________________________________________ gtk-doc-list mailing list gtk-doc-list@... http://mail.gnome.org/mailman/listinfo/gtk-doc-list |
|
|
Re: status gtk-doc towards 1.9On Sun, Jul 22, 2007 at 12:42:37PM +0100, Damon Chaplin wrote:
> > I'm afraid I don't really want to spend much time on gtk-doc these days. > So you guys will have to take over maintainership, at least for a while. Well, I can work on fixing bugs and implementing features -- I already do this -- but someone has to supply the vision. The goals and means are still puzzling me. Yeti -- http://gwyddion.net/ _______________________________________________ gtk-doc-list mailing list gtk-doc-list@... http://mail.gnome.org/mailman/listinfo/gtk-doc-list |
|
|
Re: status gtk-doc towards 1.9On Sun, Jul 22, 2007 at 09:58:49PM +0300, Stefan Kost wrote:
> > > The current test suite has two suites right now > gobject - this should be an example that demonstrates all capabillities > bugs - have examples that failed before to catch regressions > > Maybe we need another that has samples that should not causes warnings. s/should not/should/ ? > This > suite should run with a different driver-script (one that fails if there are no > warnings). Hm, wouldn't it be better to include the files and warnings generated by a known good gtk-doc run (manually checked) in the suite and diff the actual results? Yeti -- http://gwyddion.net/ _______________________________________________ gtk-doc-list mailing list gtk-doc-list@... http://mail.gnome.org/mailman/listinfo/gtk-doc-list |
|
|
|
|
|
Re: status gtk-doc towards 1.9Hi,
Quoting "David Ne?as (Yeti)" <yeti@...>: > On Sun, Jul 22, 2007 at 12:42:37PM +0100, Damon Chaplin wrote: >> >> I'm afraid I don't really want to spend much time on gtk-doc these days. >> So you guys will have to take over maintainership, at least for a while. > > Well, I can work on fixing bugs and implementing features -- > I already do this -- but someone has to supply the vision. > The goals and means are still puzzling me. > For the vision have a look at http://live.gnome.org/DocumentationProject/GtkDocFuture Before we start with more new stuff, I'd like to do this next: * refactor rexexps that are used in several places to gtkdoc-common * have a function that prints the warnings and refactor code to use it. as step two the function should get parsing context, so that it could print the arnings gcc-style (file:line: undefined argument blabla). > > Yeti > > -- > http://gwyddion.net/ Stefan _______________________________________________ gtk-doc-list mailing list gtk-doc-list@... http://mail.gnome.org/mailman/listinfo/gtk-doc-list |
|
|
Re: status gtk-doc towards 1.9On Sun, 2007-07-22 at 22:05 +0300, Stefan Kost wrote:
> Damon Chaplin wrote: > > I'm afraid I don't really want to spend much time on gtk-doc these days. > > So you guys will have to take over maintainership, at least for a while. > > > Fine with me. Of course it would be good if you could look over the changes > still. Can you still do the releases? I could prepare the changelog etc. I don't really want to do anything on gtk-doc for a while, I'm afraid. Releases are fairly easy to do, just make dist, scp to master.gnome.org and use the install-module script on there. The web pages are in svn, in gtk-web/gtk-doc. > > Though please test changes before committing them, at least with the GTK > > docs. (i.e. copy the xml directory, and see if any changes to gtk-doc > > affect the xml files badly). > > > Right now I build the docs for gstreamer and my own projects. I'll add gtk+ to > that too. Problem with gtk+ is that without the index-generation patch applied > it takes ages :/ You don't need to build the html to test every change. Just the xml should be fine. Damon _______________________________________________ gtk-doc-list mailing list gtk-doc-list@... http://mail.gnome.org/mailman/listinfo/gtk-doc-list |
|
|
|
|
|
Re: status gtk-doc towards 1.9hi,
I found http://live.gnome.org/MaintainersCorner/Releasing but I cannout loginto master.gnome.org - any idea? Stefan Damon Chaplin wrote: > On Sun, 2007-07-22 at 22:05 +0300, Stefan Kost wrote: >> Damon Chaplin wrote: >>> I'm afraid I don't really want to spend much time on gtk-doc these days. >>> So you guys will have to take over maintainership, at least for a while. >>> >> Fine with me. Of course it would be good if you could look over the changes >> still. Can you still do the releases? I could prepare the changelog etc. > > I don't really want to do anything on gtk-doc for a while, I'm afraid. > > Releases are fairly easy to do, just make dist, scp to master.gnome.org > and use the install-module script on there. > > The web pages are in svn, in gtk-web/gtk-doc. > > >>> Though please test changes before committing them, at least with the GTK >>> docs. (i.e. copy the xml directory, and see if any changes to gtk-doc >>> affect the xml files badly). >>> >> Right now I build the docs for gstreamer and my own projects. I'll add gtk+ to >> that too. Problem with gtk+ is that without the index-generation patch applied >> it takes ages :/ > > You don't need to build the html to test every change. Just the xml > should be fine. > > Damon > > _______________________________________________ gtk-doc-list mailing list gtk-doc-list@... http://mail.gnome.org/mailman/listinfo/gtk-doc-list |
| Free embeddable forum powered by Nabble | Forum Help |