Hello all,
We have a lot of issues registered in the Trac system which should be
transferred to Launchpad. Some are already moved, but most remain.
I would be very grateful if some people could help us out with this -
go through the list and add either a 1) bug or more likely a 2)
blueprint in LP for each issue in Trac.
http://207.192.75.110:82/dhis2/report/3
And please let us know that you are working on it 
Knut
I can help with this. Is there any specific ones I should take?
On Mon, Mar 9, 2009 at 12:55 PM, Knut Staring <knutst@gmail.com> wrote:
Hello all,
We have a lot of issues registered in the Trac system which should be
transferred to Launchpad. Some are already moved, but most remain.I would be very grateful if some people could help us out with this -
go through the list and add either a 1) bug or more likely a 2)
blueprint in LP for each issue in Trac.
http://207.192.75.110:82/dhis2/report/3And please let us know that you are working on it
Knut
_______________________________________________
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help : https://help.launchpad.net/ListHelp
Great, thanks! I think it would be good if you start at "the bottom of
the Trac", i.e. Milestone 2.0.2 and work upwards. Of course, check
that the issue is not already in LP (a first weeding would be great,
then we will have to do a second weeding once everything is in LP,
i.e. removing the fixed or obsolete ones and setting priorities as
part of the Roadmap discussion planned for this Thursday (March 12).
Also, it would be good to note if some issues to become blueprints
could be suitable for Google Summer of Code...
Knut
On Mon, Mar 9, 2009 at 4:50 PM, Jason Pickering <jason.p.pickering@gmail.com> wrote:
I can help with this. Is there any specific ones I should take?
On Mon, Mar 9, 2009 at 12:55 PM, Knut Staring <knutst@gmail.com> wrote:
Hello all,
We have a lot of issues registered in the Trac system which should be
transferred to Launchpad. Some are already moved, but most remain.I would be very grateful if some people could help us out with this -
go through the list and add either a 1) bug or more likely a 2)
blueprint in LP for each issue in Trac.
http://207.192.75.110:82/dhis2/report/3And please let us know that you are working on it
Knut
_______________________________________________
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help : https://help.launchpad.net/ListHelp
--
Cheers,
Knut Staring
I have taken a look at the tickets and they are quite outdated, i.e. many of them are either fixed or not relevant anymore. I think it’s better if I go though the list and move the relevant ones to launchpad soon.
What would really be of help though is if people could help out with testing. We will release 2.0.1-rc1 (release candidate 1) tonight, which will later be deployed in thousands of blocks in India and probably in other countries as well. Testing is in other words essential, and helping out here will benefit everyone involved with DHIS 2.
regards Lars
On Mon, Mar 9, 2009 at 12:43 PM, Knut Staring knutst@gmail.com wrote:
Great, thanks! I think it would be good if you start at "the bottom of
the Trac", i.e. Milestone 2.0.2 and work upwards. Of course, check
that the issue is not already in LP (a first weeding would be great,
then we will have to do a second weeding once everything is in LP,
i.e. removing the fixed or obsolete ones and setting priorities as
part of the Roadmap discussion planned for this Thursday (March 12).
Also, it would be good to note if some issues to become blueprints
could be suitable for Google Summer of Code…
Knut