Thank you Ulf,
All for getting the changes in place in a timely and safely manner :)
Thanks again!
On 06/30/2011 05:45 PM, Ulf Hofemeier wrote:
Luis,
You are absolutely right in saying that the removal of a key component like
meegotouch should have been announced ahead of time, allowing developers to
prepare their projects for this change accordingly. However, good news is that
I got approval from Arjan to communicate that it's OK for the maliit to now
obsolete meegotouch-inputmethods*.
I'm adding Michael as he's the one announcing maliit version updates.
Thank you.
Ulf
On Jun 30, 2011, at 2:50 PM, Luis Araujo wrote:
Hello Ulf,
Earlier this morning I sent this email to our mailing list, for a bit later
receiving the notification that libmeegotouch, among with all its packages were
removed from Trunk[0].
In this case, I guess we can proceed to obsolete our meegotouch-inputmethods* packages in
favour of maliit-*?; lots of packages are "unresolvable" in OBS, and if we are
doing these changes right now, I'd say let's go all for it, or do you guys have any plan
for this migration?.
Note: I was not aware of this removal until I see it committed, was this
announced somewhere?
Cheers,
[0] http://lists.meego.com/pipermail/meego-commits/2011-June/030779.html
PS: CC'ing meego-packaging@ too as this might be relevant to all maintainers.
On 06/30/2011 10:44 AM, Luis Araujo wrote:
Hello everyone,
This is a brief update about the current status for our packages in MeeGo.
We currently have the maliit-framework and maliit-plugins version 0.80.0
packages inside MeeGo Trunk:Testing repository. These packages as previously
announced[0] are introducing major changes, among them, new libraries names and
paths.
Initially I submitted the packages directly to the repository, marking as
obsolete the respective meegotouch-inputmethodframework and
meegotouch-inputmethodkeyboard packages in favour of our new maliit-* versions.
But this caused some errors during image generation, since some packages are
still evidently depending on the old library names, more specifically to
libmeegoimframework.
There seems to be no clear documented road to do this kind of migration, but my
plan so far is to contact the developers/maintainers of the affected packages
and work with them implementing the fixes, with an announcement here and in
meego-{packaging,dev}@ if required. I am also thinking to raise up this issue
in the TSG meetings, and see what we can come out with.
Now, one important detail, we were told that there are no resources at this
point to fix these packages in Trunk:Testing due to the upcoming tablet product
launch, since most of the developers are focusing on that release, committing
our changes or working out a solution might take a while. From release
engineering, apparently they will get back to work in Trunk after the 1.2.0
update release after July 7th, so I guess around this time things might go bit
slow.
In a related note, the release plan for 1.3 was posted already[1]. We will have
to implement these changes during the high risk intrusive phase due to:
MM2: Jul 26 - Intrusive (high risk and priority) changes phase complete
I will keep posted here about any progress, please if you have any question or
doubt, let me know.
Cheers,
[0] http://lists.meego.com/pipermail/meego-inputmethods/2011-June/000157.html
[1] http://wiki.meego.com/Release_Engineering/Plans/1.3
_______________________________________________
MeeGo-inputmethods mailing list
[email protected]
http://lists.meego.com/listinfo/meego-inputmethods
http://wiki.meego.com/Mailing_list_guidelines
http://wiki.meego.com/Meego_Input_Methods
_______________________________________________
MeeGo-packaging mailing list
[email protected]
http://lists.meego.com/listinfo/meego-packaging
_______________________________________________
MeeGo-packaging mailing list
[email protected]
http://lists.meego.com/listinfo/meego-packaging
