Community
Participate
Working Groups
It appears the Portal is not updating the following DB information if the committer election is in relation to sub component access: 1. Provisioning Info 2. Project Tab (association to the applicable project/sub project) Thanks, Sharon
Sharon, Could you provide some more detail here? I'm afraid I do not understand the issue. Perhaps you're saying that when an election happens for a component of a project, something in the database is not getting updated - what is that something or somethings? Could you provide an example of an election that would have updated that something and did not? Thanks.
Certainly Bjorn. On 2008-02-28 - a NCRF was received for aniefer as a result of a successful election - Portal record election #439. The NCRF contained the following information: --------------------------------------------------------------------------- New Committer Request - Election Conducted via the Portal Name: A Niefer Email: ***** Project: eclipse.equinox Organization: **** CVS/SVN package List: equinox.p2 group Web Package List: p2.home if there is one. --------------------------------------------------------------------------- Typically the Portal would send the DB the Provisioning Info from CVS/SVN Package List (from the NCRF) and drop it in the Provisioning Info area on the Person's DB Record - this did not happen. Also, the Portal would update the Project Tab for the Person's DB record to associate them with the correct Project - in this case it failed because aniefer was an existing committer to eclipse.equinox. What I believe should have occurred since we have opened up the sub components - is that aniefer should have been associated as a committer to eclipse.equinox as well as eclipse.equinox.p2 then I believe the provisioning info would have been trasnferred. I'm guessing either the NCRF or the way the election was held needs to be updated to take this situation into account because really the committer needed access to p2 as well as equinox - the Project info on the NCRF should have been eclipse.equinox and eclipse.equinox.p2. I added him manually to p2. Hope this helps. Sharon
Thanks. This will be fixed by the big "standardized groups" bug 198541 when components become first-class and elections can happen for multiple projects and components simultaneously. It doesn't make a lot of sense (resource-wise) to put in a temporary fix.
I believe this has been resolved earlier in the spring when we moved to elections for components in the Portal. Closing, but if this is not true, Sharon, please re-open.
Closed or released for STAGING_326. Please see final comments for actual resolution status. This message does not imply that any action was taken which was not already described.
