Em ter 27 maio 2014, às 01:10:04, Thiago Macieira escreveu:
> Also, please note that the discussion some months ago ended with both Ossi
> and I recommending that the tag be merged back into the branch for the
> minor series. That is, 5.3.0 gets tagged as v5.3.0 on release and v5.3.0 s
> merged in
Em ter 27 maio 2014, às 09:26:38, Oswald Buddenhagen escreveu:
> > I don’t see any problems with having named branches for patch level
> > releases, and it is what we agreed to some months ago. Can you explain why
> > you’d want to remove the branches once the release is done?
> >
> >
>
> let's s
On Tue, May 27, 2014 at 06:25:37AM +, Knoll Lars wrote:
> On 26/05/14 21:59, "Thiago Macieira" wrote:
> >I've just seen that all the Qt repositories got a 5.3.0 branch
>
and they lost the release branches a minute later. it was a renaming.
> >(including those for which a release not called "5
On 26/05/14 21:59, "Thiago Macieira" wrote:
>I've just seen that all the Qt repositories got a 5.3.0 branch (including
>those for which a release not called "5.3.0" was produced).
>
>I'm proposing to reverse that. There's no point in having those branches,
>since after the code is tagged and rel
I've just seen that all the Qt repositories got a 5.3.0 branch (including
those for which a release not called "5.3.0" was produced).
I'm proposing to reverse that. There's no point in having those branches,
since after the code is tagged and released. There will never be any change to
the code
