Thanks for driving this, I will be ready to release hadoop-3.4.0-RC1 in 1-2
days.

Best Regards,
Shilun Fan.

On Thu, Jan 25, 2024 at 10:22 AM Xiaoqiao He <hexiaoq...@apache.org> wrote:

> Hi all, the branch-3.4.0 codebase has been frozen. Hadoop-3.4.0-RC1 will
> be ready for a while.
> Thanks.
>
> Best Regards,
> - He Xiaoqiao
>
>
> On Tue, Jan 23, 2024 at 7:58 AM slfan1989 <slfan1...@apache.org> wrote:
>
>> branch-3.4/branch-3.4.0 was created from the trunk branch, including the
>> changes from branch-3.3.
>>
>> Best Regards,
>> Shilun Fan.
>>
>> On Tue, Jan 23, 2024 at 12:58 AM Brahma Reddy Battula <bra...@apache.org>
>> wrote:
>>
>> > Thanks for driving this.
>> >
>> > One query:
>> > Does all the jiras from 3.3 are part of the 3.4?
>> >
>> >
>> >
>> >
>> > On Mon, 22 Jan 2024 at 11:50 AM, slfan1989 <slfan1...@apache.org>
>> wrote:
>> >
>> >> Thank you very much for specifying the frozen time for the
>> >> Branch-3.4.0.  @Xiaoqiao
>> >> He <hexiaoq...@apache.org>
>> >>
>> >> If there is a need to backport any PRs to branch-3.4/branch-3.4.0,
>> please
>> >> feel free to contact me.
>> >>
>> >> Best Regards,
>> >> Shilun Fan.
>> >>
>> >> On Mon, Jan 22, 2024 at 1:58 PM Xiaoqiao He <hexiaoq...@apache.org>
>> >> wrote:
>> >>
>> >> > Hi All,
>> >> >
>> >> > Branch-3.4.0 will be frozen this Thursday (UTC 00:00 Jan 25, 2024).
>> >> > If there is any blocker/critical PR please backport to branch-3.4 and
>> >> > branch-3.4.0 or sync to me or hadoop-3.4.0 RM Shilun Fan.
>> >> >
>> >> > If any reported issues are not ready in time please wait for the next
>> >> > release.
>> >> >
>> >> > Thanks all.
>> >> >
>> >> > Best Regards,
>> >> > - He Xiaoqiao
>> >> >
>> >> >
>> >> >
>> >> > On Mon, Jan 22, 2024 at 10:43 AM slfan1989 <slfan1...@apache.org>
>> >> wrote:
>> >> >
>> >> >> Thank you for the feedback!
>> >> >>
>> >> >> I apologize for updating partial information in the Hadoop module.
>> >> >>
>> >> >> Today, I will complete the rollback of the modified JIRA and add
>> back
>> >> the
>> >> >> 3.4.0 version.
>> >> >>
>> >> >> Best
>> >> >>
>> >> >> On Mon, Jan 22, 2024 at 10:38 AM Xiaoqiao He <hexiaoq...@apache.org
>> >
>> >> >> wrote:
>> >> >>
>> >> >>> Thanks all for your input. Connected to Shilun offline yesterday,
>> and
>> >> he
>> >> >>> will
>> >> >>> update or recover the fix version tag before 3.4.0-RC1.
>> >> >>>
>> >> >>> Best Regards,
>> >> >>> - He Xiaoqiao
>> >> >>>
>> >> >>>
>> >> >>> On Mon, Jan 22, 2024 at 9:53 AM Masatake Iwasaki <
>> >> iwasak...@apache.org>
>> >> >>> wrote:
>> >> >>>
>> >> >>> > > As I mentioned in my comment on HADOOP-18045, I think 3.4.0
>> should
>> >> >>> still
>> >> >>> > be
>> >> >>> > > included in the Fix versions,
>> >> >>> > > even if it was already released in 3.3.x. If I understand
>> >> correctly,
>> >> >>> this
>> >> >>> > > is usually our practice.
>> >> >>> >
>> >> >>> > +1.
>> >> >>> > We can not assume 3.4.x contains all fixes of 3.3.y since we are
>> >> >>> > maintaining both branch-3.4 and branch-3.3.
>> >> >>> >
>> >> >>> > On Sun, Jan 21, 2024 at 2:45 PM Takanobu Asanuma <
>> >> tasan...@apache.org>
>> >> >>> > wrote:
>> >> >>> > >
>> >> >>> > > Hi Shilun,
>> >> >>> > >
>> >> >>> > > Thank you for leading the 3.4.0 release.
>> >> >>> > >
>> >> >>> > > > 2. In JIRA issues where other release versions have been
>> >> released,
>> >> >>> > remove
>> >> >>> > > > the 3.4.0 entry from the fix version.
>> >> >>> > >
>> >> >>> > > As I mentioned in my comment on HADOOP-18045, I think 3.4.0
>> should
>> >> >>> still
>> >> >>> > be
>> >> >>> > > included in the Fix versions,
>> >> >>> > > even if it was already released in 3.3.x. If I understand
>> >> correctly,
>> >> >>> this
>> >> >>> > > is usually our practice.
>> >> >>> > >
>> >> >>> > > Thanks,
>> >> >>> > > - Takanobu
>> >> >>> > >
>> >> >>> > > 2024年1月21日(日) 13:56 slfan1989 <slfan1...@apache.org>:
>> >> >>> > >
>> >> >>> > > > Hi All,
>> >> >>> > > >
>> >> >>> > > > I am currently preparing to release hadoop-3.4.0-RC1 and
>> need to
>> >> >>> > perform
>> >> >>> > > > some operations on the JIRA issues related to HADOOP, HDFS,
>> >> YARN,
>> >> >>> and
>> >> >>> > > > MAPREDUCE. Specifically, the tasks include:
>> >> >>> > > >
>> >> >>> > > > 1. For JIRA issues with target version set to 3.4.0 and
>> marked
>> >> as
>> >> >>> > > > non-blocker, update the target version to 3.5.0.
>> >> >>> > > >
>> >> >>> > > > 2. In JIRA issues where other release versions have been
>> >> released,
>> >> >>> > remove
>> >> >>> > > > the 3.4.0 entry from the fix version.
>> >> >>> > > >
>> >> >>> > > > 3. For JIRA issues with target version set to 3.4.0, fix
>> version
>> >> >>> set to
>> >> >>> > > > 3.4.0, and status set to
>> >> >>> > > > RESOLVED, if Affects Version/s, Component/s, and Hadoop Flags
>> >> are
>> >> >>> not
>> >> >>> > set,
>> >> >>> > > > complete the information.
>> >> >>> > > >
>> >> >>> > > > Best Regards,
>> >> >>> > > > - Shilun Fan.
>> >> >>> > > >
>> >> >>> > > > On Fri, Jan 19, 2024 at 3:23 PM Xiaoqiao He <
>> >> xq.he2...@gmail.com>
>> >> >>> > wrote:
>> >> >>> > > >
>> >> >>> > > > > Hi All,
>> >> >>> > > > >
>> >> >>> > > > > Branch trunk has been set to 3.5.0-SNAPSHOT and branch-3.4
>> is
>> >> >>> > created[1].
>> >> >>> > > > >
>> >> >>> > > > > Please set the proper fix version while committing jira,
>> 3.5.0
>> >> >>> should
>> >> >>> > > > > be priority. If there is any blocker/critical please also
>> >> >>> backport to
>> >> >>> > > > > branch-3.4 or sync to me or RM Shilun Fan.
>> >> >>> > > > >
>> >> >>> > > > > Shilun will start 3.4.0 RC1 voting in the next few days.
>> >> >>> > > > >
>> >> >>> > > > > Thanks.
>> >> >>> > > > >
>> >> >>> > > > > Best Regards,
>> >> >>> > > > > - He Xiaoqiao
>> >> >>> > > > >
>> >> >>> > > > > [1] https://github.com/apache/hadoop/commits/branch-3.4
>> >> >>> > > > >
>> >> >>> > > >
>> >> >>> >
>> >> >>> >
>> >> ---------------------------------------------------------------------
>> >> >>> > To unsubscribe, e-mail: private-unsubscr...@hadoop.apache.org
>> >> >>> > For additional commands, e-mail: private-h...@hadoop.apache.org
>> >> >>> >
>> >> >>> >
>> >> >>>
>> >> >>
>> >>
>> >
>>
>

Reply via email to