Thread: [Ripperx-devel] where and when to record changes

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

Hi,

What is the policy on recording changes to the code?
So far I've been just leaving a SVN log message, but
should I also put them in a file?

regards

Paul

Hi Paul,

I think SVN commit log messages are fine, and then we can use them to remind 
us to update CHANGES files.  Or if you'd rather, feel free to drop changes 
into the CHANGES file as you go - whichever you think it is easier.

I suppose now that the project is really making use of SVN, the CHANGES file 
doesn't need to include dates, etc.  I propose we use a format like this for 
CHANGES going forward:

<release version x>:

* change n
* change n-1
...
* change 1

<release version x-1>:
...

Let me know if that works for you.

By the way, I created a tag to correspond to the 2.7.1 tarball release. 
Also, we need to tweak "make dist" to include the new .po files.  I just 
noticed it didn't pick up es.po or it.po.

Thanks,
Tony

Paul wrote:
> Hi,
> 
> What is the policy on recording changes to the code?
> So far I've been just leaving a SVN log message, but
> should I also put them in a file?
> 
> regards
> 
> Paul

On Tue, 12 Feb 2008 07:46:49 -0800
tony mancill <tma...@us...> wrote: 

> By the way, I created a tag to correspond to the 2.7.1 tarball release. 
> Also, we need to tweak "make dist" to include the new .po files.  I just 
> noticed it didn't pick up es.po or it.po.

That is probably, (almost certainly), because normally auto-generated files
are in SVN.

best regards

Paul

Paul wrote:
> On Tue, 12 Feb 2008 07:46:49 -0800
> tony mancill <tma...@us...> wrote: 
> 
>> By the way, I created a tag to correspond to the 2.7.1 tarball release. 
>> Also, we need to tweak "make dist" to include the new .po files.  I just 
>> noticed it didn't pick up es.po or it.po.
> 
> That is probably, (almost certainly), because normally auto-generated files
> are in SVN.

Hmmm... I took a look at the auto-generated Makefile and noticed that we 
didn't have a LINGUAS file.  After creating that, the "make dist" tarball 
included the .po files.

As for the auto-generated files, I'll start pulling them out for the 2.7.2 
release.

Tony

On Tue, 12 Feb 2008 10:39:07 -0800
tony mancill <to...@ma...> wrote: 

> Hmmm... I took a look at the auto-generated Makefile and noticed that we 
> didn't have a LINGUAS file.  After creating that, the "make dist" tarball 
> included the .po files.

It's not needed as we have ALL_LINGUAS in configure.ac.

Here, before your related changes, if i do './autogen.sh' and then 'make
dist', the Italian and Spanish translation are created and included in the
tarball.

best regards

Paul

Thread: [Ripperx-devel] where and when to record changes

ripperx-devel