"ext gary liquid" <[EMAIL PROTECTED]> writes: > what follows is the mails between myself and Marius, sorry for the confusion:
And this is my reply to Gary's last mail: > [ beta versions in their own repo ] > this worked nicely for a large number of applications but its major > disadvantages were dependencies and bitrot. Yes, this is the "repository mess" situation. I'd say it is not an option for the reasons you state. > as a maemo developer I cannot easily compile other peoples packages from > source. Yes, this is the "distribution mess" (or "SDK mess") that we haven't seriously attacked yet, but we should. > The point of testing is also testing the package itself, if a > developer has to create 2 distinct packages, one for testing and one > for real how does the developer test that his live package includes > everything required and installs and uninstalls cleanly? There are two kinds of testing: the beta testing over a long period with selected users, maybe even while new features are implemented, and the smoke testing of new stable releases that is mostly a sanity check before your package hits Joe Sixpack. Extras-devel is good for smoke testing of new releases. You are sure that the package works for you, but you would like wider exposure to test it in more environments. > The only real way to ensure its valid is to allow a user to beta-test > the actual package. You don't need to redo your packaging when moving out of beta if you plan for this. Thus, instead of naming it "foo-beta", you can name it "foo-2". This means that the betaness of your package should be signalled in some other way, via the description, its category, the icon, or maybe with a new feature of the Application manager. If you do want to redo the packaging, you can use the smoke test in extras-devel to catch bugs introduced by it. At that point, you really have stopped releasing updates to the old stable version, and there is no problem if the new stable version stays in extras-devel a bit longer to iron out the kinks introduced by the renaming. _______________________________________________ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
