Planning for next release (1.0.7)

[Parthasarathy G]

This is a multi-part message in MIME format.

------=_NextPartTM-000-170d75ce-3d4c-11d6-a942-00b0d0d06be8
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Hi Friends,

I am bit new to open source development. Can somebody take time to highlight
how things work in Open Source World and I would be grateful if some details
on the process used to compile and test the VM before release.

some questions that come up in mind is
- Using jikes for getting Kaffee.jar... Why??
- How do we test the VM for conformance??

I guess let me hold to my questions and see if they get resolved as we move
along.

Regards,
Partha

-------------------------------------------------------------
"Attitude Matters"
Parthasarathy G
Technology Development Center - HomeNet
Wipro Technologies, E&I
53/1 , Hosur Road, Madiwala
Phone: 91-80-5502001-008  x3130
Fax No: 5502160
Bangalore - 560 068.
Visit Home Networks Website
* Intranet: http://gruha.wipro.com
* Internet: http://www.wipro.com/homenet/
----- Original Message -----
From: "Jim Pick" <jim@kaffe.org>
To: <kaffe@rufus.w3.org>
Sent: Thursday, March 21, 2002 8:34 PM
Subject: Planning for next release (1.0.7)


>
> Hi,
>
> Sorry I've been a bit quiet the last few days - things are a bit hectic at
> Transvirtual as I try to get stuff prepared for JavaOne next week (plus
I'm
> going skiing in Tahoe this weekend).
>
> I'd really like to get a new release of kaffe out sometime soon, since
it's
> been too long since the last release (July 24, 2000).
>
> I'm not as familiar with the codebase yet as I'd like to be - so I'm
asking
> for opinions on what absolutely should be in the next release.  I think
the
> emphasis on this release should be just getting something out that works.
> It doesn't have to work on everything, but if it doesn't work on a
> particular platform - it would be nice to identify that in the release
> notes.
>
> Here's how I'm thinking of doing it:
>
>  1) Solicit feedback on what should be in the release
>  2) If there isn't anything major that needs to be done, we'll tag a
release
> candidate for testing in CVS, next week
>  3) The people on the mailing list will test it for a week (from out of
CVS)
>  4) Two weeks from now, we'll release it as 1.0.7
>
> Does this sound OK?
>
> I'm a big believer in release early, release often.
>
> For future releases, I'd like to propose a version numbering scheme
similar
> to what's used for the Linux kernel.  eg. Even minor version numbers =
> stable, Odd minor version numbers = unstable.  So, future releases in the
> 1.0.x series would be considered stable, ready for production.  We'd open
up
> development on a new 1.1.x series, which ultimately would become 1.2.x
when
> it's deemed ready for a stable release.  With this arrangement, as
> developers, we'll have the freedom to do some radical stuff to the 1.1.x
> tree, as people downloading it will understand that it's a development
> series of releases.  When we're in full swing development mode, I'd like
to
> see releases made every few weeks or so.
>
> What do people think of that idea for versioning and making releases?
>
> Finally, when we decide to do this release, I think we should dedicate it
to
> the memory of Edouard Parmelan.  For those that don't know, he was one of
> the most active Kaffe developers, a member of the core team, and one of
the
> driving forces behind the project.  He died tragically in a motorcycle
> accident last year, leaving behind a wife and kids.
>
> I'm going to be very busy this coming week with JavaOne next week, but
I'll
> try to stay as involved as possible in trying to make this release happen.
>
> Cheers,
>
>  - Jim
>
>
>
>


------=_NextPartTM-000-170d75ce-3d4c-11d6-a942-00b0d0d06be8
Content-Type: text/plain;
	name="Wipro_Disclaimer.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename="Wipro_Disclaimer.txt"

**************************Disclaimer************************************
      


Information contained in this E-MAIL being proprietary to Wipro Limited
is 'privileged' and 'confidential' and intended for use only by the
individual or entity to which it is addressed. You are notified that any
use, copying or dissemination of the information contained in the E-MAIL
in any manner whatsoever is strictly prohibited.



 ********************************************************************

------=_NextPartTM-000-170d75ce-3d4c-11d6-a942-00b0d0d06be8--