[MonoDevelop] MonoDevelop 0.1 Release

[Todd Berman]

On Wed, 2004-02-04 at 00:30, Miguel de Icaza wrote:
> Hey,
> 
> >       * Icons designed. Doing a release with our current stock/windows
> >         mix would be sortta lame.
> 
> Where are those stored?

build/data/resources/icons for the time being. they will most likely be
moving a bit, but not far. NOTE: some of them are overridden inside the
code to match up with existing gtk and gnome stock icons.

> 
> >       * Also, I would like to see if we can get a few packages on Red
> >         Carpet. We should have a gtksourceview package that is in a
> >         non-unstable Ximian channel. Also, there should be a package for
> >         gtk-sourceview-sharp. As well, I would like to see a package
> >         that will register the mimetypes for C# and add icons etc.
> >         Miguel, any comments on this?
> 
> We could cross-link the package, so its not an issue.
> 
> >       * We need to get the CodeComplete/InsightWindow cleaned up. A few
> >         things there: 1) see if we can get the ctrl+space bindings 2)
> >         try to get the insight window either working nicely (eg, having
> >         it not stick around, etc).
> 
> I can help here;  What do you guys need?
> 
> Describe.  And I'll assist.

I will work on getting a list of exactly what I would like to see in
this release, what I wouldnt mind, etc.

> 
> 
> > I am a little worried about the date. It would be best to sync with a
> > Mono release so that we can take advantage of bugs that are fixed, etc.
> 
> Assume that it will be 0.30, I dont think we are doing a new release in
> such a short period.

Until we run into a mono bug that causes us problems, I see no reason to
worry about it. And I do not expect we will find any.

> > We need to come up with a list of `known issues' so that we do not get
> > tons of duplicate bug reports.
> 
> Well, I would personally like to see a list of things that must be
> tested visually.  
> 
> Something like:
> 
> 	1. Create a Gtk# project.
> 	2. Build it.
> 	3. Run it.
> 
> 		Observe: if the dialog XXX.
> 
> 	2. Create a console project....
> 
> Etc.

I agree completely.

--Todd