Why do you want to invent your own flows, if there are existing ones we can simply follow? If something does not look like a great solution for Fuel, let's discuss it and see how we could slightly modify the existing workflow to meet our needs in Fuel.
For Confirmation, Once you have reproduced the issue (or are 100% confident that this is indeed a valid bug), you should set: - Status: *Confirmed* - note in https://wiki.openstack.org/wiki/Bugs. Can we use this approach? Thank you, On Mon, Dec 16, 2013 at 6:18 PM, Nikolay Markov <[email protected]>wrote: > Greetings, dear fuelers! > > There is some kin of request to you regarding bugs you create and assign > on yourself. Please set them to "Confirmed" status for us to simplify > filtering out more important stuff. > > Thanks! > > -- > Best regards, > Nick Markov > > -- > Mailing list: https://launchpad.net/~fuel-dev > Post to : [email protected] > Unsubscribe : https://launchpad.net/~fuel-dev > More help : https://help.launchpad.net/ListHelp > > -- Mike Scherbakov #mihgen
-- Mailing list: https://launchpad.net/~fuel-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~fuel-dev More help : https://help.launchpad.net/ListHelp
