Re: Tagging hildon packages



On Fri, 2007-10-12 at 15:17 +0300, ext Michael Dominic K. wrote:
> Makes sense to me. Do you mean the branching as an additional step to
> version name unifying, or a replacement option? Streamlining the
> version numbers might be a bit hard at this point and we'll end up
> with a lot of inconsistencies anyways.

About unifying version numbers, if you look at the list I included
there's only hildon-theme-* and sapwood which couldn't follow the 2.0.x
versioning at this stage. And all those have reason for the deviation.
(Though would be nice to have it state for hildon-theme-* too)

Unless of course I'm missing something...


> > > module                   latest tag
> > > -----------------------------------
> > > hail                   <missing?>
> > > hildon-1 (libhildon)       1.0.17-1
> > > hildon-control-panel      1:2.0.0-1
> > > hildon-desktop             0.0.39-1
> > > hildon-fm (libhildonfm)    1_1.9.41
> > > hildon-help                 1.9.5-1
> > > hildon-input-method     1_1.99.29-1
> > > hildon-theme-layout-4      0.14.0-1
> > > hildon-theme-plankton      4.14.0-1
> > > hildon-theme-tools          0.5.2-1
> > > hildon-thumbnail             0.14
> > > libhildonmime              1.9.11-1
> > > sapwood                     3.0.0-1


-- 
Tommi Komulainen                            <tommi komulainen nokia com>



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]