This is a topic for shr-devel list, but i think we can find some help on this list :)
There were some discussens on IRC about the SHR-testing release. It was suggestet to do a roling release for SHR-testing beginning with the release of the next SHR-testing image. I'm thinking, that we should as soon as possible release the Xorg unstable image and then do a "feature freeze" or better "version freeze" in shr- unstable. Then wait one or two weeks for bug reports from the users about this image and then release the Xorg image as testing. >From that point on, i suggest to move every new package or new version to SHR- testing after a week, when there weren't any bugs in this package. And for bigger changes (e.g. EFL bump) we do a complete freeze of SHR-unstable and move it completely. But for this we need a maintainer for SHR-testing who cares about that all. This guy must have an overview over all new commits and work together with the SHR-unstable maintainers. But currently all SHR devs are using SHR-unstable and i think nobody of them would use shr-testing (because it's boring, no adventures) so we would need someone new for this position. It can be done by everyone he needs no skills in programming nor in bitbake. Just git, but that's easy. But if we do it now like that it will be really hard to move to org.oe.dev. The advantage of this is, that all users can use SHR-testing and so we can breake SHR-unstable as often as we want. We could have done Xorg things directly in SHR-unstalbe. So what do you think? What should we do next org.oe.dev merge or testing release? Is there a candidate for the SHR-testing maintainer? greets Thomas (Heinervdm) _______________________________________________ Shr-User mailing list [email protected] http://lists.shr-project.org/mailman/listinfo/shr-user
