> -----Original Message-----
> From: sean.harmer On Behalf Of Sean Harmer
> Sent: maanantaina 27. kesäkuuta 2016 11.46
> To: [email protected]
> Cc: Tuukka Turunen <[email protected]>
> Subject: Re: [Development] [Releasing] brown paper bag issue in Qt 5.6.1
> packages
>
> On Monday 27 June 2016 07:18:02 Tuukka Turunen wrote:
> > > -----Original Message-----
> > > From: Development [mailto:development-
> > > [email protected]] On Behalf Of Sean
> > > bounces+Harmer
> > > Sent: perjantaina 24. kesäkuuta 2016 11.23
> > > To: [email protected]
> > > Subject: Re: [Development] [Releasing] brown paper bag issue in Qt
> > > 5.6.1 packages
> > >
> > > -- clip ---
> > > This is why we have a process. How is this situation compatible with
> > > TQC's ISO
> 9001 certification?!
> > >
> >
> >
> > Hi Sean,
> >
> > Making a fix release fits well with the release process of the ISO
> > 9001 certification, no problems there.
>
> ISO 9001 is about following the processes that you say you follow. This is
> clearly not the case here as a process was made up on the spot to do it
> quickly. This is clearly a non-conformance. Removing packages is clearly
> another.
>
Deleting the package was an error that is fixed as soon as possible. It is not
part of the process to do so.
> I'm not disputing that a process for quick fix releases should be made, but
> the time to do this is not when there is a sudden need for it. That's when
> unforeseen mistakes slip through the cracks.
>
I do agree that the process of making this kind of releases should be better
documented and agreed upon by the various stakeholders. Release team has also
earlier made similar ones, but mostly related to packaging problems.
> Had the decision to just cherry pick this one fix and apply the usual release
> process for a 5.6.2 had been made, the level of testing could have been
> reduced accordingly to speed up the process and a message put out saying to
> avoid 5.6.1 if you are using QML/Quick. With a 5.6.2 release coming shortly,
> users could have made the informed decision to stick with 5.6.0 until 5.6.2
> was ready. If the installer had the ability to downgrade as well as upgrade,
> this would be even easier.
>
I think it would be best to have this discussion in the next release team
meeting and in addition at QtCon. Changing the version number in Qt modules,
re-doing all change files etc, takes time and especially when done so close to
release would cause users possibly to miss the other changes in the logs.
We need to have a process that is lightweight enough to make "hotfixes" when
necessary. If the process of making for example a security fix is too time
consuming, it will cause us not to use it as often as we perhaps should.
Yours,
Tuukka
> Cheers,
>
> Sean
>
> > In general, it is valuable to be able to make releases quickly to fix
> > e.g. a security vulnerability. The fastest way to do it is to push the
> > needed change (or changes) into the release branch, and create new
> > release directly from there. I do not have any strong opinion if the
> > number of the release should be x.y.z.1 , x.y.z-1 or even x.y.(z+1).
> > Earlier the notation has been -1, but if there is desire to change it
> > going forward, I do not think that is a problem.
>
> > Yours,
> >
> > Tuukka
> >
> >
> >
> >
> > > Sean
> > > --
> > > Dr Sean Harmer | [email protected] | Managing Director UK KDAB
> > > (UK) Ltd, a KDAB Group company Tel. +44 (0)1625 809908; Sweden (HQ)
> > > +46-
> > > 563-540090
> > > Mobile: +44 (0)7545 140604
> > > KDAB - Qt Experts
> > > _______________________________________________
> > > Development mailing list
> > > [email protected]
> > > http://lists.qt-project.org/mailman/listinfo/development
> >
> > _______________________________________________
> > Development mailing list
> > [email protected]
> > http://lists.qt-project.org/mailman/listinfo/development
>
> --
> Dr Sean Harmer | [email protected] | Managing Director UK KDAB
> (UK) Ltd, a KDAB Group company Tel. +44 (0)1625 809908; Sweden (HQ) +46-
> 563-540090
> Mobile: +44 (0)7545 140604
> KDAB - Qt Experts
_______________________________________________
Development mailing list
[email protected]
http://lists.qt-project.org/mailman/listinfo/development
