[Engine-devel] bug-url requirement for stable branch backports

[R P Herrold]

On Thu, 30 Jan 2014, Tal Nisan wrote:

> I think it will help stabilizing the new features in a short circle, sometimes
> there are small "fine tuning" fixes that don't have bugs opened for them and
> the flow is easier if you can just backport them without opening a bug.
> 
> On 01/30/2014 04:42 PM, Itamar Heim wrote:
> > I'm inclined to drop the "bug-url is required" for engine stable branch 3.4,
> 
> until we GA 3.4, as a lot of the patches are for pre-GA features.

I took Alon's comment as a -1, and do not understand the flow 
difficulty

Cloning a bug is a click and a bit of web trimming.  Adding it 
as a dependency on its parent is typing a bug number in the 
proper field.  It is very hard, unless sone follows both 
mailing lists, and commit mailing lists, to figure out some 
changes and if this is a backport (and not: "stabilizing the 
new features" as Tal mentions)

The thrashing in stabilization, and very fast gerrit approvals 
on the cpopen patch (it happened in hours, months ago) show 
the need to be explaining to a Bugzilla, what is happening.  
As near as I can tell the package succession is still not 
'right' for upgrades [It seems to need a manual exclude in a 
yum repo config in one place, OR a manual Provides, OR an 
epoched EVR (!! NOT RECOMMENDED !!)]

-1

-- Russ herrold