I suppose someone could and probably should tgz a copy of each tag and attach it to the wiki for the plugin at: http://trac.symfony-project.com/wiki/sfDoctrinePlugin Although as of now I don't believe we actually have any tags: http://svn.symfony-project.com/plugins/sfDoctrinePlugin/tags/
-- Stephen Ostrow [EMAIL PROTECTED] On Apr 30, 3:37 pm, arhak <[EMAIL PROTECTED]> wrote: > Not working > svn: PROPFIND request failed on '/sfDoctrinePlugin/branches/1.0-sf1.0' > svn: PROPFIND of '/sfDoctrinePlugin/branches/1.0-sf1.0': Could not > resolve hostname `svn.symfony-project.com': Temporary failure in name > resolution (http://svn.symfony-project.com) > > Is not a fault, just unavailable because of local net configuration > > whoiswww.google.com > getaddrinfo(...): Temporary failure in name resolution > > So, please, make something available somehow, nevermind if it's > outdated > > On Apr 29, 8:31 pm, "Jonathan Wage" <[EMAIL PROTECTED]> wrote: > > > It is only available via svn currently :( Sorry > > > What is the problem with getting it via svn? > > > - Jon > > > On Tue, Apr 29, 2008 at 7:28 PM, arhak <[EMAIL PROTECTED]> wrote: > > > > Please, allow some kind of download, ...for any version... I would > > > like to try it (above 0.1 of course) and can't get it through svn, and > > > shouldn't get it through pear. > > > Is there any chance? > > > > On Apr 29, 6:37 pm, "Jonathan Wage" <[EMAIL PROTECTED]> wrote: > > > > Hello all, > > > > > I will be doing some work on the sfDoctrinePlugin for a new version. > > > This > > > > will require that we make some changes to the way things are organized > > > in > > > > svn. I am going to propose a structure for the branches and tags. > > > > > Currently we have sfDoctrinePlugin/branches/0.1 and > > > > sfDoctrinePlugin/branches/1.0, below is an explanation of what each is > > > > currently, and what I want to change it to. > > > > > sfDoctrinePlugin/branches/0.1 - The very first version of the > > > > sfDoctrinePlugin, which is linked to a super outdated version of > > > Doctrine. > > > > This branch likely doesn't even work anymore. I would recommend removing > > > it > > > > completely? > > > > > sfDoctrinePlugin/branches/1.0 - The current stable sfDoctrinePlugin 1.0 > > > that > > > > is compatible with symfony 1.0 > > > > > sfDoctrinePlugin/trunk - The current stable sfDoctrinePlugin 1.0 that is > > > > compatiable with symfony 1.1 > > > > > I want to propose a new structure. > > > > > Rename sfDoctrinePlugin/branches/0.1 to > > > sfDoctrinePlugin/branches/0.1-sf1.0 > > > > Rename sfDoctrinePlugin/branches/1.0 to > > > sfDoctrinePlugin/branches/1.0-sf1.0 > > > > Branch sfDoctrinePlugin/trunk to sfDoctrinePlugin/branches/1.0-sf1.1(I > > > have > > > > already done this) > > > > > Continue development of new version of sfDoctrinePlugin-1.1 compatible > > > with > > > > symfony 1.1 in trunk and when it is done: > > > > > Branch sfDoctrinePlugin/trunk to sfDoctrinePlugin/branches/1.1-sf1.1 > > > > > The naming pattern is "Plugin.Version-sfDependency-Version". Tags would > > > be > > > > pretty much the same except with point releases on the version numbers, > > > i.e. > > > > sfDoctrinePlugin/tags/1.1.2-sf1.1, sfDoctrinePlugin/tags/1.0.2-sf1.1, > > > etc. > > > > > I think having this pattern for all plugins would be a good thing. > > > Thoughts? > > > > > Thanks, Jon > > > > > -- > > > > Jonathan Wagehttp://www.jwage.comhttp://www.centresource.com > > > -- > > Jonathan Wagehttp://www.jwage.comhttp://www.centresource.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
