[Development] Proposal to adjust release candidate process
jani.heikkinen at qt.io
Tue Mar 28 08:47:53 CEST 2017
> -----Original Message-----
> From: Development [mailto:development-bounces+jani.heikkinen=qt.io at qt-
> project.org] On Behalf Of Lars Knoll
> Sent: tiistaina 28. maaliskuuta 2017 9.33
> To: Alex Blasche <alexander.blasche at qt.io>
> Cc: Qt development mailing list <development at qt-project.org>
> Subject: Re: [Development] Proposal to adjust release candidate process
> > On 28 Mar 2017, at 08:09, Alex Blasche <alexander.blasche at qt.io> wrote:
> >>> Sounds good, but please remember we'll need to keep at least the
> >>> source tarballs for each and every beta and RC that we release.
> >> Yeah, that's OK
> > This implies that the user can identify the exact tag or version (aka beta 5)
> somewhere in the installer. Each bug report has to state this value.
> Yes, either through a number or (preferable IMO) by simply putting the sha1
> of qt5.git into a visible place.
We were planning to use Beta N in installer UI as well as git tags. should be ok and it is following current ways of working
> Development mailing list
> Development at qt-project.org
More information about the Development