You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by Nick Dimiduk <nd...@apache.org> on 2024/02/16 15:39:51 UTC

Unreleased hbase-thirdparty-3.5.2

Heya team,

I noticed that we still have thirdparty-3.5.2 as an unreleased version in
Jira. Looking at the release archives [0], I don't see that release in our
history -- it appears that the world has moved on. However, we have a
couple tickets [1] assigned to this release. All 5 of these tickets are
also marked as released on a later 4.x release. Checking the pom on
branch-2.4, it has moved on to thirdparty-4.x releases. Thus, I conclude
that we've completely moved on to thirdparty-4.x releases, that we can
leave 3.5.1 as the final thirdparty-3.x release, and I can delete the 3.5.2
unreleased version.

Does this sound right to you?

Thanks,
Nick

[0]: https://archive.apache.org/dist/hbase
[1]: https://issues.apache.org/jira/projects/HBASE/versions/12350365

Re: Archiving old/invalid versions (was Re: Unreleased hbase-thirdparty-3.5.2)

Posted by Andrew Purtell <ap...@apache.org>.
Thanks Nick, really appreciate the clean up.

On Tue, Mar 12, 2024 at 9:18 AM Nick Dimiduk <nd...@apache.org> wrote:

> FYI,
>
> I have marked as "archived" the following unreleased Jira release versions
> that have issues assigned to them but represent EOL release lines:
> * hbase-thirdparty-3.5.2
> * 1.0.4
> * 0.98.25
> * 0.94.28
>
> I have marked as "archived" the following Jira release versions that
> correspond with a feature branch for a ticket that has been completed,
> abandoned, or otherwise closed:
> * hbase-6055 -- "HBase Table Snapshots branch", released in 0.95
> * hbase-6721 -- "RegionServer Group based Assignment", released in 2.0.0
> * hbase-7290 -- "HBase Online Table Snapshot dev branch", released in 0.95
> * HBASE-7912 -- "HBase Backup/Restore Based on HBase Snapshot"
> * hbase-10070 -- "Developer branch for HBASE-10070", released in 1.2.0
> * hbase-10191 -- "Development branch for HBASE-1019"
> * hbase-11339 -- "Developer branch for HBAse Medium Object (MOB) Storage",
> released in 2.0.0
> * HBASE-12259 -- "Bring quorum based write ahead log into HBase", abandoned
> * hbase-12439 -- "Procedure V2"
> * hbase-14439 -- "New/Improved Filesystem Abstractions"
> * HBASE-14850 -- "C++ client implementation"
> * hbase-15283 -- "Revert to IOException in TimeRange constructor to
> maintain API compat in 1.x line", released in 1.2.0
> * HBASE-15631 -- "Backport Regionserver Groups (HBASE-6721) to branch-1",
> released in 1.4.0
> * HBASE-15867 -- "Move HBase replication tracking from ZooKeeper to HBase"
> * HBASE-16961 -- "FileSystem Quotas", released in 2.0.0
> * HBASE-18070 and HBASE-18070.branch-2 -- "Enable memstore replication for
> meta replica", released in 2.4.0
> * HBASE-18095 -- "Provide an option for clients to find the server hosting
> META that does not involve the ZooKeeper client", released in 1.7.0
> * HBASE-18410 -- "FilterList Improvement", released in 2.0.0
> * HBASE-18477 -- "Umbrella JIRA for HBase Read Replica clusters"
> * HBASE-18640 -- "Move mapreduce out of hbase-server into separate
> hbase-mapreduce module", released in 2.0.0
> * HBASE-19064 -- "Synchronous replication for HBase", released in
> 3.0.0-alpha-1
> * HBASE-19397 -- "Design procedures for ReplicationManager to notify peer
> change event from master", released in 2.1.0
> * HBASE-20952 -- "Re-visit the WAL API"
> * HBASE-21512 -- "Reimplement sync client based on async client", released
> in 3.0.0-alpha-1
> * HBASE-22120 -- "Replace HTrace with OpenTelemetry", released in
> 3.0.0-alpha-1
> * HBASE-22514 -- "Reimplement rsgroup feature and move it into core of
> HBase", released in 3.0.0-alpha-1
> * HBASE-26067 -- "Change the way on how we track store file list", released
> in 2.6.0
> * HBASE-26233 -- "The region replication framework should not be built upon
> the general replication framework", released in 3.0.0-alpha-1
>
> I have deleted the following unreleased Jira versions that have no
> associated tickets:
> * hbase-connectors
>
> Thanks,
> Nick
>
> On Tue, Mar 12, 2024 at 4:36 PM Nick Dimiduk <nd...@apache.org> wrote:
>
> > I have marked this version as "archived".
> >
> > On Wed, Feb 21, 2024 at 11:42 AM 张铎(Duo Zhang) <pa...@gmail.com>
> > wrote:
> >
> >> If there are already commits to the branch, usually we should archive
> >> that version instead of deleting it.
> >>
> >> Andrew Purtell <ap...@apache.org> 于2024年2月17日周六 03:45写道:
> >> >
> >> > Sounds right to me.
> >> >
> >> > On Fri, Feb 16, 2024 at 7:40 AM Nick Dimiduk <nd...@apache.org>
> >> wrote:
> >> >
> >> > > Heya team,
> >> > >
> >> > > I noticed that we still have thirdparty-3.5.2 as an unreleased
> >> version in
> >> > > Jira. Looking at the release archives [0], I don't see that release
> >> in our
> >> > > history -- it appears that the world has moved on. However, we have
> a
> >> > > couple tickets [1] assigned to this release. All 5 of these tickets
> >> are
> >> > > also marked as released on a later 4.x release. Checking the pom on
> >> > > branch-2.4, it has moved on to thirdparty-4.x releases. Thus, I
> >> conclude
> >> > > that we've completely moved on to thirdparty-4.x releases, that we
> can
> >> > > leave 3.5.1 as the final thirdparty-3.x release, and I can delete
> the
> >> 3.5.2
> >> > > unreleased version.
> >> > >
> >> > > Does this sound right to you?
> >> > >
> >> > > Thanks,
> >> > > Nick
> >> > >
> >> > > [0]: https://archive.apache.org/dist/hbase
> >> > > [1]:
> https://issues.apache.org/jira/projects/HBASE/versions/12350365
> >> > >
> >> >
> >> >
> >> > --
> >> > Best regards,
> >> > Andrew
> >> >
> >> > Unrest, ignorance distilled, nihilistic imbeciles -
> >> >     It's what we’ve earned
> >> > Welcome, apocalypse, what’s taken you so long?
> >> > Bring us the fitting end that we’ve been counting on
> >> >    - A23, Welcome, Apocalypse
> >>
> >
>


