Thanks everyone for prompt reply. Looks like 3.1.3 will be a good option.
We will proceed with this release number. Regards, Mohammad ----- Original Message ----- From: Devaraj Das <[email protected]> To: [email protected] Cc: Sent: Friday, January 27, 2012 5:02 PM Subject: Re: Determining new Oozie release version number +1 for using the number used at Yahoo! On Jan 27, 2012, at 4:09 PM, Alan Gates wrote: > In general you are free to use whatever release number you want. AFAIK > Apache does not impose a release numbering scheme on its projects, though > most seem to follow the pattern that we are used to from Hadoop > (major.minor.patch). Given that I'd choose whatever you feel will cause your > current users and developers the least confusion. 3.1.0 seems to fail that > test since some subset of your users are already used to 3.1.3. If Yahoo > internal 3.1.3 is the same as what you are releasing, then 3.1.3 seems a good > choice. If it's not, I would consider 3.2.0. > > Alan. > > On Jan 27, 2012, at 3:34 PM, Alejandro Abdelnur wrote: > >> IMO we should be good with 3.1.3 as our first Apache release. >> >> Thanks. >> >> Alejandro >> >> On Fri, Jan 27, 2012 at 3:03 PM, Mohammad Islam <[email protected]> wrote: >>> Hi Oozie Mentors and others, >>> We plan to release Oozie for the first time in Apache. >>> We need help to determine the release version. >>> >>> Here is the history timeline: >>> 1. Last oozie released from Github was 3.0. >>> 2. Yahoo certified version of latest Oozie is 3.1.3 >>> >>> What should we use as our new release version? >>> Option 1: Use 3.1.0 >>> Option 2: Use 3.1.3 : will there be any issue with "patch" release as the >>> first one in Apache. >>> Option 3: 3.2.0 >>> >>> Regards, >>> Mohammad >
