[dev] [cvs] commit: dimp/docs CHANGES

[Jan Schneider]

Zitat von Chuck Hagenbuch <chuck at horde.org>:

> Quoting Jan Schneider <jan at horde.org>:
>
>>> This seems to have nuked all changelog entries made since the release
>>> of RC1.  See, e.g., horde, imp, dimp, mnemo, and turba.
>>
>> Yes, that was on purpose. It made sense as long as we had cut releases
>> from HEAD because I didn't want to have changelogs for, say horde
>> 3.1.5-cvs in the 3.2-rc1 release. Though, now that we are going to
>> make releases from the branches again, it's debatable.
>>
>> It still makes sense to only track changes for a version in the branch
>> that this version will be created from, and only copy changelogs for
>> released versions to other branches.
>> But OTOH, since bugs are always fixed in HEAD first, it makes sense to
>> get back to the old behavior and track all cvs versions in the HEAD
>> changelog. I'm fine with that if this is consensus.
>
> Shouldn't the changes that were under, for example, DIMP 1.0-cvs be
> moved to DIMP 2.0-cvs, since that's essentially where those changes
> went now? I'm not sure I follow your proposal, but we shouldn't just
> lose changelog entries...

We don't lose them. They are still in the FRAMEWORK_3 branch, and  
that's where the changes done since DIMP 1.0-RC1 have been done. There  
are no changes for 2.0-cvs yet.
We could either track 1.0-cvs changes in both branches, or only in the  
FW3 branch, and copy them to 2.0-cvs each time we have a release from  
the FW3 branch.

Jan.

-- 
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/