-- 
Best regards,
Andrew

Unrest, ignorance distilled, nihilistic imbeciles -
    It's what we’ve earned
Welcome, apocalypse, what’s taken you so long?
Bring us the fitting end that we’ve been counting on
   - A23, Welcome, Apocalypse

Archiving old/invalid versions (was Re: Unreleased hbase-thirdparty-3.5.2)

Posted by Nick Dimiduk <nd...@apache.org>.
FYI,

I have marked as "archived" the following unreleased Jira release versions
that have issues assigned to them but represent EOL release lines:
* hbase-thirdparty-3.5.2
* 1.0.4
* 0.98.25
* 0.94.28

I have marked as "archived" the following Jira release versions that
correspond with a feature branch for a ticket that has been completed,
abandoned, or otherwise closed:
* hbase-6055 -- "HBase Table Snapshots branch", released in 0.95
* hbase-6721 -- "RegionServer Group based Assignment", released in 2.0.0
* hbase-7290 -- "HBase Online Table Snapshot dev branch", released in 0.95
* HBASE-7912 -- "HBase Backup/Restore Based on HBase Snapshot"
* hbase-10070 -- "Developer branch for HBASE-10070", released in 1.2.0
* hbase-10191 -- "Development branch for HBASE-1019"
* hbase-11339 -- "Developer branch for HBAse Medium Object (MOB) Storage",
released in 2.0.0
* HBASE-12259 -- "Bring quorum based write ahead log into HBase", abandoned
* hbase-12439 -- "Procedure V2"
* hbase-14439 -- "New/Improved Filesystem Abstractions"
* HBASE-14850 -- "C++ client implementation"
* hbase-15283 -- "Revert to IOException in TimeRange constructor to
maintain API compat in 1.x line", released in 1.2.0
* HBASE-15631 -- "Backport Regionserver Groups (HBASE-6721) to branch-1",
released in 1.4.0
* HBASE-15867 -- "Move HBase replication tracking from ZooKeeper to HBase"
* HBASE-16961 -- "FileSystem Quotas", released in 2.0.0
* HBASE-18070 and HBASE-18070.branch-2 -- "Enable memstore replication for
meta replica", released in 2.4.0
* HBASE-18095 -- "Provide an option for clients to find the server hosting
META that does not involve the ZooKeeper client", released in 1.7.0
* HBASE-18410 -- "FilterList Improvement", released in 2.0.0
* HBASE-18477 -- "Umbrella JIRA for HBase Read Replica clusters"
* HBASE-18640 -- "Move mapreduce out of hbase-server into separate
hbase-mapreduce module", released in 2.0.0
* HBASE-19064 -- "Synchronous replication for HBase", released in
3.0.0-alpha-1
* HBASE-19397 -- "Design procedures for ReplicationManager to notify peer
change event from master", released in 2.1.0
* HBASE-20952 -- "Re-visit the WAL API"
* HBASE-21512 -- "Reimplement sync client based on async client", released
in 3.0.0-alpha-1
* HBASE-22120 -- "Replace HTrace with OpenTelemetry", released in
3.0.0-alpha-1
* HBASE-22514 -- "Reimplement rsgroup feature and move it into core of
HBase", released in 3.0.0-alpha-1
* HBASE-26067 -- "Change the way on how we track store file list", released
in 2.6.0
* HBASE-26233 -- "The region replication framework should not be built upon
the general replication framework", released in 3.0.0-alpha-1

