Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 319283

Summary:	gemini component versions in bugzilla
Product:	Community	Reporter:	Glyn Normington <glyn.normington>
Component:	Bugzilla	Assignee:	Eclipse Webmaster <webmaster>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	michael.keith
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Mac OS X - Carbon (unsup.)
Whiteboard:

Description Glyn Normington

2010-07-08 12:05:19 EDT

The gemini components currently share a bugzilla product which appears to have a single set of versions and target milestones. We actually need to be able to version the gemini components independently of each other.

I don't know what flexibility there is in bugzilla to enable that or whether we need to overhaul the gemini bugzilla structure to make each gemini component a 'product'.

Any advice gratefully received!

Comment 1 Eclipse Webmaster

2010-07-08 13:27:14 EDT

Each component will need to be a 'product' if they need to have individual versions/milestones.

-M.

Comment 2 Glyn Normington

2010-07-08 14:22:01 EDT

We discussed this on today's Gemini call and there was a consensus, confirmed by Mike Keith the gemini lead (copied) that gemini components do need to be independently versioned. So please could you massage bugzilla suitably? Thanks.

Comment 3 Michael Keith

2010-07-08 14:31:35 EDT

It has always been a requirement that the Gemini subprojects be versioned separately. Unfortunately, when the PMC suggested they be merged into one product and become different components in the same product we were not aware that this would be taken away :(  

We will bring this up in the PMC before we ask you to go undoing the work that you just recently put into merging them. Very sorry for this confusion!

Comment 4 Michael Keith

2010-07-12 10:00:57 EDT

> We will bring this up in the PMC before we ask you to go undoing the work that
> you just recently put into merging them. Very sorry for this confusion!

There doesn't seem to be any viable alternative. I guess we have to go back to the  way it was before. Again, sorry about this.

Comment 5 Eclipse Webmaster

2010-07-12 10:59:15 EDT

I've created the products, and an initial component in each called 'Core'. If that's ok, I'd like to move the bugs associated with the JPA,Naming and Web components of Gemini to their respective products.

BTW will we need to keep the Gemini 'top' level product?

-M.

Comment 6 Glyn Normington

2010-07-12 11:15:51 EDT

(In reply to comment #5)
> I've created the products, and an initial component in each called 'Core'. If
> that's ok, I'd like to move the bugs associated with the JPA,Naming and Web
> components of Gemini to their respective products.
> 
> BTW will we need to keep the Gemini 'top' level product?
> 
> -M.

Please go ahead and move the Web component bugs.

Thanks for sorting this out!

Glyn

Comment 7 Eclipse Webmaster

2010-07-12 11:21:46 EDT

The web bugs have been moved and I've removed the component from Gemini.

-M.

Comment 8 Glyn Normington

2010-07-12 11:59:36 EDT

(In reply to comment #7)
> The web bugs have been moved and I've removed the component from Gemini.
> 
> -M.

Looks good. I can now create Gemini Web milestones! :-)

Thanks,
Glyn

Comment 9 Michael Keith

2010-07-12 12:03:21 EDT

(In reply to comment #5)
> I've created the products, and an initial component in each called 'Core'. If
> that's ok, I'd like to move the bugs associated with the JPA,Naming and Web
> components of Gemini to their respective products.
> 
> BTW will we need to keep the Gemini 'top' level product?
> 
> -M.

Yes, and the Gemini Demos component should remain in the Gemini product.

Thanks.

Comment 10 Denis Roy

2011-03-10 14:58:06 EST

Looks like we're done here.