Hi Per,
it's great to see that you take the challenge to improve
this very
helpful tool.
There is one little enhancement we might consider useful.
I saw recently some confusion about the online update
notification. Who
should enable it when during the process.
So far we have as values for status: UNTESTED, INQA,
REJECTED, APPROVED,
DISTRIBUTED. After distribution the next step would be to
publish a
build usually at a NLC download page (PUBLISHED). As soon as
the
download pages are in place and the responsible NLC
community feels
ready for it users can be NOTIFIED.
Just an idea...
Greetings
Stefan
Per Eriksson wrote:
> Dear QA Folks,
>
> My name is Per Eriksson, normally working with
marketing on the Swedish
> side, but recently joined QA to improve my skills
around the QA process
> within our community.
>
> As a web developer on my day time job, I have offered
my skills to André
> Schnabel and Andrea Pescetti, with grateful help from
Joost Andrae.
>
> André Schnabel and myself has agreed that QATrack can
help and assist
> the QA process more, increasing the quality of the work
done within the
> QA project and the NLC projects.
>
> We have therefore started the project involving the
development of
> QATrack 2.0, looking at how QATrack can provide the
tools needed to work
> with QA in an even more effective way.
>
>
> MAIN FEATURES
>
> + Centralized CollabNet Enterprise Edition (CEE)
authentication
> It will improve security and simplify password
management.
>
> + Language management
> Langauges will be administrated directly in the
interface.
>
> + IssueZilla-integration
> The web interface will integrate IssueZilla support
for creating and
> reading issues.
>
> + Improved interface
> An improved web interface with simpler navigation
lighter colors.
>
> + Personalized information
> Pages that show information related to your
languages.
>
> + Improved source code
> Improved security and simplified future development
with reusable
> objects and resources.
>
>
> PARTICIPATE
>
> All feedback is appreciated, and power users who use
the tool every day
> in their work are even more welcome! We will look at
both new features
> as well as wishes mentioned earlier but not
implemented.
>
> The development process can be followed here:
> http://wiki.services.openoffice.org/wiki/QATrack_Dev
elopment
>
> All discussion will take place on this dev qa list
with subject line
> "qatrack: ", issue tracker might be used to
track individual tasks, this
> will be announced here.
>
>
> ROADMAP
>
> Wll be shared soon.
>
>
> LAST BUT NOT LEAST
>
> If this might be valuable on any other list or NLC
project, you're
> welcome to spread it.
>
> If you want to discuss features/progress, please don't
use this subject
> line.
>
>
> See you,
>
> Per Eriksson
> (CEE: pereriksson)
>
>
------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribeqa.openoffice.org
For additional commands, e-mail: dev-helpqa.openoffice.org
|