On Wed, 2014-10-29 at 13:52 +0000, Bartosh, Eduard wrote: > > This helps of course, but doesn't address the underlying problem. It's easy > > for you and me, but most developers don't even know who's currently the > > active RE(s). > > > We can setup tizen-<profile>-re@ aliases to address that I guess. Or > just put names of current RE on the wiki.
I fear that both will get stale sooner or later. I like the proposal with special tag names better. > I meant using gbs stump --tag with special timestamp like > 20014MMDD.00XX00 or similar (XX - unique developer id, assigned by > RE). > So the procedure would be the following: > - developer submits packages to the project using --tag 20014MMDD.00XXXX I think assigning unique developer IDs will be too much work in practice. We also would have to handle the case where one developer needs to create several independent group submissions. I propose that we let developers pick a free "special" tag by looking at https://panel.tizen.org/app/submissions/opened/ > - developer sends e-mail to RE asking not to touch it until further > notification (later on it can be possible to do in panel.tizen.org) Can't we skip this step? "Normal" submissions without the special .00 tag can be accepted directly and "special" ones need to be on hold right away - no explicit communication required. > - developer re-tags changes with this tag and resubmits them again and again > until project is ready for integration. All prerelease artifacts (package > repos, images, manifest, etc) are available for developer on download server. > - developer uses https://panel.tizen.org/app/submissions/mine/ to see all > info about submission > - developer notifies RE when submission is ready to be integrated (later on > it can be possible to do in panel.tizen.org) > - RE accepts submission Looks better than what we have so far, so I'm in favor of it. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
