Re: Krysalis Version project

Adam Jack wrote, On 11/02/2003 0.36:
> All,
> 
> I need help in completing a few aspects of this project, prior to me having
> to drop out for a few weeks (to pamper my wife and new baby). No guarantees
> she is popping out so soon, but I want to prepare for that possibility. I'll
> like to wrap up a much as I can (for a phase 1 -- or review phase) this
> week.

Wow, congrats! (again)
The name of the baby?

> Since version is so young,

version version 0.1? ;-)

> and since I hold most of the internal knowledge
> (such it is) I'd like to implement a few practical use cases. There are lots
> of small things started (and incomplete) and though most aren't
> 'critical' -- I can't really predict what is needed until I get some
> usage/users. Although the ant tasks are nice 'standalone' users, there is no
> guarantee that their outputs are 'valuable' to real users.

+1

> 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.

> Note: I do not expect there to be a wealth of volunteers out there to
> download and play with version, it really isn't that interesting (especially
> in this development stage) for folks to take their time. I feel that version
> needs to be automated (inside a cent) and then exercised inside some
> projects builds, before we could even attempt to interest folk.

You have to make a first release. Releases are baselines.

> It seems (to me) that the path to follow needs to start with more
> testing/document/planning (on version's part) and then integration into some
> Krysalis projects, perhaps starting with Ruper -- but also with projects as
> users -- i.e. branding versions into classes. That said, I am sure it is
> tough to accept something unstable into stable projects -- are there any
> that could tolerate this?

It woul dinterest many. Interest is what we need. And yes, is some parts 
work, some may start using it.

> Could I receive some guidance on these things in order to move ahead as
> expeditiously as possible.
> 
> Thanks in advance.


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



-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com