New maintainer: how to upgrade an existing package

[marvin_ita]

I'm entering the world of Fedora contributor, but there is so many documentation that I'm starting to be confused...
I followed the steps in the wiki on how to become a contributor, but I don't know hot to proceed: the wiki says to open a bug report for reviewing a new package, but I'm updating an existing package and not creating a new one.
Should I open the bug report or not?? :confused:

Thanks

[sea]

Salve

Sharing my 2 cents here, as noone has replied yet.
The folling is ALL IMHO.

Going to be a contributor, means that you've got more experience (at least on that specific topic) than others.
Further, that brings you to the other side of anykind of support. Which means, rather than asking WHY cant i, you'll be saying, BECAUSE OF things one cannot do other things.

By that i mean, you not only KNOW the issue, but you're understanding it.
You understand, or at least aim to, the user on his side, his (spare, if any) understanding of the topic/issue/incident you're going to solve.

AFAIK, its opensource, which means, ANYONE, in this case you, may contribute anything and everything that helps to solve the issue.
If it needs you to re-open the topic than do so.
If you need more information to solve the issue, then ask them (in the bug).

[sonoran]

Have you followed the wiki instructions on introducing yourself? http://fedoraproject.org/wiki/Join_the_package_collection_maintainers#Introduce_ yourself

I think once you do that you will get fast, appropriate advice on what to do next.

You can look through the devel list archives for Self-Introduction posts if you are unsure what to say:
https://admin.fedoraproject.org/mailman/listinfo/devel

Thanks for becoming a contributor. :cool:

[leigh123linux]

I'm entering the world of Fedora contributor, but there is so many documentation that I'm starting to be confused...
I followed the steps in the wiki on how to become a contributor, but I don't know hot to proceed: the wiki says to open a bug report for reviewing a new package, but I'm updating an existing package and not creating a new one.
Should I open the bug report or not?? :confused:

Thanks


Is the package depreciated or orphaned?, if it's been in either of these states for more than four months it will need a new review.
If the package is owned you can apply to co-maintain it .

[marvin_ita]

Thanks to all for replies.

@Sonoran: no, I didn't introduced myself into devel mailing list, I'm stuck some line before in the wiki where it says to open a review request in bugzilla. I didn't introduced myself yet because in the signup page it says that the mailing list is not for support... but I will do. I will also join the IRC in #fedora-devel.

@Leigh: I looked in Fedora Package Database and Skychart (the package I would like to upgrade) is not orphaned and it has two maintainers. But the last build is 6 months old and a newer version is available. My doubt is: should I need to open a review or I can apply to co-maintain, start building in koji and the first maintainer will choose if my rpm is suitable or not?

[leigh123linux]

Thanks to all for replies.

@Sonoran: no, I didn't introduced myself into devel mailing list, I'm stuck some line before in the wiki where it says to open a review request in bugzilla. I didn't introduced myself yet because in the signup page it says that the mailing list is not for support... but I will do. I will also join the IRC in #fedora-devel.

@Leigh: I looked in Fedora Package Database and Skychart (the package I would like to upgrade) is not orphaned and it has two maintainers. But the last build is 6 months old and a newer version is available. My doubt is: should I need to open a review or I can apply to co-maintain, start building in koji and the first maintainer will choose if my rpm is suitable or not?


File a bugreport against skychart and title the report "RFE: new version available" and justify the need for the update eg: what bugs it fixes and what enhancements it adds.

[marvin_ita]

File a bugreport against skychart and title the report "RFE: new version available" and justify the need for the update eg: what bugs it fixes and what enhancements it adds.

Bug filled... even if it isn't valid to become a co-maintainer, if someone wants to give me a review of my source rpm I would appreciate: https://bugzilla.redhat.com/show_bug.cgi?id=769454

At least I will know if I'm doing things in the right way..... ;)