[Framework-Team] post-3.0: tags? branches?

[whit]

pinning seems pretty sane and makes it easy to convince a package maintainer
to branch or tag from a particular revision if maintenance branches make
sense.

-w

On 8/13/07, Wichert Akkerman <wichert at wiggy.net> wrote:
>
> With 3.0-final coming up I have been wondering how to handle the 3.0
> bundle. I would like to have this bundle be as stable as possible, which
> suggests that it ca not keep using trunks everywhere. But most products
> and packages will not have a seperate stable branch for their current or
> upcoming release either. So what to do?
>
> One option I've been pondering is to update the bundle to use tags or
> revision pins for any package or product which does not have a seperate
> maintenance branch. Possible that is a somewhat extreme thing to do
> though.
>
> I would like to hear some opinions on this before I make any decisions.
> So... what do you think?
>
> Wichert.
>
>
>
> --
> Wichert Akkerman <wichert at wiggy.net>    It is simple to make things.
> http://www.wiggy.net/                   It is hard to make things simple.
>
> _______________________________________________
> Framework-Team mailing list
> Framework-Team at lists.plone.org
> http://lists.plone.org/mailman/listinfo/framework-team
>



-- 

| david "whit" morriss
|
| contact :: http://public.xdi.org/=whit

"If you don't know where you are,
  you don't know anything at all"

  Dr. Edgar Spencer, Ph.D., 1995


"I like to write code like
other ppl like to tune their
cars or 10kW hifi equipment..."

Christian Heimes, 2004
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.plone.org/pipermail/plone-framework-team/attachments/20070814/2d095618/attachment-0002.html>