Comment # 9
on bug 8315
from Anders Broman
(In reply to comment #6)
> (In reply to comment #4)
> > The patch was not generated by diffing with trunk. I took some nice ideas
> > and put it together to make 1.8 branch usable with gtk3.
>
> Also a small, tangential note - patches are rarely accepted directly against
> a stable branch. Only in the case where the issue has already been fixed in
> trunk by a method that is unsuitable for backport (i.e. something causing
> API/ABI change, or a significant internal refactor) are commits to stable
> branches not just cherry-picks from trunk.
>
> Bill, Anders, should this be codified on the wiki somewhere?
It's mentioned here http://wiki.wireshark.org/Development/ReleasePolicy
The release life cycle
During the lifetime of this Stable release inevitably problems are found and
bug fixes presented. These fixes are developed and tested in the Development
trunk and then scheduled for back-porting to the Stable branch. When enough bug
fixes are collected or the severity of the bugs warrant it and at the
discretion of Gerald, a new Maintenance release on the Stable release branch is
prepared. This Maintenance release has to adhere to the same policy of
consistent release contents, so does not contain new or changed features, but
only repairs of detected flaws. The only other changes allowed are updates of
volatile data files, like the manufacturer database, enterprise numbers, etc.
You are receiving this mail because:
- You are watching all bug changes.