I have deleted the following unreleased Jira versions that have no
associated tickets:
* hbase-connectors

Thanks,
Nick

On Tue, Mar 12, 2024 at 4:36 PM Nick Dimiduk <nd...@apache.org> wrote:

> I have marked this version as "archived".
>
> On Wed, Feb 21, 2024 at 11:42 AM 张铎(Duo Zhang) <pa...@gmail.com>
> wrote:
>
>> If there are already commits to the branch, usually we should archive
>> that version instead of deleting it.
>>
>> Andrew Purtell <ap...@apache.org> 于2024年2月17日周六 03:45写道:
>> >
>> > Sounds right to me.
>> >
>> > On Fri, Feb 16, 2024 at 7:40 AM Nick Dimiduk <nd...@apache.org>
>> wrote:
>> >
>> > > Heya team,
>> > >
>> > > I noticed that we still have thirdparty-3.5.2 as an unreleased
>> version in
>> > > Jira. Looking at the release archives [0], I don't see that release
>> in our
>> > > history -- it appears that the world has moved on. However, we have a
>> > > couple tickets [1] assigned to this release. All 5 of these tickets
>> are
>> > > also marked as released on a later 4.x release. Checking the pom on
>> > > branch-2.4, it has moved on to thirdparty-4.x releases. Thus, I
>> conclude
>> > > that we've completely moved on to thirdparty-4.x releases, that we can
>> > > leave 3.5.1 as the final thirdparty-3.x release, and I can delete the
>> 3.5.2
>> > > unreleased version.
>> > >
>> > > Does this sound right to you?
>> > >
>> > > Thanks,
>> > > Nick
>> > >
>> > > [0]: https://archive.apache.org/dist/hbase
>> > > [1]: https://issues.apache.org/jira/projects/HBASE/versions/12350365
>> > >
>> >
>> >
>> > --
>> > Best regards,
>> > Andrew
>> >
>> > Unrest, ignorance distilled, nihilistic imbeciles -
>> >     It's what we’ve earned
>> > Welcome, apocalypse, what’s taken you so long?
>> > Bring us the fitting end that we’ve been counting on
>> >    - A23, Welcome, Apocalypse
>>
>

Re: Unreleased hbase-thirdparty-3.5.2

Posted by Nick Dimiduk <nd...@apache.org>.
I have marked this version as "archived".

On Wed, Feb 21, 2024 at 11:42 AM 张铎(Duo Zhang) <pa...@gmail.com>
wrote:

