[dev] Bugfixing on the new release?

Jan Schneider jan at horde.org
Wed Jan 5 06:57:06 PST 2005


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

> Quoting Jan Schneider <jan at horde.org>:
>
>> Zitat von Stuart K Bingë <omicron-list at mighty.co.za>:
>>
>>> I'm going to be doing some bugfixing on the Kolab code within the various
>>> Horde applications in the coming days, and I'd like to find out 
>>> what process
>>> I need to follow in order for the changes to make it into a later bugfix
>>> release of Horde/IMP/Kronolith, etc. Should I still just commit 
>>> everything to head, or is there another branch I should work on 
>>> instead?
>>
>> http://lists.horde.org/archives/dev/Week-of-Mon-20041227/016895.html
>
> ... the 2 second version of which is: commit to HEAD, merge to FRAMEWORK_3.

... and don't break BC.

Jan.

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


More information about the dev mailing list