Am Freitag, 11. Dezember 2009 schrieb Geert Janssens:
BTW if you write a svn commit message and quote a bugzilla bug number, I
recommend writing bug #1234, i.e. with the hash sign in front of the
number. Our trac website is set up to turn those numbers (those with
hash) into hyperlinks
Dear Geert,
Am Donnerstag, 10. Dezember 2009 schrieb Geert Janssens:
We also have such a script - the makefile rules for the ChangeLog file
in the top-level directory do exactly this: It downloads the svn log
data from the hard-coded revision and formats it into some text file
by the use
On Friday 11 December 2009, Christian Stimming wrote:
Dear Geert,
Am Donnerstag, 10. Dezember 2009 schrieb Geert Janssens:
We also have such a script - the makefile rules for the ChangeLog file
in the top-level directory do exactly this: It downloads the svn log
data from the
Zitat von Geert Janssens janssens-ge...@telenet.be:
A new template would be great. Even better would be working out a good
process for updating the changed item section. For this, I looked at
the revision log from http://svn.gnucash.org/trac/log/gnucash/trunk,
but it cuts off the
On Thursday 10 December 2009, Christian Stimming wrote:
Zitat von Geert Janssens janssens-ge...@telenet.be:
A new template would be great. Even better would be working out a
good process for updating the changed item section. For this, I
looked at the revision log from
Phil,
I see you have pushed a new news item. You already found there is now a
warning block in it. I had made some additional changes to the news pages,
like adding links to the proper download locations and some general tidying to
the titles.
I see now that I didn't communicate these changes
Also, when you update a release (stable or development), the new version
number should be inserted in externals/global_params.php.
This ensures that the front page and downloads page continue to list the
latest versions. For an unstable release, only the downloads page is affected
by this, for
From: Geert Janssens janssens-ge...@telenet.be
To: gnucash-devel@gnucash.org
Sent: Wed, December 9, 2009 1:35:42 PM
Subject: Re: r18476 - htdocs/trunk/news - Fix unstable version warning
Phil,
I see you have pushed a new news item. You already found there is now a
warning block in it. I had made
On Wednesday 9 December 2009, Phil Longstaff wrote:
I didn't 'svn update' until after I'd copied 2.3.7 to 2.3.8 as a template,
so I didn't know about the new stuff. It wasn't until I had first
committed the 2.3.8 news item and then went to see how it looked on
gnucash.org that I noticed some
On Wednesday 9 December 2009, Phil Longstaff wrote:
On Wed, 2009-12-09 at 23:34 +0100, Geert Janssens wrote:
On Wednesday 9 December 2009, Phil Longstaff wrote:
I didn't 'svn update' until after I'd copied 2.3.7 to 2.3.8 as a
template, so I didn't know about the new stuff. It wasn't
On Wed, 2009-12-09 at 23:34 +0100, Geert Janssens wrote:
On Wednesday 9 December 2009, Phil Longstaff wrote:
I didn't 'svn update' until after I'd copied 2.3.7 to 2.3.8 as a template,
so I didn't know about the new stuff. It wasn't until I had first
committed the 2.3.8 news item and then
11 matches
Mail list logo