You are viewing a plain text version of this content. The canonical link for it is here.
Posted to discuss@petri.apache.org by "sebbASF (via GitHub)" <gi...@apache.org> on 2023/09/15 13:16:38 UTC
[GitHub] [petri] sebbASF opened a new issue, #42: info.yaml is inconsistent
sebbASF opened a new issue, #42:
URL: https://github.com/apache/petri/issues/42
The info.yaml file has two lists of projects:
the 'projects' list and the 'cultures' list.
The 'projects' list is documented as 'current' Petri cultures.
It is currently empty.
However the 'cultures' list contains the buildstream culture, which has the status current.
This is inconsistent.
Is the projects list really needed as well as the status?
If so, it is vital that the two definitions of currency are kept in step.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: discuss-unsubscribe@petri.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [petri] dave2wave commented on issue #42: info.yaml is inconsistent
Posted by "dave2wave (via GitHub)" <gi...@apache.org>.
dave2wave commented on issue #42:
URL: https://github.com/apache/petri/issues/42#issuecomment-1722269792
`info.yaml` has:
```
cultures:
buildstream:
start: 2020/04/08
end: 2022/09/21
status: tlp
```
That seems correct and consistent.
I see no need to make changes at this time
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: discuss-unsubscribe@petri.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [petri] sebbASF commented on issue #42: info.yaml is inconsistent
Posted by "sebbASF (via GitHub)" <gi...@apache.org>.
sebbASF commented on issue #42:
URL: https://github.com/apache/petri/issues/42#issuecomment-1722337823
https://petri.apache.org/info.yaml was only updated yesterday:
https://github.com/apache/petri/commit/c152876de400d7c61553fa12a2199f78dd37040a
Prior to that, it was still showing buildstream as current.
But the point is that there are two different ways of indicating that a project is active (or not), and these can easily be out of step, as was the case for several months.
This does not make sense to me.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: discuss-unsubscribe@petri.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [petri] sebbASF commented on issue #42: info.yaml is inconsistent
Posted by "sebbASF (via GitHub)" <gi...@apache.org>.
sebbASF commented on issue #42:
URL: https://github.com/apache/petri/issues/42#issuecomment-1722231856
Seems to me that the projects list should be dropped (having informed the relevant users)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: discuss-unsubscribe@petri.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [petri] gstein commented on issue #42: info.yaml is inconsistent
Posted by "gstein (via GitHub)" <gi...@apache.org>.
gstein commented on issue #42:
URL: https://github.com/apache/petri/issues/42#issuecomment-1722371148
Sure. We could maybe fill web page content using info.yaml
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: discuss-unsubscribe@petri.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [petri] dave2wave closed issue #42: info.yaml is inconsistent
Posted by "dave2wave (via GitHub)" <gi...@apache.org>.
dave2wave closed issue #42: info.yaml is inconsistent
URL: https://github.com/apache/petri/issues/42
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: discuss-unsubscribe@petri.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [petri] sebbASF commented on issue #42: info.yaml is inconsistent
Posted by "sebbASF (via GitHub)" <gi...@apache.org>.
sebbASF commented on issue #42:
URL: https://github.com/apache/petri/issues/42#issuecomment-1722458675
Yes, it would be good if one could also use the file to ensure the website is self-consistent, but first one needs to ensure that the info.yaml file is self-consistent.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: discuss-unsubscribe@petri.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org