2010/11/9 Zhu, Peter J <[email protected]>: > Now it's enforced that each sr has to have a bug/feature number mapped, see > http://wiki.meego.com/Release_Engineering/Process#Package_quality_expectations_for_submissions_into_.2A:Testing_projects > > Peter
Mostly a philosophical discussion, would it be possible to elaborate a bit on the rule of requiring a BMC/FEA# for package upgrades? My thought is that we're risking ourselves turning into Maemo, where packages were ancient and beyond repair - as well as if we don't follow upstream, we'll lose our ability to perform upstream-first properly as we can't easily drag in new versions. It'd be good to have some kind of upstream tracking service so we can see when things drift. I'm not saying the rule is bad, but it does need some elaboration and procedures around it so we don't lose our abilities/flexibility. BR Carsten Munk _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
