[Pkg-javascript-devel] git-buildpackage workflow

[Jonas Smedegaard]

Quoting Jérémy Lal (2012-12-15 20:32:35)
> i want to switch to a simpler and more efficient way
> of using gbp branches for the packages i am maintaining :
> 
> * always import on "upstream" branch
> * work on latest versions is made on "master" branch
> * create branches of "master" when needed, but use them
>   only for bug fixing (typically: "master-wheezy")
> 
> No more master-experimental, upstream-experimental couples

How then to handle cases where latest upstream version is not latest 
*stable* upstream version?

I mean - a very common use for the experimental suite is to try out 
newer upstream releases known to not yet be mature enough for unstable.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-javascript-devel/attachments/20121215/6b169836/attachment.pgp>