Putting together the 0.3 release plan

[JonathanKohl]

I have a lot of questions about when the next release of ST 0.3 will
be out. I've been waiting for people to become familiarized with the
code base and the project, but it's probably time to start making it
real.

What would you like to see in the next release? What would you like to
work on?

-Jonathan

[JonathanKohl]

I was thinking of cutting things off at the user configuration section
here :
http://wiki.openqa.org/display/ST/ST+0.3+Release+Worklist

My goal would be to transition the tool to be more like a testing IDE.
Text editing, a tree view for projects, files, and some cleanup/bug
fixing.

Is this list too large?

Reporting:
- web report clean up

User Interface Changes
http://wiki.openqa.org/display/ST/Project+Roadmap

Session Browser
- tree view like in an IDE to navigate to saved session files

Text Editor/Tags
-use the JEdit syntax editor for text editing

Timer
- fix timer bugs

General Bug Fixes

Update Help and Documentation

[Louise Geijer]

Hi!
I've been really busy for a while but now I really want to get going with this project again.

I think it can be a good idea to cut the user configuration section. We are a bit short on developers and it's perhaps better to concentrate on the IDE/tree-view, new editor functionality, nicer web reports and of course some bug fixing. That should keep us busy for a while!

I've never been part of this sort of project before, is it stupid to set an inofficial release date or maybe a release month? I like time-specific goals and even if they sometimes need to be re-evaluated..

//Louise

[JonathanKohl]

Thanks Louise. I appreciate your feedback. :-)

Setting a deadline is absolutely fine. Most of us tend to work a bit
better with a deadline, as long as it isn't unrealistic. Since this is
an iterative project, we don't have to worry about getting everything
perfect on a certain date and have that pressure, but we want to do as
well as we can. If it helps, I can work with you all to get a set of
tickets together in Jira, set a date, and then see where we get.

-Jonathan

[Henrik Almegren]

Hi

About the "session document tree view: test session browser" item in the 0.3 release list, what shall the tree contain? Just sessions? In that case it is just a list not a tree. Or is each session a container for more stuff than just the session (xml) document? In that case, what can it contain? I'm thinking stuff you collect during the session, like notes, screenshots, logs etc. The concept of "project" has also been mentioned. Shall the root of the tree contain session, projects or both? Shall projects contain sessions? How about a nice drag and drop feature? Drop anything in the session editor and a tag is created, linking to the dropped object that also shows up in the tree, as a child to the current session. It would be fun to try to build a prototype of the tree but I need more information about (and understanding of) the ideas.

Any thoughts?

Now it's time for football

Henrik

[JonathanKohl]

Great question Henrik. I started modeling that on Friday, and I'm
creating a document that describes work packages in more detail. I'll
get Martin's take on it, and send it to the rest of the group so we
have more specifics.