On 15/12, Ryan Rossiter wrote:
> Thanks for the review Michal! As for the bp/bug report, there’s four options:
>
> 1. Tack the work on as part of bp cinder-objects
> 2. Make a new blueprint (bp cinder—object-fields)
I think #2 would be the best option, as this is not part of the effort
to move
Sean,
Just an FYI that I have created a work item for my team to start working
this. So, watch for patches from Slade, Kendall, Ryan, Jacob and I to
get this implemented.
Thanks,
Jay
On 12/15/2015 10:31 AM, Sean McGinnis wrote:
On Tue, Dec 15, 2015 at 04:46:02PM +0100, Micha?? Dulko
On Tue, Dec 15, 2015 at 04:46:02PM +0100, Micha?? Dulko wrote:
> On 12/15/2015 04:08 PM, Ryan Rossiter wrote:
> > Thanks for the review Michal! As for the bp/bug report, there???s four
> > options:
> >
> > 1. Tack the work on as part of bp cinder-objects
> > 2. Make a new blueprint (bp
On 12/14/2015 03:59 PM, Ryan Rossiter wrote:
> Hi everyone,
>
> I have a change submitted that lays the groundwork for using custom enums and
> fields that are used by versioned objects [1]. These custom fields allow for
> verification on a set of valid values, which prevents the field from
On 12/15/2015 04:08 PM, Ryan Rossiter wrote:
> Thanks for the review Michal! As for the bp/bug report, there’s four options:
>
> 1. Tack the work on as part of bp cinder-objects
> 2. Make a new blueprint (bp cinder—object-fields)
> 3. Open a bug to handle all changes for enums/fields
> 4. Open a
Thanks for the review Michal! As for the bp/bug report, there’s four options:
1. Tack the work on as part of bp cinder-objects
2. Make a new blueprint (bp cinder—object-fields)
3. Open a bug to handle all changes for enums/fields
4. Open a bug for each changed enum/field
Personally, I’m partial
Hi everyone,
I have a change submitted that lays the groundwork for using custom enums and
fields that are used by versioned objects [1]. These custom fields allow for
verification on a set of valid values, which prevents the field from being
mistakenly set to something invalid. These custom
