[Ottoproject-devel] Planning

[TJ S. <tj...@ca...>]

Now that Otto is free (woohoo!), we'll want to draft up the stuff we think
we need/want to have done before doing a release...and even to come up
with a release policy.

For release policies, do we want the "release early, release often"
approach, where we basicially release everything we have now (don't know
how many would download it, or where we'd announce it [I just registered
ottoproject on freshmeat.net]), or we could have semi-definite roadmaps
for each release.

The things, as I see them, that would probably be required for a first
release:

  - migration to Postgres and/or MySQL for the db backend stuff
  - writing of installer scripts and/or instructions (RPMs?) for
    installation
  - basic usage docs/User Guide/Tutorials
  - User ACLs
  - fully breaking the Agent registration step out of the Inventory module

Other infrastructure stuff we'll probably want/need:

  - non-SF domain, e.g. ottoproject.org?  That way, we could (initially)
    have ottoproject.org simply redirected to ottoproject.sourceforge.net.
  - website (what Otto is, goals, how it works, who we are, that
    whitepaper/high level stuff, etc)
  - bug database (do we want to use SF's bug tracker, or set up a
    Bugzilla instance on something like bugs.ottoproject.org)
  - CVS and releases: I think it'd be a good habit if, when we want to
    do a release, we create a branch from the main development trunk and
    release from there.  It'll make maintenance of multiple releases
    (e.g. alpha/beta/RC/stable) easier.

TJ

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

   To believe in something, and not to live, is dishonest.

   	-Mahatma Gandhi

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~