sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Boglarka Egyed (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-3199) Sqoop 1.4.7 release preparation
Date Wed, 04 Oct 2017 12:20:03 GMT

    [ https://issues.apache.org/jira/browse/SQOOP-3199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16191184#comment-16191184

Boglarka Egyed commented on SQOOP-3199:

Hi [~maugli],

All right, thank you for the quick response!

Before building the RC-1 please take care of some findings which I have found during checking
the current status of this release:
* JIRAs which have been asked to include into 1.4.7 but still not in branch-1.4.7: SQOOP-3194,
* CHANGELOG.txt contains numerous JIRAs which are still in Open state without any patch or
commit (e.g. SQOOP-956, SQOOP-3052, etc..) - please run an automatic check to get the full
list, there are many unfortunately.
* SQOOP-3174 is in branch-1.4.7 but doesn't present in CHANGELOG.txt - there may be others
as well, please check those also.
* I am a bit concerned about the scope of this release. In a patch release only backwards-compatible
bug fixes should be introduced however I see other items on the CHANGELOG as New Features,
etc. - could you please reconsider the scope of 1.4.7 release? Or wouldn't it be more reasonable
to make it as 1.5.0? What do you think?

Thank you in advance,

> 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

View raw message