[Rock-dev] Flavours, freezes, updates

[Jakob Schwendner]

Hi,

Any ideas on a transition plan for these changes? I guess the autoproj commit feature could be independent from having releases instead of our master/next/stable cycle.

Cheers,

Jakob

> -----Original Message-----
> From: rock-dev-bounces at dfki.de [mailto:rock-dev-bounces at dfki.de] On
> Behalf Of Sylvain Joyeux
> Sent: Dienstag, 1. Juli 2014 11:21
> To: Steffen Planthaber
> Cc: rock-dev at dfki.de
> Subject: Re: [Rock-dev] Flavours, freezes, updates
> 
> Thanks Steffen, your summary is IMO quite accurate.
> 
> 
> 	Using the tags you can easily find and reproduce former states of the
> 	software. This is only true for a complete snapshot of all packages, so
> 	it it only useful directly after a autoproj commit. Both can be
> combined
> 	into a single command
> 
> 
> They can, but they should not IMO. The same way than git commit and git tag
> are two different things, I would keep autoproj commit and autoproj tag
> separate. If only to reuse prior knowledge about git.
> 
> Sylvain