Re: Krysalis Version project

Adam Jack wrote, On 13/02/2003 1.53:
> 	> I know this project is young, but I'd like to have input on a Project
> 	> Release Plan and/or Project Integration Test Plan and/or Project Rollout.
> I
> 	> do not know how Krysalis typically takes something like version and turns
> it
> 	> from development (at best) code into well tested release code, but I'd
> 	> appreciate your insights.
> 
> 	They are the typical OS mantras. Release early, release often. This
> 	doesn't mean you need a perfect product, in fact you should never have
> 	it perfect. The problems, and wanting to fix it, is what makes other
> 	developers coma and help. Make some functionality work well, and ignore
> 	other part. Get a website up, describe all the functionality (with notes
> 	on the broken ot not-yet-tested parts), make some examples, and make a
> 	release.
> 
> 	[...]
> 
> 	You have to make a first release. Releases are baselines.
> 
> Ok, I agree -- enthusiastically -- release early, release often -- I'd like
> to do a 1.0.1 that contains
> (primarily) the ant tasks.  [After than I'll work on Ruper integration, and
> more Version 'styles' -- such as Maven's -- related items.]

Ok. Do a 0.1 release. Doing a 0.x release is typical of projects that 
have not yet reached all the features wanted.

> Ok, so how do I 'release'? If the Nick's gump build tonight works, and
> generates/uploads a site we ought
> have a site, a distribution, ant tasks, and some documentation [which I will
> keep working on]. We have unit tests that test these ant tasks work, and
> they pass. Is that enough for a release? Do we need 'release notes'?

Nick has already showed you

> Can this have a release whilst in the sandbox?

Good question. Usual answer: no. Current answer: no.
If you want to make a release, even if it's a 0.x release, it has to be 
voted by the committers and PMC. Thus it becomes a full Krysalis project.

The alternative is to make a snapshot, instead of a release. It's 
typical for sandbox stuff, and it's not a Kryslis commitment.

Given the pace of how it' smoving, and the interest it recieved, I'm 
personally eager to see it in Krysalis proper. Make up a release 
candidate with all that is needed, and ask us to vote on it and on the 
project coming out of the sandbox.

> BTW: I'd love to have a 'cent' in the first release, like the one that Nick
> started, unfortunately that is not in my control and I don't know if Nick
> has time to help me. As such I am flexible for either way. Anou's Eclipse
> plug-in works (for her/I) but I don't want to pressure her to 'certify' it
> for this release, so I am game for with or without.

In the release you should put everything that it's in the code, and 
publicize the working parts. OS projects should never be perfect. They 
have to have a part that works well, and others that need more work, so 
we can eventually find new developers eager to help and/or give feedback.

-- 
Nicola Ken Barozzi                   [email protected]
             - verba volant, scripta manent -
    (discussions get forgotten, just code remains)
---------------------------------------------------------------------



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf