Announcing General Availability of Gitlab CI for Linux, FreeBSD and Android
Ben Cooksley
bcooksley at kde.org
Tue Nov 30 06:53:58 GMT 2021
On Tue, Nov 30, 2021 at 7:31 PM Tobias Leupold <tl at l3u.de> wrote:
> Am Dienstag, 30. November 2021, 06:31:05 CET schrieb Ben Cooksley:
> > On Tue, Nov 30, 2021 at 8:21 AM Tobias Leupold <tl at l3u.de> wrote:
> > > Am Montag, 29. November 2021, 17:25:14 CET schrieb Ben Cooksley:
> > > > @same should only be used when the other project is part of the same
> > > > release unit.
> > > > While this works for the moment because all of the involved projects
> > >
> > > have a
> > >
> > > > 'master' branch, when you go and tag/branch a stable release it will
> > >
> > > fail -
> > >
> > > > as your branch/tag names will be different.
> > > >
> > > > The correct fix in this case is to update
> > >
> > >
> https://invent.kde.org/sysadmin/repo-metadata/-/blob/master/branch-rules.y
> > > ml>
> > > > with the appropriate details for '@latest' and '@stable' for both
> marble
> > > > and libkexiv2.
> > > >
> > > > Cheers,
> > > > Ben
> > >
> > > Which versions are "latest" and/or "stable" is something the libkexiv2
> and
> > > Marble guys would have to decide or set, yes? Like "stable" could be
> the
> > > version released with Debian stable or so, and "latest" the latest
> > > released
> > > version? Or master?
> >
> > Generally I would expect @latest to correspond to the current development
> > branch for Qt 5 yes.
> > Likewise, @stable should correspond to the most current stable branch for
> > Qt 5.
> >
> > Due to the way the system works it is flexible and allows us to introduce
> > additional @ tags as needed - such as @latest-qt6 or @lts if they are
> > needed in the future.
> >
> > Cheers,
> > Ben
>
> Okay! But I can't push some change to this file only because I want to use
> a
> library as a dependency, right? This is up to the maintainers?
>
The file should be considered as community maintained - so if information
is missing or outdated then please add/correct it as needed.
There is certainly no policy that only maintainers can update the file.
Cheers,
Ben
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-devel/attachments/20211130/117e61e1/attachment.htm>
More information about the kde-devel
mailing list