The idea is to eventually avoid that "nightmare".

Plugins zip's would be built from tags that are created on the different
plugins branches. For stable versions of plugins, ie branched and tagged for
the latest stable habari release, users will be able to download that
specific zip. People running habari head HEAD, will need to check out the
plugins from their habari upcoming versions branches using svn (They are
running habari dev, you'd assume that there would not be an issue running a
dev versions of the plugins).

This would mainly allow easy developement and release for more than one
plugin version for the same habari version. I don't see how this can be done
all within trunk without having to revert changes, tag and then reapply.
Quite messy.

Another problem with the past setup is that we cannot keep packaging
plugin's trunk. Plugin's trunk is, normally, used for developement and not
stable releases.

Because -extras is currently in this transition, You should obviously expect
some sort of mess. Evnetually, all plugins will have a branch for the
current version (and it's major point version), and (if required), a branch
for the alpha version currently in developement.

This will, as a result, deem trunks obsolete. Unless you want to merge back
from the latest branch back to it when you want to create a new branch.

One last thing to add is that with or without the new svn "restructure",
plugins' trunks will break for people running 0.6 since most of them will be
up'ed to be used with the latest habari HEAD.

-- 
Ali B. / dmondark
http://awhitebox.com


On Thu, Jun 25, 2009 at 9:43 AM, Michael Bishop <[email protected]>wrote:

>
> Might I add, that already there are plugins that have been updated in
> their trunk, and not branched, so we are creating a complete nightmare
> for people to find the right version.
>
> ~miklb
> >
>

--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at http://groups.google.com/group/habari-dev
-~----------~----~----~----~------~----~------~--~---

Reply via email to