Community
Participate
Working Groups
I'll use this bug to track the 0.7.0 release. On what date would you like to release? Note that we need at least a week of community review prior to the release. Reviews run from Thursday to Wednesday.
Hi, We would like to release the 06/26/2013 and performing a release review the 06/05/2013. Thanks! (In reply to comment #0) > I'll use this bug to track the 0.7.0 release. > > On what date would you like to release? Note that we need at least a week of > community review prior to the release. Reviews run from Thursday to > Wednesday.
Please take a look at the review checklist to make sure that you have all the necessary pieces in place: http://wiki.eclipse.org/Development_Resources/HOWTO/Release_Reviews#Checklist I can schedule the review as soon as you provide review materials. Note that you can specify the review information directly in the release record: https://projects.eclipse.org/projects/modeling.mdt.sphinx/releases/0.7.0
Created attachment 229769 [details] Approved IP Log
I've made this a blocker on Kepler (bug 406441) and the modeling restructuring (bug 393682). Per bug 393682, Sphinx needs to move out of mdt and into the top-level project's root. For Sphinx, I think that this is little more than an id change. * the project website is already in the root. * project downloads are already in the root. * The bugzilla product should probably change from "MDT.Sphinx" to "Sphinx" Am I missing anything?
(In reply to comment #4) > I've made this a blocker on Kepler (bug 406441) and the modeling > restructuring (bug 393682). We are ok with moving Sphinx out of MDT. > Per bug 393682, Sphinx needs to move out of mdt and into the top-level > project's root. For Sphinx, I think that this is little more than an id > change. Which ids do you mean exactly? My understanding is that the plug-in ids can remain as is: org.ecipse.sphinx.*. Is this correct? > * the project website is already in the root. > * project downloads are already in the root. > * The bugzilla product should probably change from "MDT.Sphinx" to "Sphinx" +1 > Am I missing anything? The developer mailing list which currently is mdt-sphinx.dev needs probably also to be renamed. Aside from that the name "mdt" currently still appears in names of our Hudson build jobs (e.g., mdt-sphinx-0.7-kepler) and the downloads produced by it (e.g., mdt-sphinx-Update-0.7.0RC1.zip). We can care for renaming both of them but we are wondering if there is any convention to follow. Given that the forum is named "eclipse.sphinx" and the provider names in the plugin.properties files also have been changed to "Eclipse Sphinx", I would tend to Hudson build job name: eclipse-sphinx-0.7-kepler Download archive name: eclipse-sphinx-Update-0.7RC1.zip What do you think?
(In reply to comment #5) > Which ids do you mean exactly? My understanding is that the plug-in ids can > remain as is: org.ecipse.sphinx.*. Is this correct? I should have been more clear. This is the id that we use internally. It's used on pages like: http://projects.eclipse.org/projects/modeling.mdt.sphinx > The developer mailing list which currently is mdt-sphinx.dev needs probably > also to be renamed. I don't think renaming mailing lists is possible. We'll have to ask Webmaster. > Aside from that the name "mdt" currently still appears in names of our > Hudson build jobs (e.g., mdt-sphinx-0.7-kepler) and the downloads produced > by it (e.g., mdt-sphinx-Update-0.7.0RC1.zip). We can care for renaming both > of them but we are wondering if there is any convention to follow. Given > that the forum is named "eclipse.sphinx" and the provider names in the > plugin.properties files also have been changed to "Eclipse Sphinx", I would > tend to Webmaster knows the conventions. We can ask him to help normalize the names. > Hudson build job name: eclipse-sphinx-0.7-kepler > Download archive name: eclipse-sphinx-Update-0.7RC1.zip > > What do you think? I think it sounds like we have the rudiments of a plan.
Created attachment 232003 [details] Review documentation
PMC Approval: http://dev.eclipse.org/mhonarc/lists/modeling-pmc/msg02859.html
I declare this review successful! Please continue with your release.
My apologies. I closed this bug too quickly. The declaration of success still stands. There is still, however, the matter of completing the restructuring started in Bug 393682. Please assemble a list of action items to complete the move of this project. There are a few projects that need to move, so let's wait until we have all/most of them ready to go before we copy the webmaster and ask him to effect the changes all at once.
This bug is no longer a blocker for Kepler.
(In reply to comment #10) > Please assemble a list of action items to complete the move of this project. Ok, here is the action item list: * Change internal project id from "modeling.mdt.sphinx" to "modeling.sphinx" * Change bugzilla product from "MDT.Sphinx" to "Sphinx" * If possible, rename developer mailing from "mdt-sphinx.dev" to "modeling-sphinx.dev" (or something more appropriate if there is any specific convention to follow) * Rename Hudson build job names from "mdt-sphinx-0.7-<release name>" to "sphinx-0.7-<relase name>" (or something more appropriate if there is any specific convention to follow) * Rename Download archive names from "mdt-sphinx-Update-0.7xxx.zip" to "eclipse-sphinx-Update-0.7xxx.zip" (or something more appropriate if there is any specific convention to follow)
There is one more thing to be done: * Rename mdt-sphinx-inbox@eclipse.org used as default assignee in Bugzilla to modeling-sphinx-inbox@eclipse.org (or something more appropriate if there is any specific convention to follow)
(In reply to comment #12) > * If possible, rename developer mailing from "mdt-sphinx.dev" to > "modeling-sphinx.dev" (or something more appropriate if there is any specific > convention to follow) Renaming mailing lists is not possible. We can either continue with the existing list, or ask that the webmaster archive the old one and create a new one. What do you want to do? > * Rename Download archive names from "mdt-sphinx-Update-0.7xxx.zip" to > "eclipse-sphinx-Update-0.7xxx.zip" (or something more appropriate if there is > any specific convention to follow) You can do this. Let's keep the action item list to only those things that we need the Webmaster's help to implement. We'll need to add changing the IPZilla component to the list before we send it to the Webmaster.
(In reply to comment #14) > (In reply to comment #12) > > * If possible, rename developer mailing from "mdt-sphinx.dev" to > > "modeling-sphinx.dev" (or something more appropriate if there is any specific > > convention to follow) > > Renaming mailing lists is not possible. We can either continue with the > existing list, or ask that the webmaster archive the old one and create a > new one. What do you want to do? We'd like to get the old developer mailing list archive and a new one with the appropriate name to be created. > > * Rename Download archive names from "mdt-sphinx-Update-0.7xxx.zip" to > > "eclipse-sphinx-Update-0.7xxx.zip" (or something more appropriate if there is > > any specific convention to follow) > > You can do this. Let's keep the action item list to only those things that > we need the Webmaster's help to implement. > > We'll need to add changing the IPZilla component to the list before we send > it to the Webmaster. A complete action item list follows in the next comment.
The action item list for the webmaster: * Change internal project id from "modeling.mdt.sphinx" to "modeling.sphinx" * Change bugzilla product from "MDT.Sphinx" to "Sphinx" * Change IPZilla component from existing name to "Sphinx" (or something more appropriate if there is any specific convention to follow) * Archive existing developer mailing list "mdt-sphinx.dev" and create a new one called "modeling-sphinx.dev" (or something more appropriate if there is any specific convention to follow) * Rename Download archive names from "mdt-sphinx-Update-0.7xxx.zip" to "eclipse-sphinx-Update-0.7xxx.zip" (or something more appropriate if there is any specific convention to follow)
Webmaster, can you please coordinate with the project to implement these changes? (In reply to comment #16) > The action item list for the webmaster: > * Change internal project id from "modeling.mdt.sphinx" to "modeling.sphinx" > * Change bugzilla product from "MDT.Sphinx" to "Sphinx" > * Change IPZilla component from existing name to "Sphinx" (or something more > appropriate if there is any specific convention to follow) > * Archive existing developer mailing list "mdt-sphinx.dev" and create a new one > called "modeling-sphinx.dev" (or something more appropriate if there is any > specific convention to follow) > * Rename Download archive names from "mdt-sphinx-Update-0.7xxx.zip" to > "eclipse-sphinx-Update-0.7xxx.zip" (or something more appropriate if there is > any specific convention to follow)
Stephan/Idrissa is there a time that's best for your project or can I do this 'whenever'? -M.
Hi, you can perform these changes at any time! (In reply to comment #18) > Stephan/Idrissa is there a time that's best for your project or can I do > this 'whenever'? > > -M.
Ok, I've updated the projectid, Bugzilla, IPzilla and created a new mailing list(and scheduled the old one for closure). The file names in the downloads directory have been pruned of the leading 'mdt-'. -M.
(In reply to comment #20) > Ok, I've updated the projectid, Bugzilla, IPzilla and created a new mailing > list(and scheduled the old one for closure). The file names in the > downloads directory have been pruned of the leading 'mdt-'. > > -M. I've updated the PMI. The following URLs point to the same record: https://projects.eclipse.org/projects/modeling.mdt.sphinx https://projects.eclipse.org/projects/modeling.sphinx
I recently got aware of the following additional things, that we had failed to identify earlier, but still should be addressed: 1) Default assignee on Sphinx Bugzilla: Actual: mdt-sphinx-inbox@eclipse.org Expected: sphinx-inbox@eclipse.org 2) Git repo URL: Actual: git://git.eclipse.org/gitroot/mdt/org.eclipse.sphinx.git Expected: git://git.eclipse.org/gitroot/sphinx/org.eclipse.sphinx.git
Webmaster, the modeling.sphinx is currently a level 3 project; that needs to be changed to level 2. Also, can you make these changes (in coordination with Stephan, of course)? (In reply to comment #22) > I recently got aware of the following additional things, that we had failed to > identify earlier, but still should be addressed: > > 1) Default assignee on Sphinx Bugzilla: > Actual: mdt-sphinx-inbox@eclipse.org > Expected: sphinx-inbox@eclipse.org > > 2) Git repo URL: > Actual: git://git.eclipse.org/gitroot/mdt/org.eclipse.sphinx.git > Expected: git://git.eclipse.org/gitroot/sphinx/org.eclipse.sphinx.git
(In reply to Wayne Beaton from comment #23) > Webmaster, the modeling.sphinx is currently a level 3 project; that needs to > be changed to level 2. Why should this happen? We are consuming other projects that are level 2, e.g., Xpand, and therefore I always thought that level 3 should be fine for Sphinx.
(In reply to Stephan Eberle from comment #24) > Why should this happen? We are consuming other projects that are level 2, > e.g., Xpand, and therefore I always thought that level 3 should be fine for > Sphinx. This is an internal database thing; it has nothing to do with the simultaneous release or how you consume other projects. e.g. "modeling" is level one, "modeling.sphinx" is level two, "modeling.tmf.xtext" is level three.
(In reply to Wayne Beaton from comment #25) > (In reply to Stephan Eberle from comment #24) > > Why should this happen? We are consuming other projects that are level 2, > > e.g., Xpand, and therefore I always thought that level 3 should be fine for > > Sphinx. > > This is an internal database thing; it has nothing to do with the > simultaneous release or how you consume other projects. e.g. "modeling" is > level one, "modeling.sphinx" is level two, "modeling.tmf.xtext" is level > three. Ok, I got it, thanks. I was confusing that with the +1, +2, +3 project build offsets :D
(In reply to Wayne Beaton from comment #23) I've updated the sphinx 'level'. > > 1) Default assignee on Sphinx Bugzilla: > > Actual: mdt-sphinx-inbox@eclipse.org > > Expected: sphinx-inbox@eclipse.org This is done(since it doesn't require users to update their watch list). > > 2) Git repo URL: > > Actual: git://git.eclipse.org/gitroot/mdt/org.eclipse.sphinx.git > > Expected: git://git.eclipse.org/gitroot/sphinx/org.eclipse.sphinx.git Stephan: When is a good time for me to make this happen? It should only take a few minutes. -M.
(In reply to Eclipse Webmaster from comment #27) > (In reply to Wayne Beaton from comment #23) > > > 2) Git repo URL: > > > Actual: git://git.eclipse.org/gitroot/mdt/org.eclipse.sphinx.git > > > Expected: git://git.eclipse.org/gitroot/sphinx/org.eclipse.sphinx.git > > Stephan: When is a good time for me to make this happen? It should only > take a few minutes. As we have got our Luna M7 build out of the door two days ago, there is currently no committer who has uncommitted changes and we could and should proceed to the Git repo URL change right now. Thanks.
Ok, I've moved /gitroot/mdt/org.eclipse.sphinx.git to /gitroot/sphinx/org.eclipse.sphinx.git. if you change your URL you should be all set. -M.
Are we done?
(In reply to Wayne Beaton from comment #30) > Are we done? I'd say that we are :)
Alrighty then.
I actually found one thing that has escaped our eyes: The IP log generator tool [1]. In the case of Sphinx it still points at the old Git repo URL [2]. [1] https://www.eclipse.org/projects/ip_log.php?projectid=modeling.sphinx [2] /gitroot/mdt/org.eclipse.sphinx.git Could you fix that please, so that we can engage for the Sphinx 0.8.0 release review? Thanks.
(In reply to Stephan Eberle from comment #33) > I actually found one thing that has escaped our eyes: The IP log generator > tool [1]. In the case of Sphinx it still points at the old Git repo URL [2]. > > [1] https://www.eclipse.org/projects/ip_log.php?projectid=modeling.sphinx > [2] /gitroot/mdt/org.eclipse.sphinx.git > > Could you fix that please, so that we can engage for the Sphinx 0.8.0 > release review? > > Thanks. The IP Log generator uses the information specified in the PMI. https://projects.eclipse.org/projects/modeling.mdt.sphinx/developer Fix it yourself ;-)
(In reply to Wayne Beaton from comment #34) > Fix it yourself ;-) FWIW, I was trying to be jovial, not mean. It looks like you've made the fix.
(In reply to Wayne Beaton from comment #35) > (In reply to Wayne Beaton from comment #34) > > Fix it yourself ;-) > > FWIW, I was trying to be jovial, not mean. No worries, I did understand it as you meant it... > It looks like you've made the fix. ... but then forgot about to resolve this bug again ;)
