Mohammad, What is the urgency for doing a release? This does not affect the fact you are using Oozie from a given commit (which we could tag without doing a release).
I like the idea of doing a release soon, but I'd like to put togethe the bylaws and release process, so we can tune things up after the learnings of using them in a release. Thoughts? Thanks. Alejandro On Wed, Sep 14, 2011 at 10:55 PM, Mohammad Islam <[email protected]> wrote: > Hi, > During our last stage of the release in github, we postponed the formal > release due to transition and some legal issue with Yahoo SGA. However, the > code was already checked in. In addition, at Yahoo, the code is being QE > certified and in GA. > > As planned, we want to create our first release at Apache within next week. > There is a quite a few review requests pending for important fixes too. We > can't commit those unless we are done with the release. > > Due to this urgency, we might not follow the full Dev process in this first > release. Like planning and execution of full RE process. However, we will > follow those in the next release. > > > I will shortly send a list of issues that we addressed in 3.1 release. More > details will be discussed soon. > > Although our dev process will be short-circuited, we will follow the Apace > process such as Apache compliant code/tarball and voting to finalize. > > oozie-committers@ -- Please don't commit any new code now. > > Regards, > Mohammad
