Hi,

As we have solved all category-x problem, we could rename the package
name of TsFile to org.apache.tsfile, then do the first release.

Jialin Qiao

Christofer Dutz <[email protected]> 于2024年1月4日周四 21:10写道:
>
> I think that’s ok this way …
> Chris
>
> Von: Yuan Tian <[email protected]>
> Datum: Donnerstag, 4. Januar 2024 um 13:16
> An: [email protected] <[email protected]>
> Betreff: Re: First release version of TsFile
> Hi all,
>
> I've already submitted a pr(https://github.com/apache/tsfile/pull/1) to
> tsfile repo which removed two dependency `io.airlift.slice` and
> `org.openjdk.jol.jol-core` which are with GPL 2 licenses.
>
>
> Best regards,
> ------------------------
> Yuan Tian
>
>
> On Thu, Jan 4, 2024 at 4:05 PM Christofer Dutz <[email protected]>
> wrote:
>
> > And we should replace the category-x dependency before trying to release
> > anything.
> >
> > So I would suggest to keep the code in IoTDB until we have released TsFile
> > … as soon as that’s done we can migrate IoTDB to use that released version.
> >
> > Chris
> >
> > Von: Yuan Tian <[email protected]>
> > Datum: Donnerstag, 4. Januar 2024 um 08:23
> > An: [email protected] <[email protected]>
> > Betreff: Re: First release version of TsFile
> > Hi,
> >
> > I think that we keep the old version `0x03` will be better which means that
> > previous tsfile generated by IoTDB needn't be changed.
> >
> > Best regards,
> > --------------------------
> > Yuan Tian
> >
> >
> > On Thu, Jan 4, 2024 at 11:26 AM Jialin Qiao <[email protected]> wrote:
> >
> > > Hi,
> > >
> > > As current version of TsFile is used in IoTDB 0.12, 0.13, 1.x, we
> > > could set the first release version of TsFile 1.0.0.
> > > Local alteration of TsFile should always compatible with old version,
> > > so we could keep the major version 1.x.x as long as possible.
> > >
> > > Note: The version number in tsfile header is 000003. We could change
> > > it to 000001, the 000001 and 000002 are only used before IoTDB 0.11,
> > > which is nolonger maintained.  What do you think?
> > >
> > > Thanks,
> > > Jialin Qiao
> > >
> >

Reply via email to