Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [eclipselink-dev] Incubation component minutes

I believe Tom's topics listed below should be clearly addressed in the Wiki page each incubation project/component maintains.

I also believe that these should incubate within trunk. It will be up to each owner to manage the state of the incubation effort when we branch. In general I would see these as remaining in trunk until they mature into the main code line.

Doug

-----Original Message-----
From: Tom Ware 
Sent: Wednesday, December 03, 2008 4:16 PM
To: Dev mailing list for Eclipse Persistence Services
Subject: Re: [eclipselink-dev] Incubation componant minutes


We also need to identify what information should be provided for each incubation 
component. (perhaps in a readme)

- What version does it work with
- Any build instructions
- Any usage documentations
- Other things?

Peter Krogh wrote:
> During todays call we discusses the incubation idea, proposed by Doug, at length.
> 
> Some discussion points arose.
> 
> Incubation Componant
> 	Should the incubation directory be under trunk or parrallel to trunk?
> 	How to handle 3rd party dependancies?
> 		I assume that a consumer of the incubation code would need to download the dependancy themselves, as opposed to opening CQs.
> 
> Any others?
> _______________________________________________
> eclipselink-dev mailing list
> eclipselink-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/eclipselink-dev
_______________________________________________
eclipselink-dev mailing list
eclipselink-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-dev


Back to the top