Hi all,
This email will be long so bear with me..
Continuing/sidestepping on the interesting discussion between Arjen and
David about bugs/features. I'll go through the package submission
process into Trunk as our team experienced it. I promise it has a happy
ending :)
August (2010):
- We get a request that our package should be get into MeeGo. We learn
that OBS/osc is the way to do it.
- With some calls and face to face queries, we find out that persons X
or Y should be contacted for the access to OBS.
- After several calls/emails and a couple of weeks later, we actually
get the access.
September:
- We learn (via IRC) that "osc sr" is the way to actually make the request.
- We send our request. After a day or so the request disappears from
OBS. Backtracking with the request id, we see that the request has
denied. We get no further information why.
- Maybe something went wrong, so we try again. Same result.
- Some emails/calls again, and we learn that MeeGo is in freeze mode so
no new packages are accepted and this was the reason for the decline.
October:
- We make a bug that our package should be in Trunk. We didn't do this
before because we were told (can't remember by whom/where) not to do so.
- 1.1 is released, so we try the request again. Same result, the request
disappears.
- Emails/calls again, we learn that the bug type was wrong, it should
have been a Feature request. We weren't clear about the distinction though.
- Changes in the bug are made, and we wait.
November:
- A couple of weeks later, The FEA gets the accepted. We make a new sr.
Denied again, but at this time I get an email that gives me the reason.
At this point I've also learned about meego-commits (no one told me
about it the during previous discussions..). I also learn that the Nokia
email server had killed the previous decline emails, which didn't help..
- We try again. Success! The package lands into Trunk.
- Happy Ending :)
The biggest problems were visibility and the lack of information on my
part. Ignorance can be cured, as long as the information exists and you
can find it. I'll list some of the questions a new package maintainer
will have. Some of them have an answer in wiki, some of them don't.
- Does my package belong in Trunk? Should it be in community OBS? Maybe
somewhere else (e.g. a test package)? Is there a difference in The
Process between the places? Will e.g. licensing make a difference?
- I don't have an account. How do I get one?
- I'm submitting a new package. I don't have my own Bugzilla entry. Do I
need one? If so, where and how do I get one?
- I'm submitting a new package. I need to create the Feature request.
How do I do that? What is the component/subcomponent I should use? How
do I know that I made it correctly,if for example the feature request
just sits there for weeks?
- I'm updating an upstream package to a new version. Do I need to create
a new bug or feature request? Does the feature request go under my
package Bugzilla entry or somewhere under the "MeeGo Features..."?
- I need a devel project before I can submit anything into Trunk. How do
I need a new one or do I use some existing one?
- Before I make the request, how do I make the package is compliant and
all the bug/featurezilla flags are right? Is there a way to
(automatically) verify this before bugging the maintainers?
- How do I actually submit a package request?
- How do I track what happens to the submit request?
And this list doesn't have questions about the packaging itself (the
required commands, common problems etc..), Maybe someone else can list
those ;) I think we should try to gather this kind of information into a
"step by step" type of page that the maintainer can follow.
Cheers,
Tatu Lahtela
_______________________________________________
MeeGo-packaging mailing list
[email protected]
http://lists.meego.com/listinfo/meego-packaging
