You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@olingo.apache.org by "Bolz, Michael" <mi...@sap.com> on 2015/05/22 06:44:40 UTC
[VOTE] RC01 - Sample projects for tutorials (as ZIP file)
Hello,
I updated and extended the tutorial for simpel OData Read/Read Extended/Write Services with Olingo V4 (see section Tutorials on staging page: http://olingo.staging.apache.org/doc/odata4/ <http://olingo.staging.apache.org/doc/odata4/>).
For this I ill also uploaded the final projects in form of ZIP files.
According to the Apache Release process I understood that this ZIP file must contain the DEPENDENCIES, LICENCE and NOTES file.
Additional it must be signed.
I have signed (which was done through the key 15AB5637 in: http://keyserver.kjsl.org:11371/pks/lookup?search=0x15AB5637&op=vindex <http://keyserver.kjsl.org:11371/pks/lookup?search=0x15AB5637&op=vindex>)
and uploaded it to: http://people.apache.org/~mibo/olingo4/DemoServiceTutorials/ <http://people.apache.org/~mibo/olingo4/DemoServiceTutorials/> as RC01 versions.
If all is ok and the vote passes I will use them for official Apache Olingo Homepage (http://olingo.apache.org <http://olingo.apache.org/>).
The vote will be open for at least 72 hours (it will be closed on Monday 25/05/2015 on 8am CET) and passes if no vote is (-1).
[ ] +1 Use this sample project for tutorial
[ ] -1 Do not use this sample project because…
Best regards,
Michael
RE: [VOTE] RC01 - Sample projects for tutorials (as ZIP file)
Posted by "Kobler-Morris, Sven" <sv...@sap.com>.
Hi,
+1 from my side.
Thank and kind regards,
Sven
From: Bolz, Michael [mailto:michael.bolz@sap.com]
Sent: Freitag, 22. Mai 2015 06:45
To: dev@olingo.apache.org
Subject: [VOTE] RC01 - Sample projects for tutorials (as ZIP file)
* PGP - S/MIME Signed by an unverified key: 22.05.2015 at 06:27:53
Hello,
I updated and extended the tutorial for simpel OData Read/Read Extended/Write Services with Olingo V4 (see section Tutorials on staging page: http://olingo.staging.apache.org/doc/odata4/).
For this I ill also uploaded the final projects in form of ZIP files.
According to the Apache Release process I understood that this ZIP file must contain the DEPENDENCIES, LICENCE and NOTES file.
Additional it must be signed.
I have signed (which was done through the key 15AB5637 in: http://keyserver.kjsl.org:11371/pks/lookup?search=0x15AB5637&op=vindex)
and uploaded it to: http://people.apache.org/~mibo/olingo4/DemoServiceTutorials/ as RC01 versions.
If all is ok and the vote passes I will use them for official Apache Olingo Homepage (http://olingo.apache.org).
The vote will be open for at least 72 hours (it will be closed on Monday 25/05/2015 on 8am CET) and passes if no vote is (-1).
[ ] +1 Use this sample project for tutorial
[ ] -1 Do not use this sample project because…
Best regards,
Michael
* D046871 <mi...@sap.com>>
* Issuer: SAP-AG - Unverified
RE: [VOTE] RC01 - Sample projects for tutorials (as ZIP file)
Posted by "Amend, Christian" <ch...@sap.com>.
+1
From: Bolz, Michael [mailto:michael.bolz@sap.com]
Sent: Freitag, 22. Mai 2015 06:45
To: dev@olingo.apache.org
Subject: [VOTE] RC01 - Sample projects for tutorials (as ZIP file)
* PGP - S/MIME Signed by an unverified key: 22.05.2015 at 06:27:53
Hello,
I updated and extended the tutorial for simpel OData Read/Read Extended/Write Services with Olingo V4 (see section Tutorials on staging page: http://olingo.staging.apache.org/doc/odata4/).
For this I ill also uploaded the final projects in form of ZIP files.
According to the Apache Release process I understood that this ZIP file must contain the DEPENDENCIES, LICENCE and NOTES file.
Additional it must be signed.
I have signed (which was done through the key 15AB5637 in: http://keyserver.kjsl.org:11371/pks/lookup?search=0x15AB5637&op=vindex)
and uploaded it to: http://people.apache.org/~mibo/olingo4/DemoServiceTutorials/ as RC01 versions.
If all is ok and the vote passes I will use them for official Apache Olingo Homepage (http://olingo.apache.org).
The vote will be open for at least 72 hours (it will be closed on Monday 25/05/2015 on 8am CET) and passes if no vote is (-1).
[ ] +1 Use this sample project for tutorial
[ ] -1 Do not use this sample project because…
Best regards,
Michael
* D046871 <mi...@sap.com>>
* Issuer: SAP-AG - Unverified
Re: [VOTE] RC01 - Sample projects for tutorials (as ZIP file)
Posted by Aki Yoshida <el...@gmail.com>.
I have a related question to this, namely the status of the current
olingo-odata4/samples.
The current olingo-odata4/samples/client has not been updated for V4
and it is currently disabled.
For OLINGO-632, I needed a client sample to work against the server
sample in samples/server to test the OSGi setup for V4, so I updated
that client sample to use the V4 API to test the operations that the
server sample currently supports.
I don't know if I can create a jira ticket to request this updated
client (a normal standalone client) to be added to the repo so that I
can use that client to create its OSGi version. Let me know what I
should do.
Regards, aki
2015-05-26 8:15 GMT+02:00 Bolz, Michael <mi...@sap.com>:
> Hi Francesco,
>
> On 25 May 2015, at 08:50, Francesco Chicchiriccò <il...@apache.org>
> wrote:
>
> On 25/05/2015 08:41, Bolz, Michael wrote:
>
> Hi Francesco,
>
> IMHO this sample project sources are nothing wich is really under
> development and hence I thought this should not be put into the Olingo
> project git repo.
>
>
> Why you say this? What are you going to do when API will change in the
> future? Publish updated samples, no?
>
>
> You are right, the samples will be updated with updates of the API.
> However put all sample projects as separate maven (sub) modules into the
> Olingo git repo seems not the right solution for me.
>
>
> The quoted:
>
> "[...] when a release consists of anything beyond an archive (e.g., tarball
> or zip file) of a source control tag […]"
>
>
> …
>
>
> However I am open for suggestions on how to handle such sample projects for
> download as ZIP archive.
> Should it be put in some git repo (and if yes in which)? (which is IMHO not
> useful).
> Or should we do not handle it as a ASF release? (which is IMHO the wrong and
> not the ASF way).
> Any opinions and suggestions?
>
>
> I really don't know, it's the first time I see something similar, and I've
> just expressed my doubts.
> Regards.
>
>
> IMHO for Olingo as project it is good to have discussions about such things
> so that we as community can find together a good solution.
> And now we should try to find a solution for the sample ZIP files ;o)
>
> @Franceso: If I understand you correctly you suggest to put the samples into
> the Olingo git repo. Right?
>
> Best regards,
> Michael
>
>
>
> [1]: http://www.apache.org/dev/release.html#owned-controlled-hardware
> [2]: http://www.apache.org/dev/release.html#what-must-every-release-contain
>
>
> On 25 May 2015, at 08:04, Francesco Chicchiriccò <ilgrosso@apache.org
> <ma...@apache.org>> wrote:
>
> On 24/05/2015 09:10, Bolz, Michael wrote:
>
> Hi Francesco,
>
> For the tutorials I created the according projects which are not in the
> Olingo git repository.
> My intention was to provide the tutorials together with the according sample
> project as a single ZIP file to download from the homepage so that they can
> be easily extracted and started.
>
> Therefore I read the documentation for the Apache release process
> (http://www.apache.org/dev/release.html) and
> I came to the conclusion that for providing the sample projects as ZIP file
> it is necessary to do a official release of them.
> So I checked within the release management [1] what a release must contain
> [2] and how it must be approved [3].
>
> Based on this I prepared the sample project ZIP files and started the
> voting.
> However if something should / must be handled otherwise I’am open for help.
>
>
> What sounds quite strange to me is to release something which is not under
> this community's source repositories but somewhere else; to give you an
> example, in the same link you refer above, it is reported:
>
> "[...] when a release consists of anything beyond an archive (e.g., tarball
> or zip file) of a source control tag [...]"
>
> implying to me that this is the bare minimum.
>
> I could not find anyway a place where it is clearly stated that "releases
> are something you tag from one of community source repositories", so to me
> the doubt remains.
>
> Regards.
>
> [1]: http://www.apache.org/dev/release.html#management
> [2]: http://www.apache.org/dev/release.html#what-must-every-release-contain
> [3]: http://www.apache.org/dev/release.html#approving-a-release
>
>
> --
> Francesco Chicchiriccò
>
> Tirasa - Open Source Excellence
> http://www.tirasa.net/
>
> Involved at The Apache Software Foundation:
> member, Syncope PMC chair, Cocoon PMC, Olingo PMC
> http://people.apache.org/~ilgrosso/
>
>
Re: [VOTE] RC01 - Sample projects for tutorials (as ZIP file)
Posted by Francesco Chicchiriccò <il...@apache.org>.
On 27/05/2015 08:45, Bolz, Michael wrote:
> Hi Francesco,
>
> Would it be ok for you if the current sample / tutorial ZIP files will
> be release without being in the projects git repo
> and afterwards I start a discussion on the mailing list about where
> future samples should be put (e.g. git) and how to release them?
Hi Michael,
such approach looks like a good way to move forward.
Regards.
>> On 26 May 2015, at 08:15, Bolz, Michael <michael.bolz@sap.com
>> <ma...@sap.com>> wrote:
>>
>> Hi Francesco,
>>
>>> On 25 May 2015, at 08:50, Francesco Chicchiriccò
>>> <ilgrosso@apache.org <ma...@apache.org>> wrote:
>>>
>>> On 25/05/2015 08:41, Bolz, Michael wrote:
>>>> Hi Francesco,
>>>>
>>>> IMHO this sample project sources are nothing wich is really under
>>>> development and hence I thought this should not be put into the
>>>> Olingo project git repo.
>>>
>>> Why you say this? What are you going to do when API will change in
>>> the future? Publish updated samples, no?
>>
>> You are right, the samples will be updated with updates of the API.
>> However put all sample projects as separate maven (sub) modules into
>> the Olingo git repo seems not the right solution for me.
>>
>>>
>>>> The quoted:
>>>>> "[...] when a release consists of anything beyond an archive
>>>>> (e.g., tarball or zip file) of a source control tag […]"
>>>>
>>>> …
>>
>>>> However I am open for suggestions on how to handle such sample
>>>> projects for download as ZIP archive.
>>>> Should it be put in some git repo (and if yes in which)? (which is
>>>> IMHO not useful).
>>>> Or should we do not handle it as a ASF release? (which is IMHO the
>>>> wrong and not the ASF way).
>>>> Any opinions and suggestions?
>>>
>>> I really don't know, it's the first time I see something similar,
>>> and I've just expressed my doubts.
>>> Regards.
>>
>> IMHO for Olingo as project it is good to have discussions about such
>> things so that we as community can find together a good solution.
>> And now we should try to find a solution for the sample ZIP files ;o)
>>
>> @Franceso: If I understand you correctly you suggest to put the
>> samples into the Olingo git repo. Right?
>>
>> Best regards,
>> Michael
>>
>>
>>>
>>>> [1]:http://www.apache.org/dev/release.html#owned-controlled-hardware
>>>> [2]:http://www.apache.org/dev/release.html#what-must-every-release-contain
>>>>
>>>>
>>>>> On 25 May 2015, at 08:04, Francesco Chicchiriccò
>>>>> <ilgrosso@apache.org
>>>>> <ma...@apache.org>> wrote:
>>>>>
>>>>> On 24/05/2015 09:10, Bolz, Michael wrote:
>>>>>> Hi Francesco,
>>>>>>
>>>>>> For the tutorials I created the according projects which are not
>>>>>> in the Olingo git repository.
>>>>>> My intention was to provide the tutorials together with the
>>>>>> according sample project as a single ZIP file to download from
>>>>>> the homepage so that they can be easily extracted and started.
>>>>>>
>>>>>> Therefore I read the documentation for the Apache release process
>>>>>> (http://www.apache.org/dev/release.html) and
>>>>>> I came to the conclusion that for providing the sample projects
>>>>>> as ZIP file it is necessary to do a official release of them.
>>>>>> So I checked within the release management [1] what a release
>>>>>> must contain [2] and how it must be approved [3].
>>>>>>
>>>>>> Based on this I prepared the sample project ZIP files and started
>>>>>> the voting.
>>>>>> However if something should / must be handled otherwise I’am open
>>>>>> for help.
>>>>>
>>>>> What sounds quite strange to me is to release something which is
>>>>> not under this community's source repositories but somewhere else;
>>>>> to give you an example, in the same link you refer above, it is
>>>>> reported:
>>>>>
>>>>> "[...] when a release consists of anything beyond an archive
>>>>> (e.g., tarball or zip file) of a source control tag [...]"
>>>>>
>>>>> implying to me that this is the bare minimum.
>>>>>
>>>>> I could not find anyway a place where it is clearly stated that
>>>>> "releases are something you tag from one of community source
>>>>> repositories", so to me the doubt remains.
>>>>>
>>>>> Regards.
>>>>>
>>>>>> [1]: http://www.apache.org/dev/release.html#management
>>>>>> [2]:
>>>>>> http://www.apache.org/dev/release.html#what-must-every-release-contain
>>>>>> [3]: http://www.apache.org/dev/release.html#approving-a-release
--
Francesco Chicchiriccò
Tirasa - Open Source Excellence
http://www.tirasa.net/
Involved at The Apache Software Foundation:
member, Syncope PMC chair, Cocoon PMC, Olingo PMC
http://people.apache.org/~ilgrosso/
Re: [VOTE] RC01 - Sample projects for tutorials (as ZIP file)
Posted by "Bolz, Michael" <mi...@sap.com>.
Hi Francesco,
Would it be ok for you if the current sample / tutorial ZIP files will be release without being in the projects git repo
and afterwards I start a discussion on the mailing list about where future samples should be put (e.g. git) and how to release them?
Best regards,
Michael
> On 26 May 2015, at 08:15, Bolz, Michael <mi...@sap.com> wrote:
>
> Hi Francesco,
>
>> On 25 May 2015, at 08:50, Francesco Chicchiriccò <ilgrosso@apache.org <ma...@apache.org>> wrote:
>>
>> On 25/05/2015 08:41, Bolz, Michael wrote:
>>> Hi Francesco,
>>>
>>> IMHO this sample project sources are nothing wich is really under development and hence I thought this should not be put into the Olingo project git repo.
>>
>> Why you say this? What are you going to do when API will change in the future? Publish updated samples, no?
>
> You are right, the samples will be updated with updates of the API.
> However put all sample projects as separate maven (sub) modules into the Olingo git repo seems not the right solution for me.
>
>>
>>> The quoted:
>>>> "[...] when a release consists of anything beyond an archive (e.g., tarball or zip file) of a source control tag […]"
>>>
>>> …
>
>>> However I am open for suggestions on how to handle such sample projects for download as ZIP archive.
>>> Should it be put in some git repo (and if yes in which)? (which is IMHO not useful).
>>> Or should we do not handle it as a ASF release? (which is IMHO the wrong and not the ASF way).
>>> Any opinions and suggestions?
>>
>> I really don't know, it's the first time I see something similar, and I've just expressed my doubts.
>> Regards.
>
> IMHO for Olingo as project it is good to have discussions about such things so that we as community can find together a good solution.
> And now we should try to find a solution for the sample ZIP files ;o)
>
> @Franceso: If I understand you correctly you suggest to put the samples into the Olingo git repo. Right?
>
> Best regards,
> Michael
>
>
>>
>>> [1]: http://www.apache.org/dev/release.html#owned-controlled-hardware <http://www.apache.org/dev/release.html#owned-controlled-hardware>
>>> [2]: http://www.apache.org/dev/release.html#what-must-every-release-contain <http://www.apache.org/dev/release.html#what-must-every-release-contain>
>>>
>>>
>>>> On 25 May 2015, at 08:04, Francesco Chicchiriccò <ilgrosso@apache.org <ma...@apache.org> <mailto:ilgrosso@apache.org <ma...@apache.org>>> wrote:
>>>>
>>>> On 24/05/2015 09:10, Bolz, Michael wrote:
>>>>> Hi Francesco,
>>>>>
>>>>> For the tutorials I created the according projects which are not in the Olingo git repository.
>>>>> My intention was to provide the tutorials together with the according sample project as a single ZIP file to download from the homepage so that they can be easily extracted and started.
>>>>>
>>>>> Therefore I read the documentation for the Apache release process (http://www.apache.org/dev/release.html <http://www.apache.org/dev/release.html>) and
>>>>> I came to the conclusion that for providing the sample projects as ZIP file it is necessary to do a official release of them.
>>>>> So I checked within the release management [1] what a release must contain [2] and how it must be approved [3].
>>>>>
>>>>> Based on this I prepared the sample project ZIP files and started the voting.
>>>>> However if something should / must be handled otherwise I’am open for help.
>>>>
>>>> What sounds quite strange to me is to release something which is not under this community's source repositories but somewhere else; to give you an example, in the same link you refer above, it is reported:
>>>>
>>>> "[...] when a release consists of anything beyond an archive (e.g., tarball or zip file) of a source control tag [...]"
>>>>
>>>> implying to me that this is the bare minimum.
>>>>
>>>> I could not find anyway a place where it is clearly stated that "releases are something you tag from one of community source repositories", so to me the doubt remains.
>>>>
>>>> Regards.
>>>>
>>>>> [1]: http://www.apache.org/dev/release.html#management <http://www.apache.org/dev/release.html#management>
>>>>> [2]: http://www.apache.org/dev/release.html#what-must-every-release-contain <http://www.apache.org/dev/release.html#what-must-every-release-contain>
>>>>> [3]: http://www.apache.org/dev/release.html#approving-a-release <http://www.apache.org/dev/release.html#approving-a-release>
>>
>> --
>> Francesco Chicchiriccò
>>
>> Tirasa - Open Source Excellence
>> http://www.tirasa.net/ <http://www.tirasa.net/>
>>
>> Involved at The Apache Software Foundation:
>> member, Syncope PMC chair, Cocoon PMC, Olingo PMC
>> http://people.apache.org/~ilgrosso/ <http://people.apache.org/~ilgrosso/>
Re: [VOTE] RC01 - Sample projects for tutorials (as ZIP file)
Posted by "Bolz, Michael" <mi...@sap.com>.
Hi Francesco,
> On 25 May 2015, at 08:50, Francesco Chicchiriccò <il...@apache.org> wrote:
>
> On 25/05/2015 08:41, Bolz, Michael wrote:
>> Hi Francesco,
>>
>> IMHO this sample project sources are nothing wich is really under development and hence I thought this should not be put into the Olingo project git repo.
>
> Why you say this? What are you going to do when API will change in the future? Publish updated samples, no?
You are right, the samples will be updated with updates of the API.
However put all sample projects as separate maven (sub) modules into the Olingo git repo seems not the right solution for me.
>
>> The quoted:
>>> "[...] when a release consists of anything beyond an archive (e.g., tarball or zip file) of a source control tag […]"
>>
>> …
>> However I am open for suggestions on how to handle such sample projects for download as ZIP archive.
>> Should it be put in some git repo (and if yes in which)? (which is IMHO not useful).
>> Or should we do not handle it as a ASF release? (which is IMHO the wrong and not the ASF way).
>> Any opinions and suggestions?
>
> I really don't know, it's the first time I see something similar, and I've just expressed my doubts.
> Regards.
IMHO for Olingo as project it is good to have discussions about such things so that we as community can find together a good solution.
And now we should try to find a solution for the sample ZIP files ;o)
@Franceso: If I understand you correctly you suggest to put the samples into the Olingo git repo. Right?
Best regards,
Michael
>
>> [1]: http://www.apache.org/dev/release.html#owned-controlled-hardware <http://www.apache.org/dev/release.html#owned-controlled-hardware>
>> [2]: http://www.apache.org/dev/release.html#what-must-every-release-contain <http://www.apache.org/dev/release.html#what-must-every-release-contain>
>>
>>
>>> On 25 May 2015, at 08:04, Francesco Chicchiriccò <ilgrosso@apache.org <ma...@apache.org> <mailto:ilgrosso@apache.org <ma...@apache.org>>> wrote:
>>>
>>> On 24/05/2015 09:10, Bolz, Michael wrote:
>>>> Hi Francesco,
>>>>
>>>> For the tutorials I created the according projects which are not in the Olingo git repository.
>>>> My intention was to provide the tutorials together with the according sample project as a single ZIP file to download from the homepage so that they can be easily extracted and started.
>>>>
>>>> Therefore I read the documentation for the Apache release process (http://www.apache.org/dev/release.html) and
>>>> I came to the conclusion that for providing the sample projects as ZIP file it is necessary to do a official release of them.
>>>> So I checked within the release management [1] what a release must contain [2] and how it must be approved [3].
>>>>
>>>> Based on this I prepared the sample project ZIP files and started the voting.
>>>> However if something should / must be handled otherwise I’am open for help.
>>>
>>> What sounds quite strange to me is to release something which is not under this community's source repositories but somewhere else; to give you an example, in the same link you refer above, it is reported:
>>>
>>> "[...] when a release consists of anything beyond an archive (e.g., tarball or zip file) of a source control tag [...]"
>>>
>>> implying to me that this is the bare minimum.
>>>
>>> I could not find anyway a place where it is clearly stated that "releases are something you tag from one of community source repositories", so to me the doubt remains.
>>>
>>> Regards.
>>>
>>>> [1]: http://www.apache.org/dev/release.html#management
>>>> [2]: http://www.apache.org/dev/release.html#what-must-every-release-contain
>>>> [3]: http://www.apache.org/dev/release.html#approving-a-release
>
> --
> Francesco Chicchiriccò
>
> Tirasa - Open Source Excellence
> http://www.tirasa.net/ <http://www.tirasa.net/>
>
> Involved at The Apache Software Foundation:
> member, Syncope PMC chair, Cocoon PMC, Olingo PMC
> http://people.apache.org/~ilgrosso/ <http://people.apache.org/~ilgrosso/>
Re: [VOTE] RC01 - Sample projects for tutorials (as ZIP file)
Posted by Francesco Chicchiriccò <il...@apache.org>.
On 25/05/2015 08:41, Bolz, Michael wrote:
> Hi Francesco,
>
> IMHO this sample project sources are nothing wich is really under
> development and hence I thought this should not be put into the Olingo
> project git repo.
Why you say this? What are you going to do when API will change in the
future? Publish updated samples, no?
> The quoted:
>> "[...] when a release consists of anything beyond an archive (e.g.,
>> tarball or zip file) of a source control tag […]"
>
> is from the section "MUST RELEASES BE BUILT ON HARDWARE OWNED
> AND CONTROLLED BY THE COMMITTER?”
> and "refers to the process used to produce a release artifact from a
> source control tag.”. [1]
> I think it is not for releases in general.
>
> The section "WHAT MUST EVERY ASF RELEASE CONTAIN?”
> implying to me that an "ASF release must contain a source package”
> and that an "ASF release must comply with ASF licensing policy”.
> Which is both fulfilled by the sample ZIP archive.
>
> However I am open for suggestions on how to handle such sample
> projects for download as ZIP archive.
> Should it be put in some git repo (and if yes in which)? (which is
> IMHO not useful).
> Or should we do not handle it as a ASF release? (which is IMHO the
> wrong and not the ASF way).
> Any opinions and suggestions?
I really don't know, it's the first time I see something similar, and
I've just expressed my doubts.
Regards.
> [1]: http://www.apache.org/dev/release.html#owned-controlled-hardware
> [2]:
> http://www.apache.org/dev/release.html#what-must-every-release-contain
>
>
>> On 25 May 2015, at 08:04, Francesco Chicchiriccò <ilgrosso@apache.org
>> <ma...@apache.org>> wrote:
>>
>> On 24/05/2015 09:10, Bolz, Michael wrote:
>>> Hi Francesco,
>>>
>>> For the tutorials I created the according projects which are not in
>>> the Olingo git repository.
>>> My intention was to provide the tutorials together with the
>>> according sample project as a single ZIP file to download from the
>>> homepage so that they can be easily extracted and started.
>>>
>>> Therefore I read the documentation for the Apache release process
>>> (http://www.apache.org/dev/release.html) and
>>> I came to the conclusion that for providing the sample projects as
>>> ZIP file it is necessary to do a official release of them.
>>> So I checked within the release management [1] what a release must
>>> contain [2] and how it must be approved [3].
>>>
>>> Based on this I prepared the sample project ZIP files and started
>>> the voting.
>>> However if something should / must be handled otherwise I’am open
>>> for help.
>>
>> What sounds quite strange to me is to release something which is not
>> under this community's source repositories but somewhere else; to
>> give you an example, in the same link you refer above, it is reported:
>>
>> "[...] when a release consists of anything beyond an archive (e.g.,
>> tarball or zip file) of a source control tag [...]"
>>
>> implying to me that this is the bare minimum.
>>
>> I could not find anyway a place where it is clearly stated that
>> "releases are something you tag from one of community source
>> repositories", so to me the doubt remains.
>>
>> Regards.
>>
>>> [1]: http://www.apache.org/dev/release.html#management
>>> [2]:
>>> http://www.apache.org/dev/release.html#what-must-every-release-contain
>>> [3]: http://www.apache.org/dev/release.html#approving-a-release
--
Francesco Chicchiriccò
Tirasa - Open Source Excellence
http://www.tirasa.net/
Involved at The Apache Software Foundation:
member, Syncope PMC chair, Cocoon PMC, Olingo PMC
http://people.apache.org/~ilgrosso/
Re: [VOTE] RC01 - Sample projects for tutorials (as ZIP file)
Posted by "Bolz, Michael" <mi...@sap.com>.
Hi Francesco,
IMHO this sample project sources are nothing wich is really under development and hence I thought this should not be put into the Olingo project git repo.
The quoted:
> "[...] when a release consists of anything beyond an archive (e.g., tarball or zip file) of a source control tag […]"
is from the section "MUST RELEASES BE BUILT ON HARDWARE OWNED AND CONTROLLED BY THE COMMITTER?”
and "refers to the process used to produce a release artifact from a source control tag.”. [1]
I think it is not for releases in general.
The section "WHAT MUST EVERY ASF RELEASE CONTAIN?”
implying to me that an "ASF release must contain a source package”
and that an "ASF release must comply with ASF licensing policy”.
Which is both fulfilled by the sample ZIP archive.
However I am open for suggestions on how to handle such sample projects for download as ZIP archive.
Should it be put in some git repo (and if yes in which)? (which is IMHO not useful).
Or should we do not handle it as a ASF release? (which is IMHO the wrong and not the ASF way).
Any opinions and suggestions?
Best regards,
Michael
[1]: http://www.apache.org/dev/release.html#owned-controlled-hardware <http://www.apache.org/dev/release.html#owned-controlled-hardware>
[2]: http://www.apache.org/dev/release.html#what-must-every-release-contain <http://www.apache.org/dev/release.html#what-must-every-release-contain>
> On 25 May 2015, at 08:04, Francesco Chicchiriccò <il...@apache.org> wrote:
>
> On 24/05/2015 09:10, Bolz, Michael wrote:
>> Hi Francesco,
>>
>> For the tutorials I created the according projects which are not in the Olingo git repository.
>> My intention was to provide the tutorials together with the according sample project as a single ZIP file to download from the homepage so that they can be easily extracted and started.
>>
>> Therefore I read the documentation for the Apache release process (http://www.apache.org/dev/release.html) and
>> I came to the conclusion that for providing the sample projects as ZIP file it is necessary to do a official release of them.
>> So I checked within the release management [1] what a release must contain [2] and how it must be approved [3].
>>
>> Based on this I prepared the sample project ZIP files and started the voting.
>> However if something should / must be handled otherwise I’am open for help.
>
> What sounds quite strange to me is to release something which is not under this community's source repositories but somewhere else; to give you an example, in the same link you refer above, it is reported:
>
> "[...] when a release consists of anything beyond an archive (e.g., tarball or zip file) of a source control tag [...]"
>
> implying to me that this is the bare minimum.
>
> I could not find anyway a place where it is clearly stated that "releases are something you tag from one of community source repositories", so to me the doubt remains.
>
> Regards.
>
>> [1]: http://www.apache.org/dev/release.html#management
>> [2]: http://www.apache.org/dev/release.html#what-must-every-release-contain
>> [3]: http://www.apache.org/dev/release.html#approving-a-release
>>
Re: [VOTE] RC01 - Sample projects for tutorials (as ZIP file)
Posted by Francesco Chicchiriccò <il...@apache.org>.
On 24/05/2015 09:10, Bolz, Michael wrote:
> Hi Francesco,
>
> For the tutorials I created the according projects which are not in
> the Olingo git repository.
> My intention was to provide the tutorials together with the according
> sample project as a single ZIP file to download from the homepage so
> that they can be easily extracted and started.
>
> Therefore I read the documentation for the Apache release process
> (http://www.apache.org/dev/release.html) and
> I came to the conclusion that for providing the sample projects as ZIP
> file it is necessary to do a official release of them.
> So I checked within the release management [1] what a release must
> contain [2] and how it must be approved [3].
>
> Based on this I prepared the sample project ZIP files and started the
> voting.
> However if something should / must be handled otherwise I’am open for
> help.
What sounds quite strange to me is to release something which is not
under this community's source repositories but somewhere else; to give
you an example, in the same link you refer above, it is reported:
"[...] when a release consists of anything beyond an archive (e.g.,
tarball or zip file) of a source control tag [...]"
implying to me that this is the bare minimum.
I could not find anyway a place where it is clearly stated that
"releases are something you tag from one of community source
repositories", so to me the doubt remains.
Regards.
> [1]: http://www.apache.org/dev/release.html#management
> [2]:
> http://www.apache.org/dev/release.html#what-must-every-release-contain
> [3]: http://www.apache.org/dev/release.html#approving-a-release
>
>> On 22 May 2015, at 12:28, Francesco Chicchiriccò <ilgrosso@apache.org
>> <ma...@apache.org>> wrote:
>>
>> Hi Michael,
>> are you sure that this vote process makes sense? Where is the source
>> tree tag we are voting on?
>>
>> Regards.
>>
>> On 22/05/2015 06:44, Bolz, Michael wrote:
>>> Hello,
>>>
>>> I updated and extended the tutorial for simpel OData Read/Read
>>> Extended/Write Services with Olingo V4 (see section Tutorials on
>>> staging page: http://olingo.staging.apache.org/doc/odata4/).
>>> For this I ill also uploaded the final projects in form of ZIP files.
>>> According to the Apache Release process I understood that this ZIP
>>> file must contain the DEPENDENCIES, LICENCE and NOTES file.
>>> Additional it must be signed.
>>>
>>> I have signed (which was done through the key 15AB5637 in:
>>> http://keyserver.kjsl.org:11371/pks/lookup?search=0x15AB5637&op=vindex)
>>> and uploaded it to:
>>> http://people.apache.org/~mibo/olingo4/DemoServiceTutorials/
>>> <http://people.apache.org/%7Emibo/olingo4/DemoServiceTutorials/>
>>> <http://people.apache.org/%7Emibo/olingo4/DemoServiceTutorials/> as
>>> RC01 versions.
>>> If all is ok and the vote passes I will use them for official Apache
>>> Olingo Homepage (http://olingo.apache.org).
>>>
>>> The vote will be open for at least 72 hours (it will be closed on
>>> Monday 25/05/2015 on 8am CET) and passes if no vote is (-1).
>>>
>>> [ ] +1 Use this sample project for tutorial
>>> [ ] -1 Do not use this sample project because…
>>>
>>> Best regards,
>>> Michael
--
Francesco Chicchiriccò
Tirasa - Open Source Excellence
http://www.tirasa.net/
Involved at The Apache Software Foundation:
member, Syncope PMC chair, Cocoon PMC, Olingo PMC
http://people.apache.org/~ilgrosso/
Re: [VOTE] RC01 - Sample projects for tutorials (as ZIP file)
Posted by "Bolz, Michael" <mi...@sap.com>.
Hi Francesco,
For the tutorials I created the according projects which are not in the Olingo git repository.
My intention was to provide the tutorials together with the according sample project as a single ZIP file to download from the homepage so that they can be easily extracted and started.
Therefore I read the documentation for the Apache release process (http://www.apache.org/dev/release.html <http://www.apache.org/dev/release.html>) and
I came to the conclusion that for providing the sample projects as ZIP file it is necessary to do a official release of them.
So I checked within the release management [1] what a release must contain [2] and how it must be approved [3].
Based on this I prepared the sample project ZIP files and started the voting.
However if something should / must be handled otherwise I’am open for help.
Best regards,
Michael
[1]: http://www.apache.org/dev/release.html#management <http://www.apache.org/dev/release.html#management>
[2]: http://www.apache.org/dev/release.html#what-must-every-release-contain <http://www.apache.org/dev/release.html#what-must-every-release-contain>
[3]: http://www.apache.org/dev/release.html#approving-a-release <http://www.apache.org/dev/release.html#approving-a-release>
> On 22 May 2015, at 12:28, Francesco Chicchiriccò <il...@apache.org> wrote:
>
> Hi Michael,
> are you sure that this vote process makes sense? Where is the source tree tag we are voting on?
>
> Regards.
>
> On 22/05/2015 06:44, Bolz, Michael wrote:
>> Hello,
>>
>> I updated and extended the tutorial for simpel OData Read/Read Extended/Write Services with Olingo V4 (see section Tutorials on staging page: http://olingo.staging.apache.org/doc/odata4/).
>> For this I ill also uploaded the final projects in form of ZIP files.
>> According to the Apache Release process I understood that this ZIP file must contain the DEPENDENCIES, LICENCE and NOTES file.
>> Additional it must be signed.
>>
>> I have signed (which was done through the key 15AB5637 in: http://keyserver.kjsl.org:11371/pks/lookup?search=0x15AB5637&op=vindex)
>> and uploaded it to: http://people.apache.org/~mibo/olingo4/DemoServiceTutorials/ <http://people.apache.org/%7Emibo/olingo4/DemoServiceTutorials/> as RC01 versions.
>> If all is ok and the vote passes I will use them for official Apache Olingo Homepage (http://olingo.apache.org).
>>
>> The vote will be open for at least 72 hours (it will be closed on Monday 25/05/2015 on 8am CET) and passes if no vote is (-1).
>>
>> [ ] +1 Use this sample project for tutorial
>> [ ] -1 Do not use this sample project because…
>>
>> Best regards,
>> Michael
>
> --
> Francesco Chicchiriccò
>
> Tirasa - Open Source Excellence
> http://www.tirasa.net/
>
> Involved at The Apache Software Foundation:
> member, Syncope PMC chair, Cocoon PMC, Olingo PMC
> http://people.apache.org/~ilgrosso/
>
Re: [VOTE] RC01 - Sample projects for tutorials (as ZIP file)
Posted by Francesco Chicchiriccò <il...@apache.org>.
Hi Michael,
are you sure that this vote process makes sense? Where is the source
tree tag we are voting on?
Regards.
On 22/05/2015 06:44, Bolz, Michael wrote:
> Hello,
>
> I updated and extended the tutorial for simpel OData Read/Read
> Extended/Write Services with Olingo V4 (see section Tutorials on
> staging page: http://olingo.staging.apache.org/doc/odata4/).
> For this I ill also uploaded the final projects in form of ZIP files.
> According to the Apache Release process I understood that this ZIP
> file must contain the DEPENDENCIES, LICENCE and NOTES file.
> Additional it must be signed.
>
> I have signed (which was done through the key 15AB5637 in:
> http://keyserver.kjsl.org:11371/pks/lookup?search=0x15AB5637&op=vindex)
> and uploaded it to:
> http://people.apache.org/~mibo/olingo4/DemoServiceTutorials/
> <http://people.apache.org/%7Emibo/olingo4/DemoServiceTutorials/> as
> RC01 versions.
> If all is ok and the vote passes I will use them for official Apache
> Olingo Homepage (http://olingo.apache.org).
>
> The vote will be open for at least 72 hours (it will be closed on
> Monday 25/05/2015 on 8am CET) and passes if no vote is (-1).
>
> [ ] +1 Use this sample project for tutorial
> [ ] -1 Do not use this sample project because…
>
> Best regards,
> Michael
--
Francesco Chicchiriccò
Tirasa - Open Source Excellence
http://www.tirasa.net/
Involved at The Apache Software Foundation:
member, Syncope PMC chair, Cocoon PMC, Olingo PMC
http://people.apache.org/~ilgrosso/
[RESULT][VOTE] RC01 - Sample projects for tutorials (as ZIP file)
Posted by "Bolz, Michael" <mi...@sap.com>.
Hi all,
the vote is finished and has passed with following result:
"+1" votes:
Christian Amend
Michael Bolz
Sven Kobler-Morris
No "-1" vote.
Hence, I will upload the samples projects and publish the tutorials on the Olingo documentation site.
Best Regards,
Michael
PS: Discussion about release of samples as ZIP file will start in a separate mail.
> On 22 May 2015, at 06:44, Bolz, Michael <mi...@sap.com> wrote:
>
> Hello,
>
> I updated and extended the tutorial for simpel OData Read/Read Extended/Write Services with Olingo V4 (see section Tutorials on staging page: http://olingo.staging.apache.org/doc/odata4/ <http://olingo.staging.apache.org/doc/odata4/>).
> For this I ill also uploaded the final projects in form of ZIP files.
> According to the Apache Release process I understood that this ZIP file must contain the DEPENDENCIES, LICENCE and NOTES file.
> Additional it must be signed.
>
> I have signed (which was done through the key 15AB5637 in: http://keyserver.kjsl.org:11371/pks/lookup?search=0x15AB5637&op=vindex <http://keyserver.kjsl.org:11371/pks/lookup?search=0x15AB5637&op=vindex>)
> and uploaded it to: http://people.apache.org/~mibo/olingo4/DemoServiceTutorials/ <http://people.apache.org/~mibo/olingo4/DemoServiceTutorials/> as RC01 versions.
> If all is ok and the vote passes I will use them for official Apache Olingo Homepage (http://olingo.apache.org <http://olingo.apache.org/>).
>
> The vote will be open for at least 72 hours (it will be closed on Monday 25/05/2015 on 8am CET) and passes if no vote is (-1).
>
> [ ] +1 Use this sample project for tutorial
> [ ] -1 Do not use this sample project because…
>
> Best regards,
> Michael