On 23/11/10 17:05, Selbak, Rolla N wrote:
Hey all,
A lot of questions arise when submitting your code for inclusion into MeeGo OBS.
"What should I put in my changelog? Where should I submit from? Why was my
submission rejected?"
Here is a Developer Submission Checklist that one can use to check-off items
before a submittal.
It's simple, easy to read, and hopefully helpful.
http://wiki.meego.com/Release_Engineering/Submission_Checklist
Thanks Rolla
Since I hope that we can do a lot of early-rejection without wasting maintainer
time I'm trying to link automated policy checks back to the docs that talk about
them - this means that an automated rejection message can politely point to a
clear policy statement.
So it would be nice to find a way to link checks back to these statements.
Equally it would be nice to link the statements to the code that verifies them
so we can ensure coverage.
Please follow this check-list carefully before submission, and it will ensure
smooth acceptance into MeeGo.
On the "Changelog must refer to a feature # or bug #" I wonder if you should
define the mention of a feature# means "contributes to feature#" rather than
"implements (and closes) feature#".
David
--
"Don't worry, you'll be fine; I saw it work in a cartoon once..."
_______________________________________________
MeeGo-packaging mailing list
[email protected]
http://lists.meego.com/listinfo/meego-packaging
