Re: MidCOM 2.6 roadmap

Torben Nehmer <[email protected]> wrote:

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

What I meant was 'how to create good and readable development plans'. 
On the contrary I am interested what's happening with midcom as I try to not ignore 
things with midgard as denominator.
 
> EOT.

Not for me. My patience is endless.

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.

Piotras