Thanks Nick, really appreciate the clean up.
On Tue, Mar 12, 2024 at 9:18 AM Nick Dimiduk 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.9
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 br
I have marked this version as "archived".
On Wed, Feb 21, 2024 at 11:42 AM 张铎(Duo Zhang)
wrote:
> If there are already commits to the branch, usually we should archive
> that version instead of deleting it.
>
> Andrew Purtell 于2024年2月17日周六 03:45写道:
> >
> > Sounds right to me.
> >
> > On Fri, Fe
If there are already commits to the branch, usually we should archive
that version instead of deleting it.
Andrew Purtell 于2024年2月17日周六 03:45写道:
>
> Sounds right to me.
>
> On Fri, Feb 16, 2024 at 7:40 AM Nick Dimiduk wrote:
>
> > Heya team,
> >
> > I noticed that we still have thirdparty-3.5.2
Sounds right to me.
On Fri, Feb 16, 2024 at 7:40 AM Nick Dimiduk 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. How