Hey,

before finally preparing the first RC the only thing thats missing from my side 
is the packaging oft he binaries.
As Chris already said, he would offer some help on the maven assembly plugin.

Background is that it’s a "delicate" topic in the ASF to provide bundled 
artefacts alongside sources (we do not do "binary releases").
So at least one wants an automated and reproducibale way to ensure that 
everyone gets the same binary artefacts and ideally one can check those (if 
only valid things are inside and such).

But if someone else wants to do the assembly stuff, feel free : )
I'm personally lacking skills and experience with that kind of stuff, so I have 
to rely on other volunteers : )

Julian

PS.: But after that is done I would start the first release candidate and we 
can move to the next phase which is Checking the RC and Voting : )

Am 22.07.19, 14:43 schrieb "Xiangdong Huang" <[email protected]>:

    Hi,
    
    Both PR #282 and #274 are merged.
    
    What is the next? Wait for #287 (rename source folder)?
    
    Best,
    -----------------------------------
    Xiangdong Huang
    School of Software, Tsinghua University
    
     黄向东
    清华大学 软件学院
    
    
    Xiangdong Huang <[email protected]> 于2019年7月22日周一 下午4:33写道:
    
    > Hi,
    >
    > +1 for  DO NOT push more new features into rel/0.8.
    >
    > Best,
    > -----------------------------------
    > Xiangdong Huang
    > School of Software, Tsinghua University
    >
    >  黄向东
    > 清华大学 软件学院
    >
    >
    > Julian Feinauer <[email protected]> 于2019年7月22日周一 下午4:24写道:
    >
    >> Hi Xiangdong and Jialin,
    >>
    >> I saw both of your work and agree with both!
    >> So this was no general criticism but rather a sensibilization as I also
    >> saw some features that went into.
    >>
    >> As this release is important for learning I simply took the freedom to
    >> put that out explicitly again : )
    >>
    >> Julian
    >>
    >> Am 22.07.19, 10:09 schrieb "Xiangdong Huang" <[email protected]>:
    >>
    >>     Hi,
    >>
    >>     I cherry-picked a modification for fixing Travis-CI from the master 
to
    >>     rel/0.8 just now, otherwise the branch will fail on Travis...
    >>
    >>     Best,
    >>     -----------------------------------
    >>     Xiangdong Huang
    >>     School of Software, Tsinghua University
    >>
    >>      黄向东
    >>     清华大学 软件学院
    >>
    >>
    >>     Jialin Qiao <[email protected]> 于2019年7月22日周一 下午3:56写道:
    >>
    >>     > Hi Julian,
    >>     >
    >>     > Thanks for the introduction.
    >>     >
    >>     > Most of the commits are from PRs that supplement documents of
    >> version
    >>     > 0.8.0. However, these PRs went to master.
    >>     >
    >>     > From now on, I will change the target of document-related PRs to
    >> rel/
    >>     > 0.8.0.
    >>     >
    >>     > Besides, there are two PRs that should be merged to rel/0.8.0.
    >>     >
    >>     > 1. about generating release folder:
    >>     > https://github.com/apache/incubator-iotdb/pull/282
    >>     > 2. about TsFile documents:
    >>     > https://github.com/apache/incubator-iotdb/pull/274
    >>     >
    >>     > Best,
    >>     > --
    >>     > Jialin Qiao
    >>     > School of Software, Tsinghua University
    >>     >
    >>     > 乔嘉林
    >>     > 清华大学 软件学院
    >>     >
    >>     > > -----原始邮件-----
    >>     > > 发件人: "Julian Feinauer" <[email protected]>
    >>     > > 发送时间: 2019-07-22 15:01:14 (星期一)
    >>     > > 收件人: "[email protected]" <[email protected]>
    >>     > > 抄送:
    >>     > > 主题: Very frequent commits to rel/0.8
    >>     > >
    >>     > > Hi al,
    >>     > >
    >>     > > I just checked the git logs and observerd that there are very
    >> frequent
    >>     > commits to the branch “rel/0.8”, which should not be the case.
    >>     > > So I’ll try to briefly summarize the release process or how the
    >>     > branching model works.
    >>     > >
    >>     > > The branch rel/0.8 is solely for the preparation for the release.
    >> So NO
    >>     > new feature is allowed to come in.
    >>     > > All we do in this branch is to clean up things, fix possible bugs
    >> (in
    >>     > preparation for the release), finish release documents or artifacts
    >> and
    >>     > those things.
    >>     > >
    >>     > > Everything else goes to master.
    >>     > >
    >>     > > So there usually is only one direction, only cherry-picks from
    >> rel/0.8
    >>     > to master are allowed the other direction NOT.
    >>     > > There are very few circumstances where one wants to cherry pick
    >> from
    >>     > master to a rel branch.
    >>     > >
    >>     > > So please try to focus on the master branch with development.
    >>     > > Perhaps it also helps to notify me on PRs that should go to
    >> rel/0.8.
    >>     > >
    >>     > > If there are questions please feel free to ask : )
    >>     > >
    >>     > > Julian
    >>     >
    >>
    >>
    >>
    

Reply via email to