Hi Rob,
That is slightly different: from logical point of view that are
different schemas indeed, however they all map to the same DB schema,
so we do not have any issues with upgrades. There are some limitations
on the schema modifications as well, and being able to work with
multiple versions of
On 17 February 2015 at 03:31, Alexander Tivelkov wrote:
> Hi Client,
>
> Thanks for your input.
>
> We actually support the scenarios you speak about, yet in a slightly
> different way. The authors of the Artifact Type (the plugin
> developers) may define their own custom field (or set of fields)
Hi Client,
Thanks for your input.
We actually support the scenarios you speak about, yet in a slightly
different way. The authors of the Artifact Type (the plugin
developers) may define their own custom field (or set of fields) to
store their "sequence" information or any other type-specific
ver
Donald,
Thanks for your comments, really useful!
I think I need to clarify a bit: I am not speaking about the actual
semantic: placing the meaning into the actual values is still up to
the end-users (or the developers of Artifact Types, if they build some
custom logic which processes version info
Hi Ian,
On Tue, Feb 10, 2015 at 11:17 PM, Ian Cordasco
wrote:
> I think the fundamental disconnect is that not every column in a database
> needs offer sorting to the user. Imposing that restriction here causes a
> cascade of further restrictions that will fundamentally cause this to be
> unusabl
Excerpts from Alexander Tivelkov's message of 2015-02-10 07:28:55 -0800:
> Hi folks,
>
> One of the key features that we are adding to Glance with the
> introduction of Artifacts is the ability to have multiple versions of
> the same object in the repository: this gives us the possibility to
> que
> On Feb 10, 2015, at 3:17 PM, Ian Cordasco wrote:
>
>>
>> And of course, the chosen solution should be mappable to database, so
>> we may do sorting and filtering on the DB-side.
>> So, having it as a simple string and letting the user to decide what
>> it means is not an option.
>
> Except f
On 2/10/15, 12:01, "Alexander Tivelkov" wrote:
>Hi Ian,
>
>Automatic version generation is not the only and not the primary
>reason for the version concept. In fact, the implementation which is
>planned to land in this cycle does not contain this feature at all:
>currently we also leave the versi
On 2/10/15, 13:55, "Jay Pipes" wrote:
>On 02/10/2015 12:15 PM, Ian Cordasco wrote:
>> So Semantic Versioning, as I’ve already mentioned in the past, isn’t
>> really a de facto standard in any language community but it is a
>>language
>> agnostic proposal. That said, just because it’s language agn
I agree with Alexander on this. We should certainly learn what we can from
existing software. That said, the Solum team really wants this feature in
Glance so we can leverage that instead of having our own repository for Heat
templates we generate when building apps. We want to keep our requirem
On 02/10/2015 12:15 PM, Ian Cordasco wrote:
So Semantic Versioning, as I’ve already mentioned in the past, isn’t
really a de facto standard in any language community but it is a language
agnostic proposal. That said, just because it’s language agnostic does not
mean it won’t conflict with other l
Hi Ian,
Automatic version generation is not the only and not the primary
reason for the version concept. In fact, the implementation which is
planned to land in this cycle does not contain this feature at all:
currently we also leave the version assignment up to uploader (version
is a regular immu
On 2/10/15, 10:35, "Alexander Tivelkov" wrote:
>Thanks Monty!
>
>Yup, probably I've missed that. I was looking at pbr and its version
>implementation, but didn't realize that this is actually a fusion of
>semver and pep440.
>
>So, we have this as an extra alternative to choose from.
>
>It would
Thanks Monty!
Yup, probably I've missed that. I was looking at pbr and its version
implementation, but didn't realize that this is actually a fusion of
semver and pep440.
So, we have this as an extra alternative to choose from.
It would be an obvious choice if we were just looking for some commo
On 02/10/2015 10:28 AM, Alexander Tivelkov wrote:
> Hi folks,
>
> One of the key features that we are adding to Glance with the
> introduction of Artifacts is the ability to have multiple versions of
> the same object in the repository: this gives us the possibility to
> query for the latest versi
Hi folks,
One of the key features that we are adding to Glance with the
introduction of Artifacts is the ability to have multiple versions of
the same object in the repository: this gives us the possibility to
query for the latest version of something, keep track on the changes
history, and build
16 matches
Mail list logo
