On May 22, 4:44 pm, Owen Winkler <[email protected]> wrote:
> Concerning the issue of trunk: Yes, I think we should abandon trunk
> development for plugins. If development happens in the branch, there's
> no guessing at what version it is and what version of Habari's API it
> targets.
Is that to say that once the branches are up and running, the trunks
should be deleted?
> That said, I think we should avoid an automated process that moves
> everything from trunk to a branch. The reason I say this is because not
> every plugin is compatible with the current Habari version, and there's
> no way to tell if a plugin is being maintained or for what version of
> Habari it might be targeted.
Definitely agreed - it'll take some effort to do, but it's going to
have to be a manual process just to keep things straight and watch for
compatibility. We should manually verify that compatibility before
moving/tagging.
> Manually verifying plugin compatibility and moving seems like a better
> course to me.
Yes, me too :)
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
