[
https://issues.apache.org/jira/browse/SQOOP-3199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16209364#comment-16209364
]
Attila Szabo commented on SQOOP-3199:
-------------------------------------
Hey [~BoglarkaEgyed],
Let me first answer only the second part of your concerns:
As far as I remember the Sqoop release policy was not following that release
policy what you'd referred to. It was allowed in the past as well that features
had been included in "patch releases". The only thing what was not allowed is
to introduce compatibility breaking changes? AFAR non of the PMC members
mentioned anything like this to me either.
The second part:
As you might remember we had a quite long conversation on the dev list about if
we gonna release 1.4.7 or 1.5.0. We'd made an agreement to just release 1.4.7,
b/c we'd like to have bigger changes for 1.5.0 (like new gradle based build
system, and so on), thus still my humble opinion is to stick to 1.4.7.
But regardless these pros/cons I'm more than open to change the scope of the
release if it is really the wish of the community, and PMC, but I will still
advocate to stick to 1.4.7 if it's possible (just b/c we had a past agreement).
Looking forward for your input, and many thanks for bringing up this topic here
as well,
Attila
> Sqoop 1.4.7 release preparation
> -------------------------------
>
> Key: SQOOP-3199
> URL: https://issues.apache.org/jira/browse/SQOOP-3199
> Project: Sqoop
> Issue Type: Task
> Reporter: Attila Szabo
> Assignee: Attila Szabo
> Fix For: no-release
>
> Attachments: text.html
>
>
> Umbrella jira for 1.4.6 release.
> For reference, the release wikis are:
> https://cwiki.apache.org/confluence/display/SQOOP/How+to+Release
> https://cwiki.apache.org/confluence/display/SQOOP/How+to+Release+Sqoop2
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
