Thanks for your report!

This is more a broad topic than just a definite bug item and should be discuted further with -discuss and marcomm teams. If this is done for KDE, this could/should be done for other components as well.

It's more about strategy, how to advertise later updates of initially released components, how to attract new users, where to put the focus, with whose resources and when, etc. You're welcome to suggest this and provide your insights to the marcomm' team (which is to grow, as you noticed properly) mailing-list or the -discuss ml: https://www.mageia.org/mailman/

CC: (none) => rdalverny

@ Dieter
@ Romain

Was there ever a discussion about this issue? 

I wasn't aware of it before, but updates-announce@ml.mageia.org mails don't show the version number of an update in the subject line. Would it be possible to add that? (And whom should I ask?)

@ Romain

BTW, please set status to ASSIGNED if you think this bug was assigned to the webteam correctly. If for work flow reasons you can't do that, then please put OK on the whiteboard instead.

CC: (none) => marja11

My apologies Marja and Romain, 

real life for me is now not going well and all my home computer work I fail to address time for it. 
I have not discussed about this bug any further.
I still find it important for Mageia to have a website where the latest features of its current distribution with important updates can be easily seen.

I don't understand your question about "the version number of an update in the subject line"". Do you mean that you don't see the "4.6.5" in the subject line between "KDE" and "updates"?

(In reply to comment #3)
> My apologies Marja and Romain, 
> 
> real life for me is now not going well and all my home computer work I fail to
> address time for it. 


Very best wishes for 2012, I hope that life will be a lot easier on you, and that you'll be healthy and happy and not in need of anything important.

> I have not discussed about this bug any further.
> I still find it important for Mageia to have a website where the latest
> features of its current distribution with important updates can be easily seen.

What is important for one person, might be trivial for the next person and the other way around.

We do have the anouncement on this page now:
http://www.mageia.org/en/support/

It links to the updates-anounce mailing list
https://ml.mageia.org/wwsympa-wrapper.fcgi/info/updates-announce

> 
> I don't understand your question about "the version number of an update in the
> subject line"". Do you mean that you don't see the "4.6.5" in the subject line
> between "KDE" and "updates"?

Almost, when I receive such a mail, all I see is, e.g.:
[updates-announce] Package update: kdebase4-workspace (core)
and even when I open the mail I don't see the new version number.
I would like to see e.g.:
[updates-announce]: kdebase4-workspace-4.6.5-1.4 (core)

But I guess I should ask this as an enhancement in a seperate bug report :)

Anyway, I saw you don't receive those mails. Can you please subscribe to that list, and report back what you think about it?

Thank you, best wishes for you too of course.

I've subscribed to the updates-announce mailing list now and see what you mean but I can't help you with that. I do not know who you need to contact for that.

Regards

has there been a separate enhancement bug request? it should block this one. 

allthough i think this modification might need to be done by sysadmin team? (unsure)

CC: (none) => alien

We have two (non exclusive from each other) solutions at least:
 - publish a RSS feed sourcing from the same source as the ml + version numbers as Marja suggests;
 - publish on the release page a list of "critical" components with their original version (at release time) + their last updated version in this release.

Other ideas?

@Marja: assigning the bug before having someone actually taking care of it (asking/coding/testing) won't be really helpful. We're still discussing it here.

(In reply to comment #7)
> We have two (non exclusive from each other) solutions at least:
>  - publish a RSS feed sourcing from the same source as the ml + version numbers
> as Marja suggests;
>  - publish on the release page a list of "critical" components with their
> original version (at release time) + their last updated version in this
> release.
> 

I think it would be great to have both :)

> Other ideas?

Yep, what do you consider to be "critical" components? All security updates, of course, and what else? 

> 
> @Marja: assigning the bug before having someone actually taking care of it
> (asking/coding/testing) won't be really helpful. We're still discussing it
> here.

I understand. So it is no problem if I ping again when nothing happened to it for a while :D

(In reply to comment #8)
> Yep, what do you consider to be "critical" components? All security updates, of
> course, and what else? 

"critical" was not the right word; I meant, big things like the kernel, KDE, GNOME, LibreOffice, Firefox, etc. that may draw interest; it's a arbitrarily limited list of component to show the version that's available in a up-to-date Mageia given release.

(In reply to comment #9)

> big things like the kernel, KDE,
> GNOME, LibreOffice, Firefox, etc. that may draw interest; it's a arbitrarily
> limited list of component to show the version that's available in a up-to-date
> Mageia given release.

This list isn't too long and I don't see anything in it that shouldn't be there :)

(In reply to comment #4)

> Almost, when I receive such a mail, all I see is, e.g.:
> [updates-announce] Package update: kdebase4-workspace (core)
> and even when I open the mail I don't see the new version number.
> I would like to see e.g.:
> [updates-announce]: kdebase4-workspace-4.6.5-1.4 (core)


I've started adding the version to the updates I push manually for now.

But I guess this is also a feature request for the repo management tool boklm is working on.

CC: (none) => tmb

(In reply to comment #11)
> 
> But I guess this is also a feature request for the repo management tool boklm
> is working on.

Yes, new tool to manage updates should support this.

CC: (none) => boklm

(In reply to comment #12)
> (In reply to comment #11)
> > 
> > But I guess this is also a feature request for the repo management tool boklm
> > is working on.
> 
> Yes, new tool to manage updates should support this.

So bug 3964 should be re-assigned to you?

(In reply to comment #13)
> 
> So bug 3964 should be re-assigned to you?

yes

old

Status: NEW => RESOLVED
Resolution: (none) => OLD