Active Topics
-
Maemo repository (8)
to Community by Maemish - 21 hrs, 17 mins ago -
Porting apps to Leste (44)
to Maemo 7 / Leste by norayr - 1 day, 1 hr ago -
List of well performing apps on Leste (35)
to Maemo 7 / Leste by smatkovi - 3 days, 23 hrs ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (13)
to SailfishOS by edp17 - 4 days, 21 hrs ago -
Sailfish OS for the Samsung Galaxy Note 4 (SM-N910C) - (treltexx) (79)
to SailfishOS by edp17 - 4 days, 21 hrs ago -
U-Boot for Nokia RX-51 with BootMenu (updated version 2012.10-rc3-1) (843)
to Alternatives by Arno_11 - 5 days, 2 hrs ago - more...
 |
|
2010-08-01
, 13:13
|
|
Posts: 2,154 |
Thanked: 2,186 times |
Joined on Dec 2009
@ Hellsinki, Finland
|
#2
|
In my case it's because of two things:
- I got server error when tried to promote severall my themes right after receiving promotion unlocked -mails
- I can't remember which of my themes are unlocked since there are so many of them. A single page which would show status of all my maintained packages would be more than helpful. Now it's slow to search for all packages and then go and check if the testing version is promotable or not.
- I got server error when tried to promote severall my themes right after receiving promotion unlocked -mails
- I can't remember which of my themes are unlocked since there are so many of them. A single page which would show status of all my maintained packages would be more than helpful. Now it's slow to search for all packages and then go and check if the testing version is promotable or not.
__________________
If you're rich and you think I deserve a cold beer, you may donate one or two :-P
80's style stadium rock is back - FIRENOTE
Hi-Octane heavy metal - FORCE MAJEURE
If you're rich and you think I deserve a cold beer, you may donate one or two :-P
80's style stadium rock is back - FIRENOTE
Hi-Octane heavy metal - FORCE MAJEURE
|
|
2010-08-01
, 13:24
|
|
Posts: 3,319 |
Thanked: 5,610 times |
Joined on Aug 2008
@ Finland
|
#3
|
Originally Posted by D-Iivil
I’ll try and see with our webmaster if we can resend the promotion emails.
In my case it's because of two things:
- I got server error when tried to promote severall my themes right after receiving promotion unlocked -mails
- I can't remember which of my themes are unlocked since there are so many of them. A single page which would show status of all my maintained packages would be more than helpful. Now it's slow to search for all packages and then go and check if the testing version is promotable or not.
__________________
Blogging about mobile linux - The Penguin Moves!
Maintainer of PyQt (see introduction and docs), AppWatch, QuickBrownFox, etc
Blogging about mobile linux - The Penguin Moves!
Maintainer of PyQt (see introduction and docs), AppWatch, QuickBrownFox, etc
|
|
2010-08-01
, 13:27
|
|
Posts: 159 |
Thanked: 122 times |
Joined on Nov 2009
|
#4
|
Originally Posted by D-Iivil
Thanks for your thoughts.
In my case it's because of two things:
- I got server error when tried to promote severall my themes right after receiving promotion unlocked -mails
- I can't remember which of my themes are unlocked since there are so many of them. A single page which would show status of all my maintained packages would be more than helpful. Now it's slow to search for all packages and then go and check if the testing version is promotable or not.
The server issue is really an subotpimal. What do you think of solution 1?
If you had an auto-promote option enabled your packages would get promotion when the server recovered.
How about this list?
If the Karma number is green, the package is unlocked and with 5 pages the list is not to long.
And this list is sorted alphabetically and your packages have all the same prefix.
Nevertheless, maybe you can add more solutions to the brainstorm issue?
|
|
2010-08-01
, 14:42
|
|
Posts: 2,154 |
Thanked: 2,186 times |
Joined on Dec 2009
@ Hellsinki, Finland
|
#5
|
Originally Posted by hschmitt
Thanks for the urls. I cleared the list on my part:
Thanks for your thoughts.
The server issue is really an subotpimal. What do you think of solution 1?
If you had an auto-promote option enabled your packages would get promotion when the server recovered.
How about this list?
If the Karma number is green, the package is unlocked and with 5 pages the list is not to long.
And this list is sorted alphabetically and your packages have all the same prefix.
Nevertheless, maybe you can add more solutions to the brainstorm issue?
- promoted packages that were PR1.2 compatible
- thumbed down the ones that were not
__________________
If you're rich and you think I deserve a cold beer, you may donate one or two :-P
80's style stadium rock is back - FIRENOTE
Hi-Octane heavy metal - FORCE MAJEURE
If you're rich and you think I deserve a cold beer, you may donate one or two :-P
80's style stadium rock is back - FIRENOTE
Hi-Octane heavy metal - FORCE MAJEURE
|
|
2010-08-01
, 14:55
|
|
Posts: 159 |
Thanked: 122 times |
Joined on Nov 2009
|
#6
|
Originally Posted by D-Iivil
I created a solution suggesting to add an option for a maintainer "will not promote".
Thanks for the urls. I cleared the list on my part:
- promoted packages that were PR1.2 compatible
- thumbed down the ones that were not
What do you think?
 |
