Community
Participate
Working Groups
- Create project tools.sequoyah and mark as Active in Foundation Database - Move SVN: http://dev.eclipse.org/svnroot/dsdp/org.eclipse.sequoyah/ to http://dev.eclipse.org/svnroot/tools/org.eclipse.sequoyah/ - Move Bugzilla Product: DSDP/Sequoyah to Tools/Sequoyah - Move IPZilla Product: dsdp/dsdp.sequoyah to tools/dsdp.sequoyah - Move existing committers: -- Eric Cloninger -- Daniel Drigo Pastore -- Marcel Gorri -- Doug Schaefer -- Daniel Barboza Franco -- David Dubrow - Mark dsdp.sequoyah project as inactive in Foundation Database
Entry tools.sequoyah has been created in the Foundation database.
All Sequoyah IPzilla CQs have now been moved to Tools.Sequoyah from DSDP. Webmaster: All committer legal records have been checked and there are no barriers to prevent committers from being moved as well to Tools.Sequoyah. Thanks, Sharon (IP)
When is a good time for this move? -M.
(In reply to comment #3) From Sequoyah side, it can occur anytime now (since SR1 has already been released). > When is a good time for this move? > > -M.
(In reply to comment #4) This bug is to track required actions and progress: - inform/get in touch with Tools PMC - move build from /dsdp/sequoyah to /sequoyah - change feature text and icons in SVN to remove DSDP reference - check product/component in ipzilla - change bugzilla classification - has implications on queries in websites - check projectid? Has implications on projectplanurl etc - change SVN from dev.eclipse.org/svnroot/dsdp/org.eclipse.sequoyah to dev.eclipse.org/svnroot/org.eclipse.sequoyah All, are we correct in the assumptions we made in the items above? (e.g. build and SVN addresses) > (In reply to comment #3) > From Sequoyah side, it can occur anytime now (since SR1 has already been > released). > > > When is a good time for this move? > > > > -M.
We also need to modify whatever feeds the portal because when I log into portal to handle admin needs, I still see dsdp.sequoyah. Would that be tools.sequoyah or just sequoyah?
*** Bug 330655 has been marked as a duplicate of this bug. ***
(In reply to comment #6) > We also need to modify whatever feeds the portal because when I log into portal > to handle admin needs, I still see dsdp.sequoyah. Would that be tools.sequoyah > or just sequoyah? Right now, there are no committers or project leads on the project; so nobody has authority to make changes in the portal. That will be fixed after we move the committers over. It will happen as a matter of due course.
dsdp.sequoyah will disappear at the end of this process. For now, we'd like to keep it alive until the move is completed.
> All, are we correct in the assumptions we made in the items above? (e.g. build > and SVN addresses) As long as 'above' refers to your initial post then yes I think we're fine. -M.
(In reply to comment #10) Hi Matt, just to have everybody aligned, I'm writing here an updated list (now with numbered items) so we can avoid any possible misunderstanding about what should be done. This bug is to track required actions and progress: 1 - Create project tools.sequoyah and mark as Active in Foundation Database 2 - Move SVN: http://dev.eclipse.org/svnroot/dsdp/org.eclipse.sequoyah/ to http://dev.eclipse.org/svnroot/tools/org.eclipse.sequoyah/ 3 - Change feature text and icons in SVN to remove DSDP reference 4 - Move build from /dsdp/sequoyah to /sequoyah 5 - Move Bugzilla Product: DSDP/Sequoyah to Tools/Sequoyah 6 - Move IPZilla Product: dsdp/dsdp.sequoyah to tools/sequoyah 7 - check projectid? Has implications on projectplanurl etc 8 - Move existing committers: -- Eric Cloninger -- Daniel Drigo Pastore -- Marcel Gorri -- Doug Schaefer -- Daniel Barboza Franco -- David Dubrow 9 - Mark dsdp.sequoyah project as inactive in Foundation Database > > All, are we correct in the assumptions we made in the items above? (e.g. build > > and SVN addresses) > > As long as 'above' refers to your initial post then yes I think we're fine. > > -M.
(In reply to comment #11) That looks about right to me. Wayne do you see anything missing? -M.
(In reply to comment #12) > (In reply to comment #11) > > That looks about right to me. Wayne do you see anything missing? > > -M. I see nothing missing at this point.
Ok, so where are we with scheduling this move? -M.
I'd like to do this move(unless the project objects) Monday Feb 21st. -M.
Matt, Feb 21 is fine with us. The timing is good as we have the Helios SR2 packages completed, pending some emergency. There will be some path changes and a million little details to get this done by Indigo, so it's best to start earlier rather than later.
Ok, here's where we stand: 1) I've moved the SVN repo to svnroot/tools/org.eclipse.sequoyah, and marked the dsdp copy as read only. In a few months I'll remove the old repo. 2) All the IPzillas have been moved 3) Ditto for Bugzilla. 4) Committers have been moved in the DB, and the old project is now marked 'inactive' 5) I've moved the build areas under dsdp/ in /shared and /shared/download-staging.priv into the tools/ container. 6) I've updated the project info 'keys' so they should now show the dsdp.seqouyah data for tools.sequoyah. The project will need to make sure the data is up to date. I think that's it. It will take a while for the changes to Apache and ViewVC to propagate(~12-24h). I'll close this bug, but please let me know if something isn't quite right. -M.
Good morning, guys! (In reply to comment #17) > Ok, here's where we stand: > > 1) I've moved the SVN repo to svnroot/tools/org.eclipse.sequoyah, and marked > the dsdp copy as read only. In a few months I'll remove the old repo. We are having some issues on this subject: - We cannot checkout using http, neither from svnroot/dsdp/org.eclipse.sequoyah nor from svnroot/tools/org.eclipse.sequoyah; - We can access the repository using svn+ssh; - On the build scripts we use the internal access, and it is ok; I believe it should be only a matter of setting one forgotten bit or another... > 2) All the IPzillas have been moved > 3) Ditto for Bugzilla. > 4) Committers have been moved in the DB, and the old project is now marked > 'inactive' > 5) I've moved the build areas under dsdp/ in /shared and > /shared/download-staging.priv into the tools/ container. I have started a build and this seems to be ok too; > 6) I've updated the project info 'keys' so they should now show the > dsdp.seqouyah data for tools.sequoyah. The project will need to make sure the > data is up to date. > > I think that's it. It will take a while for the changes to Apache and ViewVC to > propagate(~12-24h). > > I'll close this bug, but please let me know if something isn't quite right. > > -M. We are still checking the other migrated parts. Thanks, Daniel Pastore
(In reply to comment #18) > Good morning, guys! > > I believe it should be only a matter of setting one forgotten bit or another... The Apache process needed to be restarted. Http should be fine now. -M.
(In reply to comment #19) Hi guys, we checked here and it seems we are good to go. All items have been updated regarding the move (SVN, bugzila, IPLog, web site, wiki, blog). Is there anything else we need to do? > (In reply to comment #18) > > Good morning, guys! > > > > > I believe it should be only a matter of setting one forgotten bit or another... > > The Apache process needed to be restarted. Http should be fine now. > > -M.
I don't think so. -M.
(In reply to comment #21) Ok, so I'm closing this bug. We can reopen it if anything else is needed. Thanks, Marcel > I don't think so. > > -M.
