this rc is for parquet-format so you have time to provide a patch for parquet-mr. parquet-mr will follow later.
On Wed, Feb 11, 2015 at 1:27 PM, lukas nalezenec <[email protected]> wrote: > Hi, > I would like to commit PARQUET-175 > <https://issues.apache.org/jira/browse/PARQUET-175> before release. > Its small improvement but it can affect architectural decisions a lot - > without this commit parquet-protobuf can read only data written by > parquet-protobuf. > > > https://github.com/lukasnalezenec/incubator-parquet-mr/commits/master > > On Wed, Feb 11, 2015 at 7:11 PM, Julien Le Dem <[email protected] > > > wrote: > > > It sounds like it. I started a thread on the incubator mailing list about > > this. > > But yes it is the official guideline, so we have to comply. > > > > On Tue, Feb 10, 2015 at 3:10 PM, Ryan Blue <[email protected]> wrote: > > > > > On 02/10/2015 02:56 PM, Julien Le Dem wrote: > > > > > >> changing the artifact name will break the conflict resolution when the > > >> project is not incubating anymore. > > >> we should not change the artifact names (again) when we get out of the > > >> incubator. > > >> > > >> I finally found the guideline Tom was referring to: > > >> > > http://incubator.apache.org/guides/release-java.html#best-practice-maven > > >> "It is best to use the groupId and artifactId that will be used upon > > >> graduation. The version should includeincubating (or incubator) to > > ensure > > >> that the artifacts created comply with Incubator release policy > > >> < > http://incubator.apache.org/incubation/Incubation_Policy.html#Releases > > >" > > >> > > > > > > In that case, I think the most reasonable thing is to add it to the > > > version string. Do you agree, Julien? > > > > > > > > > rb > > > > > > > > > -- > > > Ryan Blue > > > Software Engineer > > > Cloudera, Inc. > > > > > >
