Re: Tagging hildon packages
- From: Lucas Rocha <lucas rocha nokia com>
- To: "ext Michael Dominic K." <mdk mdk am>
- Cc: hildon-list <hildon-list gnome org>
- Subject: Re: Tagging hildon packages
- Date: Fri, 12 Oct 2007 15:49:11 +0300
Hi,
Em Sex, 2007-10-12 �15:17 +0300, ext Michael Dominic K. escreveu:
> On 10/12/07, Lucas Rocha <lucas rocha nokia com> wrote:
> > Hi all,
> >
> > I'd like to suggest something slightly different.
> >
> > >From 2.0 on, we should tag our *upstream* releases (no the maemo debian
> > packages) just like in GNOME modules. For example: hildon-desktop 2.3.1
> > would be tagged as HILDON_DESKTOP_2_3_1. This way we don't mix debian
> > packages tags with upstream packages.
> >
> > IMO, we should branch all our modules for Hildon 2.0 release with the
> > same branch name. My suggestion is that we all modules have a branch
> > named "hildon-2-0". Future development continues on trunk.
> >
> > I have some other ideas but, for now, I'd like to know what you all
> > think about this basic tagging ans branching policy.
>
> 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.
I'm not talking about streamlining the version numbers. The branch
"hildon-2-0" would used for the major/wider "Hildon 2.0" release in each
module. Call it "the current stable code branch". Trunk would be used
for new features development for future major released. The proposed tag
names standard would be used for upstream tags in each module.
Basicaly, what I'm proposing is that we use the GNOME Way(tm). Have a
look at this page for more detailed info:
http://live.gnome.org/MaintainersCorner
--lucasr
> > Em Ter, 2007-10-02 �10:32 +0300, ext Tommi Komulainen escreveu:
> > > Hi,
> > >
> > > Below is the list of latest tags in sardine.packages for the modules
> > > listed in http://live.gnome.org/Hildon/MigrationToGnome
> > >
> > > I know we didn't exactly have release candidates or other release
> > > process, but could the maintainers tag their releases as '2.0.0' when
> > > you think it's good to call stable?
> > >
> > > If '2.0.0' doesn't make sense for a module, feel free to use a version
> > > number that makes sense and indicates a "stable" release (as opposed to
> > > constantly being developed in random ways.)
> > >
> > >
> > > 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
> > >
> > >
> >
> > _______________________________________________
> > hildon-list mailing list
> > hildon-list gnome org
> > http://mail.gnome.org/mailman/listinfo/hildon-list
> >
>
>
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]