preliminary guide to Mercurial via workflows

[Arne Babenhauserheide]

Am Dienstag 05 Mai 2009 10:21:43 schrieb Giorgos Keramidas:
> On Tue, 5 May 2009 08:54:43 +0200, Arne Babenhauserheide <arne_bab at web.de> 
wrote:
> > Every workflow should have a section about how to release - or we
> > should have a seperate main section only about doing releases.
> >
> > Mercurial offers many advantages there, after all - including shipping
> > releases via a simple stable repository :)
>
> `Releasing' is a term that may have varying meanings, depending on what
> is being released, so do we really want to go there?  

Since every project needs to make releases of some kind, it would at least be 
nice to have some best practises, but maybe the workflows page isn't the best 
place for these. 

> These tend to be more project-specific than workflow-specific, with
> local conventions for each team.  So it may not be easy to define a 1-1
> mapping from workflows to release processes.

Maybe it would be more useful to create a wikipage with information for people 
who want to setup a release process. 

What do you think? 

Best wishes, 
Arne

--- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- 
   - singing a part of the history of free software -
              http://infinite-hands.draketo.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
Url : http://selenic.com/pipermail/mercurial/attachments/20090505/c254fd73/attachment.pgp