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 <[email protected]> wrote: > > Hi Francesco, > >> On 25 May 2015, at 08:50, Francesco Chicchiriccò <[email protected] >> <mailto:[email protected]>> 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ò <[email protected] >>>> <mailto:[email protected]> <mailto:[email protected] >>>> <mailto:[email protected]>>> 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/>
smime.p7s
Description: S/MIME cryptographic signature