|
2010-08-01
, 15:02
|
|
Posts: 246 |
Thanked: 204 times |
Joined on Jun 2007
@ Potsdam (Germany)
|
#7
|
Originally Posted by hschmitt
Is there no possibilty for a package maintainer to demote a package if he does not wish to promote it?
I created a solution suggesting to add an option for a maintainer "will not promote".
What do you think?
__________________
|
|
2010-08-01
, 15:10
|
|
Posts: 3,319 |
Thanked: 5,610 times |
Joined on Aug 2008
@ Finland
|
#8
|
Originally Posted by hschmitt
What would the rationale be for that ? Testing is a temporary repo before getting to Extras. If you don't want it in extras, you should keep it in extras-devel. If you mean 'will not promote' as in want to remove the package from testing, they just need to thumb their package down.
I created a solution suggesting to add an option for a maintainer "will not promote".
What do you think?
__________________
Blogging about mobile linux - The Penguin Moves!
Maintainer of PyQt (see introduction and docs), AppWatch, QuickBrownFox, etc
Blogging about mobile linux - The Penguin Moves!
Maintainer of PyQt (see introduction and docs), AppWatch, QuickBrownFox, etc
|
|
2010-08-01
, 15:12
|
|
Posts: 3,319 |
Thanked: 5,610 times |
Joined on Aug 2008
@ Finland
|
#9
|
Originally Posted by D-Iivil
One teensy request - please upload screenshots of the themes on the respective pages (as it is now, they all have the '?' instead of screenshots).
Thanks for the urls. I cleared the list on my part:
- promoted packages that were PR1.2 compatible
- thumbed down the ones that were not
__________________
Blogging about mobile linux - The Penguin Moves!
Maintainer of PyQt (see introduction and docs), AppWatch, QuickBrownFox, etc
Blogging about mobile linux - The Penguin Moves!
Maintainer of PyQt (see introduction and docs), AppWatch, QuickBrownFox, etc
|
|
2010-08-01
, 15:56
|
|
Posts: 159 |
Thanked: 122 times |
Joined on Nov 2009
|
#10
|
Originally Posted by attila77
Okay, I did not know. The intention was, that a developer might just want to collect some feedback for a alpha/beta version, but does not want to have this version in Extras.
What would the rationale be for that ? Testing is a temporary repo before getting to Extras. If you don't want it in extras, you should keep it in extras-devel. If you mean 'will not promote' as in want to remove the package from testing, they just need to thumb their package down.
How can this be reduced?
Brainstorm at Many tested apps in Extras-testing are not promoted timely
Last edited by hschmitt; 2010-08-03 at 10:55.