[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [equinox-dev] [prov] Participation opportunity
- From: "Jeff McAffer" <jeff@xxxxxxxxx>
- Date: Tue, 8 Apr 2008 20:36:39 -0400
- Delivered-to: firstname.lastname@example.org
- Organization: Code 9
- Thread-index: AciZy6ltl3GvP6hrQYe0Fq7lXoo+GgADTr0g
While we are all loving each other I feel obliged to say that the focus of
this call to action was (I believe) helping p2 *ship in 3.4* with a
reasonable function level. To that end it would be really useful to
distinguish between participation aimed at 3.4 and futures participation.
Futures stuff is very welcomed but needs to be called out as such so as to
not distract from the 3.4 goal.
For context, p2 needs to be function complete in 2 weeks (M7). After that
it is locking down code, fixing lingering bugs, improving robustness etc.
> -----Original Message-----
> From: equinox-dev-bounces@xxxxxxxxxxx [mailto:equinox-dev-
> bounces@xxxxxxxxxxx] On Behalf Of Scott Lewis
> Sent: Tuesday, April 08, 2008 6:55 PM
> To: Equinox development mailing list
> Subject: Re: [equinox-dev] [prov] Participation opportunity
> Hi Thomas,
> Thomas Hallgren wrote:
> > Susan Franklin McCourt wrote:
> >> I could imagine the day when
> >> - update sites, CVS repos, etc. are all using ECF
> > And while we're at it, let's not forget Subversion. Just think about
> > it. An EPL licensed SVN-client based on ECF. That certainly gives me
> > that warm and fuzzy feeling :-)
> Thomas your 'I <heart> ECF' t-shirt is in the mail ;-).
> equinox-dev mailing list