Open Stack

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hi all,

let me give you some examples of patches that I think do not *require*
any bug or blueprint (though some of them still have an associated bug):

https://review.openstack.org/#/c/90781/ (minor pythonic refactoring)
https://review.openstack.org/#/c/91044/ (oslo-incubator sync)
https://review.openstack.org/#/c/95450/ (fixed a docstring)
https://review.openstack.org/#/c/82756/ (minor unit tests enhancement)

/Ihar

On 23/05/14 19:23, Nachi Ueno wrote:
> Hi folks
> 
> I believed we should link bug or bp for any commit except
> automated commit by infra. However, I found also there is no
> written policy for this. so may be, I'm wrong for here.
> 
> The reason, we need bug or bp linked , is
> 
> (1) Triage for core reviewing (2) Avoid duplication of works (3)
> Release management
> 
> IMO, generally, the answer is yes.
> 
> However, how about small 5-6 nit change? so such patch will be
> exception or not?
> 
> I wanna ask community opinion, and I'll update gerrit workflow page
> based on this discussion.
> 
> Best Nachi
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBCgAGBQJTg4/ZAAoJEC5aWaUY1u576EYH/1Rt7zQRExaeB1ukL9eS9fx9
hm1W58s9jwC7NwRE22lpwtow/YNcDyYVSDTyLbvcbp4K8inv3I6No1KL5ySaA1hx
8ge1txGEtp5cHJAU26SIPr+hZAZRiRmoI5mLAMPVPfvt9jXMgTxBFwZQnfP0qbsY
czMtreSggExYT7jeC1a0MmeEMYUhAPR/hm8uEH22rGS9zpTMiDGG9PmfhJjEJ+y/
O7rqz+GuP8SdI736ttHmWWrTCXeONnkRWsnxR8POcPAuIWNrEQUOT7FnYKCNktyi
0kb+4tNEkcWxreHOgZkmzJgU20cD2e7CkwZuwTwulPuxe0J/rJZdfvg93B66MBg=
=QMpK
-----END PGP SIGNATURE-----