Bug 379552

Comment 1 Wayne Beaton 2012-05-15 10:15:53 EDT

Created attachment 215644 [details]
Review documentation

Comment 2 Wayne Beaton 2012-06-12 10:37:47 EDT

What is the status of this release/graduation? Are you ready to schedule a release?

Note that the project currently has no releases indicated in the project metadata. Please make a habit of providing this information.

Comment 3 Wayne Beaton 2012-08-30 12:24:46 EDT

Created attachment 220522 [details]
Review documentation

Comment 4 Wayne Beaton 2012-08-30 16:02:42 EDT

Created attachment 220535 [details]
Approved IP Log

Comment 5 Wayne Beaton 2012-08-30 16:05:02 EDT

I believe that all of the necessary pieces are in place. I've scheduled the review to conclude on September 5/2012.

Comment 6 Wayne Beaton 2012-08-30 16:15:03 EDT

Note that Epsilon will move out of EMFT to directly under Modeling with this release.

Comment 7 Wayne Beaton 2012-09-05 09:57:44 EDT

Review is successful. Please continue with your release.

The project has been marked as "regular" (i.e. mature) in the database.

Comment 8 Dimitris Kolovos 2012-11-07 10:33:06 EST

To complete the move from EMFT->Modeling, the following actions should also take place (copied from the penultimate slide of the review documentation):

- Change bugzilla product from EMFT.Epsilon to Modeling.Epsilon (or just Epsilon)
- Change project ID from modeling.emft.epsilon to modeling.epsilon (or just epsilon)
- Move all 3 committers to the new project

It'd be great if we could also have a dev mailing list for the project.

Comment 9 Wayne Beaton 2012-11-21 15:42:57 EST

We have a few things that need to be done to complete this move.

Change the project id from modeling.emft.epsilon to modeling.epsilon
- In the Foundation and portal databases (including committer/PL records)
- In IPZilla

Move the project's bugzilla records from EMFT.Epsilon to Epsilon (can we just change the name of the Bugzilla product?)

The project's download directory does not require modification

(In reply to comment #8)
> It'd be great if we could also have a dev mailing list for the project.

The mailing list exists.

Comment 10 Wayne Beaton 2013-04-23 12:07:02 EDT

This clearly slipped through the cracks. Are you ready to make the changes?

I think that the only thing that will affect you is the Bugzilla change. 

Can we do this sometime this week?

Comment 11 Dimitris Kolovos 2013-04-25 05:18:45 EDT

This week should be fine. It'd be great if we could also add a rewrite rule so that we don't break all links from forum posts to bug reports when the Bugzilla id changes.

(In reply to comment #10)
> This clearly slipped through the cracks. Are you ready to make the changes?
> 
> I think that the only thing that will affect you is the Bugzilla change. 
> 
> Can we do this sometime this week?

Comment 12 Eclipse Webmaster 2013-05-01 09:34:43 EDT

Sorry this got pushed out.  Is today ok?

The Bugzilla links(ie:  https://bugs.eclipse.org/bugs/show_bug.cgi?id=406195) should be fine since the bug numbers wont change.  

-M.

Comment 13 Dimitris Kolovos 2013-05-01 11:09:36 EDT

No worries. Today is fine.

Comment 14 Eclipse Webmaster 2013-05-02 11:15:07 EDT

Ok I've renamed 'modeling.emft.epsilon' to 'modeling.epsilon' in our back end DB,bugzilla,ipzilla and the portal db. 

-M.

Comment 15 Wayne Beaton 2013-05-02 12:03:31 EDT

(In reply to comment #14)
> Ok I've renamed 'modeling.emft.epsilon' to 'modeling.epsilon' in our back
> end DB,bugzilla,ipzilla and the portal db. 
> 
> -M.

The parent project needs to be set to modeling as well.

Comment 16 Eclipse Webmaster 2013-05-02 13:05:13 EDT

D'oh.  Fixed.

-M.

Comment 17 Wayne Beaton 2013-06-05 15:52:13 EDT

I  think we're done here.