Re: MidCOM 2.6 roadmap

Torben Nehmer <[email protected]> Thu, 09 Feb 2006 17:21:58 +0100
Newsgroups gmane.comp.web.midgard.devel
Message-ID <[email protected]>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

- --Piotras wrote on 2006-02-09 17:13:
> What do you think if we could create 'plans' subpage under development one? 
> This one could be simialir to this one which exists for exisiting release and
> follows gnome's convention. Something like: 
> http://www.midgard-project.org/midgard/1.7/
> 
> And /development/plans/1.8 could give you as many informations as possible.
> 
> * For developers * For end users * New features * What's going to be fixed
> 
> With correct links to already existing documentation.
> 
> It's rather simple task and I do not think we should write some particular
> mRFC about this. According to users *and* developers feedback we should have
> ready to use release notes when release should be done.

Put that way, yes that would be an idea. It is what I've been trying to
accomplish in 2.0/2.2 with my technical notes. Unfortunalety it has slept in a
bit until we had the Wiki readily available. I am planning to do a full official
(as opposed to privatly on my desk) release plan for MidCOM 3.0 again, it'll be
absolutely neccessary given the scope of changes I plan for 3.0.

It should definitly be in the Wiki, for easy maintainance, and grouped by
Versions, like my original MidCOM technical notes.

Actually I think I'll basically keep working with the tech notes in the future,
just in the Wiki, not on my own Homepage. A release plan page could then link to
them, as the technical notes will (for 3.0) again encompass everything needed to
coordinate development.


Live long and Prosper!
Torben Nehmer

- --
Torben Nehmer, Guenzburg, Bavaria, Germany
http://www.nathan-syntronics.de, mailto:[email protected]
PGP Public Key: https://www.link-m.de/pgp/t.nehmer.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFD62wmJPh4Kn6d5FYRAt7qAKDbYeIacH4lUc6PK2LkRMyHErQEgQCfTO8C
JCvkHnOaVR+rl58wPw++v1I=
=ZcQ+
-----END PGP SIGNATURE-----