> -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Anas Nashif > Sent: Monday, April 11, 2011 4:32 PM > To: [email protected] list) > Subject: [meego-packaging] devel: project process > > Hi, > There is a need to clarify the devel: project process and how changes should > be > done to packages in those projects. From the traffic on meego-commits it is > evident that there is some misunderstanding in how those project are > managed and there seems to be a misunderstanding on the purpose of the > devel projects. > > - devel:* project are team development area, where a group of people can > work on related packages and verify their changes against others before > submitting > - Additionally, a team can chose to add dependent packages that are not > directly maintained in the devel project, but serves for testing API changes > etc. > - Usually, if a package is maintained in a devel project, changes by > maintainers should happen inside that project, and not using a branch. This > mean that if you are the maintainer and need to make a change, you do not > have to branch the package and submit it, this should be done only in some > special cases. Even maintain could make mistake. So it's better for maintainer to branch and submit to devel as well. So that changes by maintainers could be reviewed by the world as well before it bothers going to T:T.
> - Only submissions to devel: project should come from contributors, not > maintainers. > - We often see a change being submitted to a devel project, then minutes later > the accepted change is forwarded to Trunk:Testing, probably skipping any value > that a devel project would provide (compile against other packages in the same > devel project, install all related components and verify the change, etc.). > That's some issues seen mostly often. Maintainers really should make sure all packages in devel builds well and runs well, for changes made in devel. Peter > So please if you are a maintainer of the devel project, try to manage the > changes directly in the devel project, by checking out the packages directly > and > making the changes directly to the packages in the project and after > verification submit to Trunk:Testing. If you are a contributor you should > still > submit the change to the devel project as usual. > > If you have comments, please let us know. > > Anas > _______________________________________________ > 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
