There is a helpful submission checklist for developers and submitters here:
http://wiki.meego.com/Release_Engineering/Submission_Checklist And this submission checklist is actually also referred to in the Process wiki you have below: http://wiki.meego.com/Release_Engineering/Process#Step_3:_Developer_Submission_Check-list So to answer your q, you're right, the SR# bug comment is not necessary right now, but a nice-to-have for ease of tracking. The one thing you are required to do is make sure the bug or feature you are requesting is set to 'resolved', which indicates that the code is submitted. Then once it hits MeeGo Trunk, Release Engineers will set the bug to 'released', or if the submisison is rejected, they will set the bug to 'reopened'. Hope this clarifies things a bit... rs On 12/3/10 7:27 AM, "Luis Araujo" <[email protected]> wrote: I am guessing this would help to speed things up with bug assigning and all, but It'd be nice if someone could clarify this. Regards, On 12/03/2010 09:51 AM, Senko Rasic wrote: > Hi, > > when submitting a request for package for Trunk:Testing, we're > supposed to reference a bug or feature explaining it. > > Now, the unofficial practice I see (and follow) is to also specify the > generated SR# in the bug comments, for easier tracking. > > But AFAICS, this is not mandated (or at least not written up in the > wiki at > http://wiki.meego.com/Release_Engineering/Process#Package_quality_expectations_for_submissions_into_.2A:Testing_projects > > > Should we do this (in which case the wiki needs update), or is this > unneccessary? > > Thanks, > Senko > _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
