Re: MidCOM 2.6 roadmap

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

- --Piotras wrote on 2006-02-09 13:51:
>> [1] http://www.midgard-project.org/documentation/midcom-2-5-roadmap/ [2]
>> http://www.midgard-project.org/documentation/midcom-development-technical-notes/
>> 
> 
> Can you point me to some mRFC which is a basement for roadmap publishing? 
> Should I write roadmap as developers adressed list or rather as future
> release notes?
> 
> Also the question for *all* developers at this list. How much of you are
> familiar with 1.8 plans after reading plans "compatible" with releases' mRFC?
>  http://www.midgard-project.org/development/mrfc/0008.html
> 
> Quoting: "The schedule for next two releases should be always available in a
> calendar on the Midgard website and in a subscribe-able vCal format. The
> calendar should also generate notices to the midgard-dev mailing list. Making
> decisions on the release schedule and keeping the calendar updated are duties
>  of the Release Manager."

This mRFC has proven impractical, which is why I did not adopt it for MidCOM.
What you do at the core is none of my business though.

EOT.


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

iD8DBQFD61wmJPh4Kn6d5FYRAlDgAJsHy4cagiKSGS8SkjJe0lbvXgd4NACg+NWp
yqcHj3z0I3QnM3aaIkuA7uA=
=eiE5
-----END PGP SIGNATURE-----