You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@olingo.apache.org by "Kobler-Morris, Sven" <sv...@sap.com> on 2014/07/09 17:01:41 UTC
[DISCUSS] OData 4.0 Client for "Java Script" -> making the first
release
Hi,
after the initial commit of the datajs library to Apache and additional work to adopt it to OData-V4 we think it is time to start a discussion about the first release of the new library.
The current code is available via https://git-wip-us.apache.org/repos/asf?p=olingo-odata4-js.git
However there are some things be done, e.g.
- naming of the new dataJS library (e.g. "Apache Olingo Javascript library" as suggested by Bing)
- finalize features required for the release
- Apache compliance
- Documentation
- ???
What do you think?
regards,
Sven
Re: [DISCUSS] OData 4.0 Client for "Java Script" -> making the first release
Posted by Vikram Pancholi <vi...@gmail.com>.
Hi,
Out of curiosity is there a conscious effort to maintain code base
release names in sync with the OData spec version. If so how would that be
maintained
Regards,
Vikram
On Fri, Jul 11, 2014 at 10:06 AM, Bolz, Michael <mi...@sap.com>
wrote:
> Hi together,
>
> +1 for "Oingo.JS" as name and +1 for Christian as "Release Manager".
> And at least again +1 for making a first release ;o)
>
> Kind regards,
> Michael
>
> On 10.07.2014, at 13:30, Amend, Christian <ch...@sap.com> wrote:
>
> > Hi,
> >
> > I would volunteer as the Release Manager and guide you through the
> release process if there are no objections.
> >
> > Best Regards,
> > Christian
> >
> > -----Original Message-----
> > From: Klevenz, Stephan [mailto:stephan.klevenz@sap.com]
> > Sent: Donnerstag, 10. Juli 2014 13:18
> > To: dev@olingo.apache.org
> > Subject: Re: [DISCUSS] OData 4.0 Client for "Java Script" -> making the
> first release
> >
> > I like Olingo.JS. AFAIK there are no specific requirements by Apache how
> > to name release artifacts. I see only technical (or marketing :) reasons
> > and it should be avoided that the name clashes happen with any other
> > project. I am not a JS expert but in Java we ensured to have a unique
> > namespace within each artifact name. At least I recommend to do some
> > investigations before deciding for a name.
> >
> > Before you can release the JS library there are some requirements by
> > Apache you have to fulfill first. Usually you learn that during
> incubation
> > which is behind us. So its our self responsibility to do the release
> > correctly. Have a look at [1] and [2] to get an overview about how we do
> > releases in Olingo and what Apache release requirements are.
> >
> > Not going to much in details and as Michael has suggested we need 1st a
> > release manager who has already experience and manages all the detailed
> > tasks. Tracking could happen with Jira. Who wants to voluntier?
> >
> > Regards,
> > Stephan
>
>
Re: [DISCUSS] OData 4.0 Client for "Java Script" -> making the
first release
Posted by "Bolz, Michael" <mi...@sap.com>.
Hi together,
+1 for "Oingo.JS" as name and +1 for Christian as "Release Manager".
And at least again +1 for making a first release ;o)
Kind regards,
Michael
On 10.07.2014, at 13:30, Amend, Christian <ch...@sap.com> wrote:
> Hi,
>
> I would volunteer as the Release Manager and guide you through the release process if there are no objections.
>
> Best Regards,
> Christian
>
> -----Original Message-----
> From: Klevenz, Stephan [mailto:stephan.klevenz@sap.com]
> Sent: Donnerstag, 10. Juli 2014 13:18
> To: dev@olingo.apache.org
> Subject: Re: [DISCUSS] OData 4.0 Client for "Java Script" -> making the first release
>
> I like Olingo.JS. AFAIK there are no specific requirements by Apache how
> to name release artifacts. I see only technical (or marketing :) reasons
> and it should be avoided that the name clashes happen with any other
> project. I am not a JS expert but in Java we ensured to have a unique
> namespace within each artifact name. At least I recommend to do some
> investigations before deciding for a name.
>
> Before you can release the JS library there are some requirements by
> Apache you have to fulfill first. Usually you learn that during incubation
> which is behind us. So its our self responsibility to do the release
> correctly. Have a look at [1] and [2] to get an overview about how we do
> releases in Olingo and what Apache release requirements are.
>
> Not going to much in details and as Michael has suggested we need 1st a
> release manager who has already experience and manages all the detailed
> tasks. Tracking could happen with Jira. Who wants to voluntier?
>
> Regards,
> Stephan
RE: [DISCUSS] OData 4.0 Client for "Java Script" -> making the
first release
Posted by "Amend, Christian" <ch...@sap.com>.
Hi,
I would volunteer as the Release Manager and guide you through the release process if there are no objections.
Best Regards,
Christian
-----Original Message-----
From: Klevenz, Stephan [mailto:stephan.klevenz@sap.com]
Sent: Donnerstag, 10. Juli 2014 13:18
To: dev@olingo.apache.org
Subject: Re: [DISCUSS] OData 4.0 Client for "Java Script" -> making the first release
I like Olingo.JS. AFAIK there are no specific requirements by Apache how
to name release artifacts. I see only technical (or marketing :) reasons
and it should be avoided that the name clashes happen with any other
project. I am not a JS expert but in Java we ensured to have a unique
namespace within each artifact name. At least I recommend to do some
investigations before deciding for a name.
Before you can release the JS library there are some requirements by
Apache you have to fulfill first. Usually you learn that during incubation
which is behind us. So its our self responsibility to do the release
correctly. Have a look at [1] and [2] to get an overview about how we do
releases in Olingo and what Apache release requirements are.
Not going to much in details and as Michael has suggested we need 1st a
release manager who has already experience and manages all the detailed
tasks. Tracking could happen with Jira. Who wants to voluntier?
Regards,
Stephan
[1] http://olingo.apache.org/doc/release.html
[2] http://www.apache.org/dev/release.html
On 10.07.14 07:44, "Bolz, Michael" <mi...@sap.com> wrote:
>Hi together,
>
>For naming I suggest simply "Olingo.JS".
>For the "Apache compliance" there are proven "Release Managers" which
>surely help prepare and make a first release.
>For "finalize features required for the release" and the according
>"Documentation" JIRA can be helpful (e.g. tracking open features and
>release notes).
>For "Documentation" also take a look into
>"https://issues.apache.org/jira/browse/OLINGO-345" because I think there
>are some ongoing changes for the homepage.
>
>Apart from that "+1" for doing a release.
>
>Kind regards,
>Michael
>
>
>On 10.07.2014, at 04:38, Yi Ding <yi...@microsoft.com> wrote:
>
>> For name, I would suggest "OData.JS". It inherits from the original
>>name "Data.JS" and is more related to OData. Besides, it has a similar
>>convention as other well-known JavaScript libraries such as "Angular.JS"
>>and "Breeze.JS". "Apache Olingo Javascript Library" seems a really long
>>name.
>>
>> -----Original Message-----
>> From: Kobler-Morris, Sven [mailto:sven.kobler-morris@sap.com]
>> Sent: Wednesday, July 9, 2014 11:02 PM
>> To: dev@olingo.apache.org
>> Subject: [DISCUSS] OData 4.0 Client for "Java Script" -> making the
>>first release
>>
>> Hi,
>>
>>
>>
>> after the initial commit of the datajs library to Apache and additional
>>work to adopt it to OData-V4 we think it is time to start a discussion
>>about the first release of the new library.
>>
>>
>>
>> The current code is available via
>>https://git-wip-us.apache.org/repos/asf?p=olingo-odata4-js.git
>>
>>
>>
>> However there are some things be done, e.g.
>>
>> - naming of the new dataJS library (e.g. "Apache Olingo Javascript
>>library" as suggested by Bing)
>>
>> - finalize features required for the release
>>
>> - Apache compliance
>>
>> - Documentation
>>
>> - ???
>>
>>
>>
>> What do you think?
>>
>>
>>
>> regards,
>>
>> Sven
>>
>
Re: [DISCUSS] OData 4.0 Client for "Java Script" -> making the
first release
Posted by "Klevenz, Stephan" <st...@sap.com>.
I like Olingo.JS. AFAIK there are no specific requirements by Apache how
to name release artifacts. I see only technical (or marketing :) reasons
and it should be avoided that the name clashes happen with any other
project. I am not a JS expert but in Java we ensured to have a unique
namespace within each artifact name. At least I recommend to do some
investigations before deciding for a name.
Before you can release the JS library there are some requirements by
Apache you have to fulfill first. Usually you learn that during incubation
which is behind us. So its our self responsibility to do the release
correctly. Have a look at [1] and [2] to get an overview about how we do
releases in Olingo and what Apache release requirements are.
Not going to much in details and as Michael has suggested we need 1st a
release manager who has already experience and manages all the detailed
tasks. Tracking could happen with Jira. Who wants to voluntier?
Regards,
Stephan
[1] http://olingo.apache.org/doc/release.html
[2] http://www.apache.org/dev/release.html
On 10.07.14 07:44, "Bolz, Michael" <mi...@sap.com> wrote:
>Hi together,
>
>For naming I suggest simply "Olingo.JS".
>For the "Apache compliance" there are proven "Release Managers" which
>surely help prepare and make a first release.
>For "finalize features required for the release" and the according
>"Documentation" JIRA can be helpful (e.g. tracking open features and
>release notes).
>For "Documentation" also take a look into
>"https://issues.apache.org/jira/browse/OLINGO-345" because I think there
>are some ongoing changes for the homepage.
>
>Apart from that "+1" for doing a release.
>
>Kind regards,
>Michael
>
>
>On 10.07.2014, at 04:38, Yi Ding <yi...@microsoft.com> wrote:
>
>> For name, I would suggest "OData.JS". It inherits from the original
>>name "Data.JS" and is more related to OData. Besides, it has a similar
>>convention as other well-known JavaScript libraries such as "Angular.JS"
>>and "Breeze.JS". "Apache Olingo Javascript Library" seems a really long
>>name.
>>
>> -----Original Message-----
>> From: Kobler-Morris, Sven [mailto:sven.kobler-morris@sap.com]
>> Sent: Wednesday, July 9, 2014 11:02 PM
>> To: dev@olingo.apache.org
>> Subject: [DISCUSS] OData 4.0 Client for "Java Script" -> making the
>>first release
>>
>> Hi,
>>
>>
>>
>> after the initial commit of the datajs library to Apache and additional
>>work to adopt it to OData-V4 we think it is time to start a discussion
>>about the first release of the new library.
>>
>>
>>
>> The current code is available via
>>https://git-wip-us.apache.org/repos/asf?p=olingo-odata4-js.git
>>
>>
>>
>> However there are some things be done, e.g.
>>
>> - naming of the new dataJS library (e.g. "Apache Olingo Javascript
>>library" as suggested by Bing)
>>
>> - finalize features required for the release
>>
>> - Apache compliance
>>
>> - Documentation
>>
>> - ???
>>
>>
>>
>> What do you think?
>>
>>
>>
>> regards,
>>
>> Sven
>>
>
Re: [DISCUSS] OData 4.0 Client for "Java Script" -> making the
first release
Posted by "Bolz, Michael" <mi...@sap.com>.
Hi together,
For naming I suggest simply "Olingo.JS".
For the "Apache compliance" there are proven "Release Managers" which surely help prepare and make a first release.
For "finalize features required for the release" and the according "Documentation" JIRA can be helpful (e.g. tracking open features and release notes).
For "Documentation" also take a look into "https://issues.apache.org/jira/browse/OLINGO-345" because I think there are some ongoing changes for the homepage.
Apart from that "+1" for doing a release.
Kind regards,
Michael
On 10.07.2014, at 04:38, Yi Ding <yi...@microsoft.com> wrote:
> For name, I would suggest "OData.JS". It inherits from the original name "Data.JS" and is more related to OData. Besides, it has a similar convention as other well-known JavaScript libraries such as "Angular.JS" and "Breeze.JS". "Apache Olingo Javascript Library" seems a really long name.
>
> -----Original Message-----
> From: Kobler-Morris, Sven [mailto:sven.kobler-morris@sap.com]
> Sent: Wednesday, July 9, 2014 11:02 PM
> To: dev@olingo.apache.org
> Subject: [DISCUSS] OData 4.0 Client for "Java Script" -> making the first release
>
> Hi,
>
>
>
> after the initial commit of the datajs library to Apache and additional work to adopt it to OData-V4 we think it is time to start a discussion about the first release of the new library.
>
>
>
> The current code is available via https://git-wip-us.apache.org/repos/asf?p=olingo-odata4-js.git
>
>
>
> However there are some things be done, e.g.
>
> - naming of the new dataJS library (e.g. "Apache Olingo Javascript library" as suggested by Bing)
>
> - finalize features required for the release
>
> - Apache compliance
>
> - Documentation
>
> - ???
>
>
>
> What do you think?
>
>
>
> regards,
>
> Sven
>
RE: [DISCUSS] OData 4.0 Client for "Java Script" -> making the
first release
Posted by Yi Ding <yi...@microsoft.com>.
For name, I would suggest "OData.JS". It inherits from the original name "Data.JS" and is more related to OData. Besides, it has a similar convention as other well-known JavaScript libraries such as "Angular.JS" and "Breeze.JS". "Apache Olingo Javascript Library" seems a really long name.
-----Original Message-----
From: Kobler-Morris, Sven [mailto:sven.kobler-morris@sap.com]
Sent: Wednesday, July 9, 2014 11:02 PM
To: dev@olingo.apache.org
Subject: [DISCUSS] OData 4.0 Client for "Java Script" -> making the first release
Hi,
after the initial commit of the datajs library to Apache and additional work to adopt it to OData-V4 we think it is time to start a discussion about the first release of the new library.
The current code is available via https://git-wip-us.apache.org/repos/asf?p=olingo-odata4-js.git
However there are some things be done, e.g.
- naming of the new dataJS library (e.g. "Apache Olingo Javascript library" as suggested by Bing)
- finalize features required for the release
- Apache compliance
- Documentation
- ???
What do you think?
regards,
Sven