On Friday 17 February 2012 06:26:29 Matti Airas wrote:
> Hi all,
> 
> Since PySide is becoming a Qt add-on project, we're also moving the
> different project facilities to Qt. Significantly, this mailing list
> will be migrated from the current self-hosted Mailman setup to
> qt-project.org. The new mailing list address will be
> pys...@qt-project.org. I'll try to arrange a bulk move of all list
> subscribers to the new list so that no other action than possible
> updates of mailing list filters would be required on the subscribers'
> behalf.
> 
> As for the other project facilities, the Git repositories have been
> migrated from Gitorious to Qt's Gerrit setup. The new repositories are:
> 
> ssh://codereview.qt-project.org:29418/pyside/apiextractor.git
> ssh://codereview.qt-project.org:29418/pyside/generatorrunner.git
> ssh://codereview.qt-project.org:29418/pyside/shiboken.git
> ssh://codereview.qt-project.org:29418/pyside/pyside.git
> 
> These are the official PySide repositories from now on.
> 
> The new repositories have their history flattened, with the old
> repositories being archived in gitorious.org. Please don't make any
> commits to the Gitorious repos any longer.
> 
> The new repos also have some contributions withdrawn, and therefore
> there are some regressions at the moment. I will file bugs explaining
> the issues as soon as Marcelo Lira adds component version numbers to the
> Jira bugtracker.

Need I to fill version information on PySide as well? If so, where can I do 
this? I asking because I didn't found any option on jira, but there's a huge 
chance that I was looking at the wrong place.

> All Qt projects use Qt's Jira bugtracker, and so will PySide. The new
> bugtracker can be found at:
> 
> https://bugreports.qt-project.org/
> 
> Unfortunately, it is not yet possible to report new bugs until Marcelo
> Lira has added version numbers to the different PySide components.
> Nevertheless, I recommend to refrain from opening new bugs in the old
> Bugzilla from now on.
> 
> I am unsure about what would be the best way to deal with the existing
> Bugzilla bugs. I'd prefer disabling creating new bugs there as soon as
> the kinks with Jira have been ironed out, but there are currently 67
> open bugs. One possibility would be to continue tracking them in
> Bugzilla in parallel with the new Jira bugtracker, but I don't know if
> they can be resolved before the old server goes away, so I'd be hesitant
> to take that approach. My proposal is that we simply comment on the open
> bugs and ask the reporters to re-submit the bugs to Jira if they still
> regard the bugs valid.
> 
> Cheers,
> 
> Matti Airas
> _______________________________________________
> PySide mailing list
> PySide@lists.pyside.org
> http://lists.pyside.org/listinfo/pyside

-- 
Hugo Parente Lima
INdT - Instituto Nokia de Tecnologia

Attachment: signature.asc
Description: This is a digitally signed message part.

_______________________________________________
PySide mailing list
PySide@lists.pyside.org
http://lists.pyside.org/listinfo/pyside

Reply via email to