[Releasing] rename qtwebkit-examples-and-demos => qtwebkit-examples?

Iikka Eklund iikka.eklund at digia.com
Wed Mar 27 12:18:54 CET 2013


On 03/25/2013 06:01 PM, Oswald Buddenhagen wrote:
> moin,
>
> for sanity and accuracy, i'd like to rename this repo.
> the impact is rather small:
> - repo rename: minor disruption, but as almost nobody is working on it,
>    most people won't notice anything beyond a (very small) module
>    appearing and another disappearing
> - adjust qt5.git (.gitmodules, qt.pro, init-repository)
> - packaging
>    - upstream: this will have no noticable impact except the name in the
>      installer lists
>    - downstream: as the repo is logically part of qtwebkit, i would not
>      expect it to be separately packaged in the first place, but follow
>      the packaging scheme of the examples of other qt modules
>

yes, only a very minor impact, so this is ok from packaging point of 
view (after 5.0.2 is out)

- iikka

> unless there is substantial resistance, i'll do that in a few weeks
> (after 5.0.2 is out and it is clear that 5.0.3 won't happen on regular
> schedule (or it did actually happen)).
> _______________________________________________
> Releasing mailing list
> Releasing at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/releasing
>


-- 
Br,
Mr. Iikka Eklund
Senior software engineer

Elektronikkatie 10
FI-90590 Oulu
Email: iikka.eklund at digia.com

Visit us at: www.digia.com or qt.digia.com
------------------------------------------------------------------
PRIVACY AND CONFIDENTIALITY NOTICE
This message and any attachments are intended only for use by the named
addressee and may contain privileged and/or confidential information. If
you are not the named addressee you should not disseminate, copy or take
any action in reliance on it. If you have received this message in
error, please contact the sender immediately and delete the message and
any attachments accompanying it. Digia Plc does not accept liability for
any corruption, interception, amendment, tampering or viruses occurring
to this message.
------------------------------------------------------------------



More information about the Releasing mailing list