[maemo-developers] where might this old version be coming from

[From: Frank Banul]

On Wed, Oct 1, 2008 at 3:38 PM, Ryan Abel <rabelg5 at gmail.com> wrote:
> On Oct 1, 2008, at 1:10 PM, Frank Banul wrote:
>>>>
>>>> Then when I'm finally satisfied,
>>>> promote to extras. But it seems that extras-devel has many of
>>>> the same rules as extras. Oh well, I appreciate the information.
>>>>
>>> Extras-devel is a testing area, and potentially testers and developers
>>> can install packages from there for testing, right? If developer would
>>> reupload package with the same version how people, who install this
>>> package from extras-devel would know which package they installed? How
>>> they can be sure that they installed fixed package, if fixed and broken
>>> packages would have the same version?
>>
>> Well I control that don't I? If I want to make sure users get the
>> update, then I bump the revision. If I don't care, then I don't. I had
>> the impression using extras-devel was risky anyway. Adding the risk of
>> different code with the same revision doesn't bother me until it
>> happens in the extras repository. All just my opinion.
>
> It's wise to follow proper packaging procedure even during testing phases.
> Two different packages with the exact same version doesn't make much sense,
> does it? :)

If that's not a rhetorical question, yes it did make perfect sense (to
me). My testing follows something like this. 1) Test on scratchbox
until happy. 2) Copy the deb over to my tablet. Test again until
happy. 3) Upload to the autobuilder, download from extras-devel on a
2nd tablet and test until happy. 4) Promote to extras. At this point,
any changes (in my opinion) deserve a revision.

In this specific case I got fed up with a gtk file chooser and
switched to a hildon file chooser while in step 3. Is that worthy of a
revision to something in a devel repository? I had not thought so.

But no matter, I don't have a problem with it.

Frank