> If there are already commits to the branch, usually we should archive
> that version instead of deleting it.
>
> Andrew Purtell <ap...@apache.org> 于2024年2月17日周六 03:45写道:
> >
> > Sounds right to me.
> >
> > On Fri, Feb 16, 2024 at 7:40 AM Nick Dimiduk <nd...@apache.org>
> wrote:
> >
> > > Heya team,
> > >
> > > I noticed that we still have thirdparty-3.5.2 as an unreleased version
> in
> > > Jira. Looking at the release archives [0], I don't see that release in
> our
> > > history -- it appears that the world has moved on. However, we have a
> > > couple tickets [1] assigned to this release. All 5 of these tickets are
> > > also marked as released on a later 4.x release. Checking the pom on
> > > branch-2.4, it has moved on to thirdparty-4.x releases. Thus, I
> conclude
> > > that we've completely moved on to thirdparty-4.x releases, that we can
> > > leave 3.5.1 as the final thirdparty-3.x release, and I can delete the
> 3.5.2
> > > unreleased version.
> > >
> > > Does this sound right to you?
> > >
> > > Thanks,
> > > Nick
> > >
> > > [0]: https://archive.apache.org/dist/hbase
> > > [1]: https://issues.apache.org/jira/projects/HBASE/versions/12350365
> > >
> >
> >
> > --
> > Best regards,
> > Andrew
> >
> > Unrest, ignorance distilled, nihilistic imbeciles -
> >     It's what we’ve earned
> > Welcome, apocalypse, what’s taken you so long?
> > Bring us the fitting end that we’ve been counting on
> >    - A23, Welcome, Apocalypse
>

Re: Unreleased hbase-thirdparty-3.5.2

Posted by "张铎(Duo Zhang)" <pa...@gmail.com>.
If there are already commits to the branch, usually we should archive
that version instead of deleting it.

Andrew Purtell <ap...@apache.org> 于2024年2月17日周六 03:45写道:
>
> Sounds right to me.
>
> On Fri, Feb 16, 2024 at 7:40 AM Nick Dimiduk <nd...@apache.org> wrote:
>
> > Heya team,
> >
> > I noticed that we still have thirdparty-3.5.2 as an unreleased version in
> > Jira. Looking at the release archives [0], I don't see that release in our
> > history -- it appears that the world has moved on. However, we have a
> > couple tickets [1] assigned to this release. All 5 of these tickets are
> > also marked as released on a later 4.x release. Checking the pom on
> > branch-2.4, it has moved on to thirdparty-4.x releases. Thus, I conclude
> > that we've completely moved on to thirdparty-4.x releases, that we can
> > leave 3.5.1 as the final thirdparty-3.x release, and I can delete the 3.5.2
> > unreleased version.
> >
> > Does this sound right to you?
> >
> > Thanks,
> > Nick
> >
> > [0]: https://archive.apache.org/dist/hbase
> > [1]: https://issues.apache.org/jira/projects/HBASE/versions/12350365
> >
>
>
> --
> Best regards,
> Andrew
>
> Unrest, ignorance distilled, nihilistic imbeciles -
>     It's what we’ve earned
> Welcome, apocalypse, what’s taken you so long?
> Bring us the fitting end that we’ve been counting on
>    - A23, Welcome, Apocalypse

Re: Unreleased hbase-thirdparty-3.5.2

Posted by Andrew Purtell <ap...@apache.org>.
Sounds right to me.

On Fri, Feb 16, 2024 at 7:40 AM Nick Dimiduk <nd...@apache.org> wrote:

> Heya team,
>
> I noticed that we still have thirdparty-3.5.2 as an unreleased version in
> Jira. Looking at the release archives [0], I don't see that release in our
> history -- it appears that the world has moved on. However, we have a
> couple tickets [1] assigned to this release. All 5 of these tickets are
> also marked as released on a later 4.x release. Checking the pom on
> branch-2.4, it has moved on to thirdparty-4.x releases. Thus, I conclude
> that we've completely moved on to thirdparty-4.x releases, that we can
> leave 3.5.1 as the final thirdparty-3.x release, and I can delete the 3.5.2
> unreleased version.
>
> Does this sound right to you?
>
> Thanks,
> Nick
>
> [0]: https://archive.apache.org/dist/hbase
> [1]: https://issues.apache.org/jira/projects/HBASE/versions/12350365
>


-- 
Best regards,
Andrew

Unrest, ignorance distilled, nihilistic imbeciles -
    It's what we’ve earned
Welcome, apocalypse, what’s taken you so long?
Bring us the fitting end that we’ve been counting on
   - A23, Welcome, Apocalypse