On Thu, 9 Dec 2021 at 18:05, Richard Purdie <
[email protected]> wrote:
> On Thu, 2021-12-09 at 15:48 +0100, Konrad Weihmann wrote:
> > I support that idea.
> >
> > as said in the other ML conversation the format should look like
> >
> > Upstream-Status: Inactive-Upstream [<last release date>(, <last commit
> > date>)]
> >
> > with the part in the ()-brackets being opinion, as we mainly aim for
> > using releases anyway.
> > This time I would actually have it as much machine readable as possible,
> > so it might be suitable to dictate a yyyymmdd date format pattern here.
>
> I'm in favour of adding the new category and I agree some kind of dates in
> the
> [reason] space would be nice to have.
>
> For the purposes of a patch upstream, the last commit date is much more
> important than a release. I don't think this needs to be machine readable
> as a
> definition, it is better we have the appropriate info. Year is probably as
> much
> as we need since inactive software is usually measured in years.
>
> We may need to put some kind of guide in the docs about what "inactive"
> looks
> like.
>
I added the following to the wiki:
'''Inactive-Upstream [lastcommit: when (and/or) lastrelease: when]'''
- The upstream is no longer available. This typically means a defunct
project
where no activity has happened for a long time - measured in years. To
make
that judgement, it is recommended to look at not only when the last
release
happened, but also when the last commit happened, and whether newly
made bug
reports and merge requests since that time receive no reaction. It is
also
recommended to add any relevant links to the commit message where the
inactivity
can be clearly seen.
https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines#Patch_Header_Recommendations:_Upstream-Status
Alex
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#1391):
https://lists.openembedded.org/g/openembedded-architecture/message/1391
Mute This Topic: https://lists.openembedded.org/mt/87612566/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-architecture/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
