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 <[email protected]> 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 <[email protected]> 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:[email protected]] > > Sent: Donnerstag, 10. Juli 2014 13:18 > > To: [email protected] > > 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 > >
