Hello I want to send bulk mails

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
16 messages Options
Reply | Threaded
Open this post in threaded view
|

Hello I want to send bulk mails

skpradeepkumar
Hi All,

Can anybody tell me how to send the bulk mails?
I am trying the newsletter functionality in ofbiz, I come to know how to
subscribe. and I want to know how to send the letters to the
subscriber.

--
With regards,
S K Pradeep kumar
Reply | Threaded
Open this post in threaded view
|

Re: Hello I want to send bulk mails

rajsaini
It was discussed sometime back. There is also tip on wiki related to
this. Following links should help you.

http://docs.ofbiz.org/display/OFBIZ/FAQ+-+Tips+-+Tricks+-+Cookbook+-+HowTo#FAQ-Tips-Tricks-Cookbook-HowTo-SendingMailsToContactLists
http://markmail.org/message/v667vuo6djkddggz#query:Ofbiz%20contact%20list%20Raj%20saini+page:1+mid:2kdhmpcw5rl57ymu+state:results

Thanks,

Raj

Pradeep Kumar wrote:
> Hi All,
>
> Can anybody tell me how to send the bulk mails?
> I am trying the newsletter functionality in ofbiz, I come to know how to
> subscribe. and I want to know how to send the letters to the
> subscriber.
>
>  

Reply | Threaded
Open this post in threaded view
|

Re: Hello I want to send bulk mails

skpradeepkumar
Hi,

 Is there any option to filter the contact list? for which we are sending
the mail

On Wed, May 21, 2008 at 9:06 AM, Raj Saini <[hidden email]> wrote:

> It was discussed sometime back. There is also tip on wiki related to this.
> Following links should help you.
>
>
> http://docs.ofbiz.org/display/OFBIZ/FAQ+-+Tips+-+Tricks+-+Cookbook+-+HowTo#FAQ-Tips-Tricks-Cookbook-HowTo-SendingMailsToContactLists
>
> http://markmail.org/message/v667vuo6djkddggz#query:Ofbiz%20contact%20list%20Raj%20saini+page:1+mid:2kdhmpcw5rl57ymu+state:results
>
> Thanks,
>
> Raj
>
>
> Pradeep Kumar wrote:
>
>> Hi All,
>>
>> Can anybody tell me how to send the bulk mails?
>> I am trying the newsletter functionality in ofbiz, I come to know how to
>> subscribe. and I want to know how to send the letters to the
>> subscriber.
>>
>>
>>
>
>


--
With regards,
S K Pradeep kumar
Reply | Threaded
Open this post in threaded view
|

Best stable version for production ecommerce web site

Eric DE MAULDE
Hello,

I have read the documentation
http://docs.ofbiz.org/display/OFBADMIN/Release+Plan
What version is the best for a production ecommerce web site ? Branch
release.4.0

Where is the tag "stable" ?
How can I download / update my package to this tag with subversion ?

Thanks

Eric


Reply | Threaded
Open this post in threaded view
|

Re: Best stable version for production ecommerce web site

Ray Barlow
The release branch would hopefully be more stable, but it will be
missing all of the features added to the main trunk since it branched.
At the end of the day the choice is yours, if you are going to do enough
testing then no reason you can't snapshot the trunk version test what
you need to use, fix (and submit patches) and get the best of the recent
changes.

Re SVN updates read through these for some ideas:
  http://docs.ofbiz.org/x/l
  http://docs.ofbiz.org/x/8gI

Ray

PS: I don't think there is a "stable" tag, just the release branch and
trunk.

PPS: There have been rumours of doing a new release branch sometime
soonish but no commitments on that one!



Eric wrote:

> Hello,
>
> I have read the documentation
> http://docs.ofbiz.org/display/OFBADMIN/Release+Plan
> What version is the best for a production ecommerce web site ? Branch
> release.4.0
>
> Where is the tag "stable" ?
> How can I download / update my package to this tag with subversion ?
>
> Thanks
>
> Eric
>
>
>
Reply | Threaded
Open this post in threaded view
|

Re: Best stable version for production ecommerce web site

Eric DE MAULDE
Thank you very much for your advices

I go to study in order to use and maintain a custom trunk !


> The release branch would hopefully be more stable, but it will be
> missing all of the features added to the main trunk since it branched.
> At the end of the day the choice is yours, if you are going to do enough
> testing then no reason you can't snapshot the trunk version test what
> you need to use, fix (and submit patches) and get the best of the recent
> changes.
>
> Re SVN updates read through these for some ideas:
>  http://docs.ofbiz.org/x/l
>  http://docs.ofbiz.org/x/8gI
>
> Ray
>
> PS: I don't think there is a "stable" tag, just the release branch and
> trunk.
>
> PPS: There have been rumours of doing a new release branch sometime
> soonish but no commitments on that one!
>
>
>
> Eric wrote:
>> Hello,
>>
>> I have read the documentation
>> http://docs.ofbiz.org/display/OFBADMIN/Release+Plan
>> What version is the best for a production ecommerce web site ? Branch
>> release.4.0
>>
>> Where is the tag "stable" ?
>> How can I download / update my package to this tag with subversion ?
>>
>> Thanks
>>
>> Eric
>>
>>
>>
>
>
>
> --
> No virus found in this incoming message.
> Checked by AVG.
> Version: 7.5.524 / Virus Database: 269.24.0/1459 - Release Date:
> 21/05/2008 17:34
>

Reply | Threaded
Open this post in threaded view
|

Re: Best stable version for production ecommerce web site

Adrian Crum
In reply to this post by Ray Barlow
Here is the system I use, for what it's worth:

1. I keep two main patch files - basic_development.patch and
basic_production.patch. Both patch files change the OFBiz configuration
to work with our network environment, each one using settings chosen for
the task - development or production. Only one patch is used at a time.

2. I keep all of my custom development in a single folder under the
ofbiz/applications folder. I avoid touching the trunk code at all costs
- except for the configuration patches mentioned above.

3. To keep my local copy updated, I do an SVN revert (to reverse the
changes made by the patch), then an SVN update, then re-apply the patch.
My custom development folder is untouched by the SVN commands, because
SVN doesn't "know" about the folder.

This works really well and it doesn't involve any complicated merging -
since the configuration files changed by the patches seldom change in
the trunk.

-Adrian

Ray Barlow wrote:

> The release branch would hopefully be more stable, but it will be
> missing all of the features added to the main trunk since it branched.
> At the end of the day the choice is yours, if you are going to do enough
> testing then no reason you can't snapshot the trunk version test what
> you need to use, fix (and submit patches) and get the best of the recent
> changes.
>
> Re SVN updates read through these for some ideas:
>   http://docs.ofbiz.org/x/l
>   http://docs.ofbiz.org/x/8gI
>
> Ray
>
> PS: I don't think there is a "stable" tag, just the release branch and
> trunk.
>
> PPS: There have been rumours of doing a new release branch sometime
> soonish but no commitments on that one!
>
>
>
> Eric wrote:
>> Hello,
>>
>> I have read the documentation
>> http://docs.ofbiz.org/display/OFBADMIN/Release+Plan
>> What version is the best for a production ecommerce web site ? Branch
>> release.4.0
>>
>> Where is the tag "stable" ?
>> How can I download / update my package to this tag with subversion ?
>>
>> Thanks
>>
>> Eric
>>
>>
>>
>
Reply | Threaded
Open this post in threaded view
|

Re: Best stable version for production ecommerce web site

Eric DE MAULDE
Hi,

Do you have a production server working every time (without failure) ?
If an updated version of the trunk contains a bug, what happens ?

Is the following system realistic ?
I develop with a local copy from the OFBiz Trunk.
*** At once this local copy is my working copy (client) from the official
repository (OFBiz trunk server)
        and the server (repository) to my OFBiz production copy  in the
hosting computer.

When I stabilize my local development copy (without bug)
I upate my hosting production copy
Then again I update and stabilize my local development copy
...

Thanks

Eric


> Here is the system I use, for what it's worth:
>
> 1. I keep two main patch files - basic_development.patch and
> basic_production.patch. Both patch files change the OFBiz configuration to
> work with our network environment, each one using settings chosen for the
> task - development or production. Only one patch is used at a time.
>
> 2. I keep all of my custom development in a single folder under the
> ofbiz/applications folder. I avoid touching the trunk code at all costs -
> except for the configuration patches mentioned above.
>
> 3. To keep my local copy updated, I do an SVN revert (to reverse the
> changes made by the patch), then an SVN update, then re-apply the patch.
> My custom development folder is untouched by the SVN commands, because SVN
> doesn't "know" about the folder.
>
> This works really well and it doesn't involve any complicated merging -
> since the configuration files changed by the patches seldom change in the
> trunk.
>
> -Adrian
>
> Ray Barlow wrote:
>> The release branch would hopefully be more stable, but it will be
>> missing all of the features added to the main trunk since it branched.
>> At the end of the day the choice is yours, if you are going to do enough
>> testing then no reason you can't snapshot the trunk version test what
>> you need to use, fix (and submit patches) and get the best of the recent
>> changes.
>>
>> Re SVN updates read through these for some ideas:
>>   http://docs.ofbiz.org/x/l
>>   http://docs.ofbiz.org/x/8gI
>>
>> Ray
>>
>> PS: I don't think there is a "stable" tag, just the release branch and
>> trunk.
>>
>> PPS: There have been rumours of doing a new release branch sometime
>> soonish but no commitments on that one!
>>
>>
>>
>> Eric wrote:
>>> Hello,
>>>
>>> I have read the documentation
>>> http://docs.ofbiz.org/display/OFBADMIN/Release+Plan
>>> What version is the best for a production ecommerce web site ? Branch
>>> release.4.0
>>>
>>> Where is the tag "stable" ?
>>> How can I download / update my package to this tag with subversion ?
>>>
>>> Thanks
>>>
>>> Eric
>>>
>>>
>>>
>>
>
>
>
> --
> No virus found in this incoming message.
> Checked by AVG. Version: 7.5.524 / Virus Database: 269.24.0/1459 - Release
> Date: 21/05/2008 17:34
>
>

Reply | Threaded
Open this post in threaded view
|

Re: Best stable version for production ecommerce web site

Adrian Crum
That's similar to how I do it.

1. Update local copy from the trunk.
2. Apply the development patch.
3. Test the local copy. If all is okay, then
4. Revert local copy, apply production patch.
5. Deploy local copy to the server. I have a script that does an SVN
export, then zips it into a single file. Then I ftp the zipped file to
the server and unzip it.

-Adrian

Eric DE MAULDE wrote:

> Hi,
>
> Do you have a production server working every time (without failure) ?
> If an updated version of the trunk contains a bug, what happens ?
>
> Is the following system realistic ?
> I develop with a local copy from the OFBiz Trunk.
> *** At once this local copy is my working copy (client) from the
> official repository (OFBiz trunk server)
>        and the server (repository) to my OFBiz production copy  in the
> hosting computer.
>
> When I stabilize my local development copy (without bug)
> I upate my hosting production copy
> Then again I update and stabilize my local development copy
> ...
>
> Thanks
>
> Eric
>
>
>> Here is the system I use, for what it's worth:
>>
>> 1. I keep two main patch files - basic_development.patch and
>> basic_production.patch. Both patch files change the OFBiz
>> configuration to work with our network environment, each one using
>> settings chosen for the task - development or production. Only one
>> patch is used at a time.
>>
>> 2. I keep all of my custom development in a single folder under the
>> ofbiz/applications folder. I avoid touching the trunk code at all
>> costs - except for the configuration patches mentioned above.
>>
>> 3. To keep my local copy updated, I do an SVN revert (to reverse the
>> changes made by the patch), then an SVN update, then re-apply the
>> patch. My custom development folder is untouched by the SVN commands,
>> because SVN doesn't "know" about the folder.
>>
>> This works really well and it doesn't involve any complicated merging
>> - since the configuration files changed by the patches seldom change
>> in the trunk.
>>
>> -Adrian
>>
>> Ray Barlow wrote:
>>> The release branch would hopefully be more stable, but it will be
>>> missing all of the features added to the main trunk since it branched.
>>> At the end of the day the choice is yours, if you are going to do enough
>>> testing then no reason you can't snapshot the trunk version test what
>>> you need to use, fix (and submit patches) and get the best of the recent
>>> changes.
>>>
>>> Re SVN updates read through these for some ideas:
>>>   http://docs.ofbiz.org/x/l
>>>   http://docs.ofbiz.org/x/8gI
>>>
>>> Ray
>>>
>>> PS: I don't think there is a "stable" tag, just the release branch and
>>> trunk.
>>>
>>> PPS: There have been rumours of doing a new release branch sometime
>>> soonish but no commitments on that one!
>>>
>>>
>>>
>>> Eric wrote:
>>>> Hello,
>>>>
>>>> I have read the documentation
>>>> http://docs.ofbiz.org/display/OFBADMIN/Release+Plan
>>>> What version is the best for a production ecommerce web site ? Branch
>>>> release.4.0
>>>>
>>>> Where is the tag "stable" ?
>>>> How can I download / update my package to this tag with subversion ?
>>>>
>>>> Thanks
>>>>
>>>> Eric
>>>>
>>>>
>>>>
>>>
>>
>>
>>
>> --
>> No virus found in this incoming message.
>> Checked by AVG. Version: 7.5.524 / Virus Database: 269.24.0/1459 -
>> Release Date: 21/05/2008 17:34
>>
>>
>
>
Reply | Threaded
Open this post in threaded view
|

Re: Best stable version for production ecommerce web site

Jacques Le Roux
Administrator
Adrian,

Maybe we could create a hat page for

http://docs.ofbiz.org/x/l
http://docs.ofbiz.org/x/8gI

in Wiki and add your interesting suggestions below ?

Jacques

From: "Adrian Crum" <[hidden email]>

> That's similar to how I do it.
>
> 1. Update local copy from the trunk.
> 2. Apply the development patch.
> 3. Test the local copy. If all is okay, then
> 4. Revert local copy, apply production patch.
> 5. Deploy local copy to the server. I have a script that does an SVN
> export, then zips it into a single file. Then I ftp the zipped file to
> the server and unzip it.
>
> -Adrian
>
> Eric DE MAULDE wrote:
>> Hi,
>>
>> Do you have a production server working every time (without failure) ?
>> If an updated version of the trunk contains a bug, what happens ?
>>
>> Is the following system realistic ?
>> I develop with a local copy from the OFBiz Trunk.
>> *** At once this local copy is my working copy (client) from the
>> official repository (OFBiz trunk server)
>>        and the server (repository) to my OFBiz production copy  in the
>> hosting computer.
>>
>> When I stabilize my local development copy (without bug)
>> I upate my hosting production copy
>> Then again I update and stabilize my local development copy
>> ...
>>
>> Thanks
>>
>> Eric
>>
>>
>>> Here is the system I use, for what it's worth:
>>>
>>> 1. I keep two main patch files - basic_development.patch and
>>> basic_production.patch. Both patch files change the OFBiz
>>> configuration to work with our network environment, each one using
>>> settings chosen for the task - development or production. Only one
>>> patch is used at a time.
>>>
>>> 2. I keep all of my custom development in a single folder under the
>>> ofbiz/applications folder. I avoid touching the trunk code at all
>>> costs - except for the configuration patches mentioned above.
>>>
>>> 3. To keep my local copy updated, I do an SVN revert (to reverse the
>>> changes made by the patch), then an SVN update, then re-apply the
>>> patch. My custom development folder is untouched by the SVN commands,
>>> because SVN doesn't "know" about the folder.
>>>
>>> This works really well and it doesn't involve any complicated merging
>>> - since the configuration files changed by the patches seldom change
>>> in the trunk.
>>>
>>> -Adrian
>>>
>>> Ray Barlow wrote:
>>>> The release branch would hopefully be more stable, but it will be
>>>> missing all of the features added to the main trunk since it branched.
>>>> At the end of the day the choice is yours, if you are going to do enough
>>>> testing then no reason you can't snapshot the trunk version test what
>>>> you need to use, fix (and submit patches) and get the best of the recent
>>>> changes.
>>>>
>>>> Re SVN updates read through these for some ideas:
>>>>   http://docs.ofbiz.org/x/l
>>>>   http://docs.ofbiz.org/x/8gI
>>>>
>>>> Ray
>>>>
>>>> PS: I don't think there is a "stable" tag, just the release branch and
>>>> trunk.
>>>>
>>>> PPS: There have been rumours of doing a new release branch sometime
>>>> soonish but no commitments on that one!
>>>>
>>>>
>>>>
>>>> Eric wrote:
>>>>> Hello,
>>>>>
>>>>> I have read the documentation
>>>>> http://docs.ofbiz.org/display/OFBADMIN/Release+Plan
>>>>> What version is the best for a production ecommerce web site ? Branch
>>>>> release.4.0
>>>>>
>>>>> Where is the tag "stable" ?
>>>>> How can I download / update my package to this tag with subversion ?
>>>>>
>>>>> Thanks
>>>>>
>>>>> Eric
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> No virus found in this incoming message.
>>> Checked by AVG. Version: 7.5.524 / Virus Database: 269.24.0/1459 -
>>> Release Date: 21/05/2008 17:34
>>>
>>>
>>
>>
>
Reply | Threaded
Open this post in threaded view
|

Re: Best stable version for production ecommerce web site

Adrian Crum
If anyone finds it useful, sure - go ahead.

The funny thing is, when I first got started with OFBiz I didn't ask
anyone how they were doing it. I came up with this system on my own, so
I don't know if it's good or bad.

-Adrian

Jacques Le Roux wrote:

> Adrian,
>
> Maybe we could create a hat page for
>
> http://docs.ofbiz.org/x/l
> http://docs.ofbiz.org/x/8gI
>
> in Wiki and add your interesting suggestions below ?
>
> Jacques
>
> From: "Adrian Crum" <[hidden email]>
>> That's similar to how I do it.
>>
>> 1. Update local copy from the trunk.
>> 2. Apply the development patch.
>> 3. Test the local copy. If all is okay, then
>> 4. Revert local copy, apply production patch.
>> 5. Deploy local copy to the server. I have a script that does an SVN
>> export, then zips it into a single file. Then I ftp the zipped file to
>> the server and unzip it.
>>
>> -Adrian
>>
>> Eric DE MAULDE wrote:
>>> Hi,
>>>
>>> Do you have a production server working every time (without failure) ?
>>> If an updated version of the trunk contains a bug, what happens ?
>>>
>>> Is the following system realistic ?
>>> I develop with a local copy from the OFBiz Trunk.
>>> *** At once this local copy is my working copy (client) from the
>>> official repository (OFBiz trunk server)
>>>        and the server (repository) to my OFBiz production copy  in
>>> the hosting computer.
>>>
>>> When I stabilize my local development copy (without bug)
>>> I upate my hosting production copy
>>> Then again I update and stabilize my local development copy
>>> ...
>>>
>>> Thanks
>>>
>>> Eric
>>>
>>>
>>>> Here is the system I use, for what it's worth:
>>>>
>>>> 1. I keep two main patch files - basic_development.patch and
>>>> basic_production.patch. Both patch files change the OFBiz
>>>> configuration to work with our network environment, each one using
>>>> settings chosen for the task - development or production. Only one
>>>> patch is used at a time.
>>>>
>>>> 2. I keep all of my custom development in a single folder under the
>>>> ofbiz/applications folder. I avoid touching the trunk code at all
>>>> costs - except for the configuration patches mentioned above.
>>>>
>>>> 3. To keep my local copy updated, I do an SVN revert (to reverse the
>>>> changes made by the patch), then an SVN update, then re-apply the
>>>> patch. My custom development folder is untouched by the SVN
>>>> commands, because SVN doesn't "know" about the folder.
>>>>
>>>> This works really well and it doesn't involve any complicated
>>>> merging - since the configuration files changed by the patches
>>>> seldom change in the trunk.
>>>>
>>>> -Adrian
>>>>
>>>> Ray Barlow wrote:
>>>>> The release branch would hopefully be more stable, but it will be
>>>>> missing all of the features added to the main trunk since it branched.
>>>>> At the end of the day the choice is yours, if you are going to do
>>>>> enough
>>>>> testing then no reason you can't snapshot the trunk version test what
>>>>> you need to use, fix (and submit patches) and get the best of the
>>>>> recent
>>>>> changes.
>>>>>
>>>>> Re SVN updates read through these for some ideas:
>>>>>   http://docs.ofbiz.org/x/l
>>>>>   http://docs.ofbiz.org/x/8gI
>>>>>
>>>>> Ray
>>>>>
>>>>> PS: I don't think there is a "stable" tag, just the release branch and
>>>>> trunk.
>>>>>
>>>>> PPS: There have been rumours of doing a new release branch sometime
>>>>> soonish but no commitments on that one!
>>>>>
>>>>>
>>>>>
>>>>> Eric wrote:
>>>>>> Hello,
>>>>>>
>>>>>> I have read the documentation
>>>>>> http://docs.ofbiz.org/display/OFBADMIN/Release+Plan
>>>>>> What version is the best for a production ecommerce web site ? Branch
>>>>>> release.4.0
>>>>>>
>>>>>> Where is the tag "stable" ?
>>>>>> How can I download / update my package to this tag with subversion ?
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> Eric
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> No virus found in this incoming message.
>>>> Checked by AVG. Version: 7.5.524 / Virus Database: 269.24.0/1459 -
>>>> Release Date: 21/05/2008 17:34
>>>>
>>>>
>>>
>>>
>>
>
Reply | Threaded
Open this post in threaded view
|

Re: Best stable version for production ecommerce web site

Jacques Le Roux
Administrator
I think Andrew Sykes was doing something very near. I will create a page under the hat page suggested...

Jacques

From: "Adrian Crum" <[hidden email]>

> If anyone finds it useful, sure - go ahead.
>
> The funny thing is, when I first got started with OFBiz I didn't ask
> anyone how they were doing it. I came up with this system on my own, so
> I don't know if it's good or bad.
>
> -Adrian
>
> Jacques Le Roux wrote:
>> Adrian,
>>
>> Maybe we could create a hat page for
>>
>> http://docs.ofbiz.org/x/l
>> http://docs.ofbiz.org/x/8gI
>>
>> in Wiki and add your interesting suggestions below ?
>>
>> Jacques
>>
>> From: "Adrian Crum" <[hidden email]>
>>> That's similar to how I do it.
>>>
>>> 1. Update local copy from the trunk.
>>> 2. Apply the development patch.
>>> 3. Test the local copy. If all is okay, then
>>> 4. Revert local copy, apply production patch.
>>> 5. Deploy local copy to the server. I have a script that does an SVN
>>> export, then zips it into a single file. Then I ftp the zipped file to
>>> the server and unzip it.
>>>
>>> -Adrian
>>>
>>> Eric DE MAULDE wrote:
>>>> Hi,
>>>>
>>>> Do you have a production server working every time (without failure) ?
>>>> If an updated version of the trunk contains a bug, what happens ?
>>>>
>>>> Is the following system realistic ?
>>>> I develop with a local copy from the OFBiz Trunk.
>>>> *** At once this local copy is my working copy (client) from the
>>>> official repository (OFBiz trunk server)
>>>>        and the server (repository) to my OFBiz production copy  in
>>>> the hosting computer.
>>>>
>>>> When I stabilize my local development copy (without bug)
>>>> I upate my hosting production copy
>>>> Then again I update and stabilize my local development copy
>>>> ...
>>>>
>>>> Thanks
>>>>
>>>> Eric
>>>>
>>>>
>>>>> Here is the system I use, for what it's worth:
>>>>>
>>>>> 1. I keep two main patch files - basic_development.patch and
>>>>> basic_production.patch. Both patch files change the OFBiz
>>>>> configuration to work with our network environment, each one using
>>>>> settings chosen for the task - development or production. Only one
>>>>> patch is used at a time.
>>>>>
>>>>> 2. I keep all of my custom development in a single folder under the
>>>>> ofbiz/applications folder. I avoid touching the trunk code at all
>>>>> costs - except for the configuration patches mentioned above.
>>>>>
>>>>> 3. To keep my local copy updated, I do an SVN revert (to reverse the
>>>>> changes made by the patch), then an SVN update, then re-apply the
>>>>> patch. My custom development folder is untouched by the SVN
>>>>> commands, because SVN doesn't "know" about the folder.
>>>>>
>>>>> This works really well and it doesn't involve any complicated
>>>>> merging - since the configuration files changed by the patches
>>>>> seldom change in the trunk.
>>>>>
>>>>> -Adrian
>>>>>
>>>>> Ray Barlow wrote:
>>>>>> The release branch would hopefully be more stable, but it will be
>>>>>> missing all of the features added to the main trunk since it branched.
>>>>>> At the end of the day the choice is yours, if you are going to do
>>>>>> enough
>>>>>> testing then no reason you can't snapshot the trunk version test what
>>>>>> you need to use, fix (and submit patches) and get the best of the
>>>>>> recent
>>>>>> changes.
>>>>>>
>>>>>> Re SVN updates read through these for some ideas:
>>>>>>   http://docs.ofbiz.org/x/l
>>>>>>   http://docs.ofbiz.org/x/8gI
>>>>>>
>>>>>> Ray
>>>>>>
>>>>>> PS: I don't think there is a "stable" tag, just the release branch and
>>>>>> trunk.
>>>>>>
>>>>>> PPS: There have been rumours of doing a new release branch sometime
>>>>>> soonish but no commitments on that one!
>>>>>>
>>>>>>
>>>>>>
>>>>>> Eric wrote:
>>>>>>> Hello,
>>>>>>>
>>>>>>> I have read the documentation
>>>>>>> http://docs.ofbiz.org/display/OFBADMIN/Release+Plan
>>>>>>> What version is the best for a production ecommerce web site ? Branch
>>>>>>> release.4.0
>>>>>>>
>>>>>>> Where is the tag "stable" ?
>>>>>>> How can I download / update my package to this tag with subversion ?
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>> Eric
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> No virus found in this incoming message.
>>>>> Checked by AVG. Version: 7.5.524 / Virus Database: 269.24.0/1459 -
>>>>> Release Date: 21/05/2008 17:34
>>>>>
>>>>>
>>>>
>>>>
>>>
>>
>
Reply | Threaded
Open this post in threaded view
|

Re: Best stable version for production ecommerce web site

Ray Barlow
In reply to this post by Adrian Crum
Adrian,

When I thought through your method more and under what circumstances I
might adopt it I was a little unsure as to whether you do any source
control on your own changes other than effectively creating the patch.
Personally I like to have my mods committed to a source control system
as well so I can see history and manage change etc but wasn't sure if
you are doing that and how?

I suppose as your custom app is not part of the standard SVN it could be
added to another local SVN server...although if you want to get the
product version on another machine you've got to checkout a specific
trunk revision that you need to document somewhere as well as apply the
production patch and checkout the custom app SVN which could be tagged
in the local SVN.

Sorry Adrian email is rambling a bit as I think aloud. I like your idea
as it is certainly simper and as Jacques suggested it's good to add to
the list of options people can look at because it's very much an area
where people can choose to use a method that suits them or even
different for different projects.

Thanks,

Ray


Adrian Crum wrote:

>>> Here is the system I use, for what it's worth:
>>>
>>> 1. I keep two main patch files - basic_development.patch and
>>> basic_production.patch. Both patch files change the OFBiz
>>> configuration to work with our network environment, each one using
>>> settings chosen for the task - development or production. Only one
>>> patch is used at a time.
>>>
>>> 2. I keep all of my custom development in a single folder under the
>>> ofbiz/applications folder. I avoid touching the trunk code at all
>>> costs - except for the configuration patches mentioned above.
>>>
>>> 3. To keep my local copy updated, I do an SVN revert (to reverse the
>>> changes made by the patch), then an SVN update, then re-apply the
>>> patch. My custom development folder is untouched by the SVN
>>> commands, because SVN doesn't "know" about the folder.
>>>
>>> This works really well and it doesn't involve any complicated
>>> merging - since the configuration files changed by the patches
>>> seldom change in the trunk.
>>>
>>> -Adrian
>>>
Reply | Threaded
Open this post in threaded view
|

Re: Best stable version for production ecommerce web site

Adrian Crum
The folder that contains our custom code is kept in a local SVN repository.

-Adrian

Ray Barlow wrote:

> Adrian,
>
> When I thought through your method more and under what circumstances I
> might adopt it I was a little unsure as to whether you do any source
> control on your own changes other than effectively creating the patch.
> Personally I like to have my mods committed to a source control system
> as well so I can see history and manage change etc but wasn't sure if
> you are doing that and how?
>
> I suppose as your custom app is not part of the standard SVN it could be
> added to another local SVN server...although if you want to get the
> product version on another machine you've got to checkout a specific
> trunk revision that you need to document somewhere as well as apply the
> production patch and checkout the custom app SVN which could be tagged
> in the local SVN.
>
> Sorry Adrian email is rambling a bit as I think aloud. I like your idea
> as it is certainly simper and as Jacques suggested it's good to add to
> the list of options people can look at because it's very much an area
> where people can choose to use a method that suits them or even
> different for different projects.
>
> Thanks,
>
> Ray
>
>
> Adrian Crum wrote:
>>>> Here is the system I use, for what it's worth:
>>>>
>>>> 1. I keep two main patch files - basic_development.patch and
>>>> basic_production.patch. Both patch files change the OFBiz
>>>> configuration to work with our network environment, each one using
>>>> settings chosen for the task - development or production. Only one
>>>> patch is used at a time.
>>>>
>>>> 2. I keep all of my custom development in a single folder under the
>>>> ofbiz/applications folder. I avoid touching the trunk code at all
>>>> costs - except for the configuration patches mentioned above.
>>>>
>>>> 3. To keep my local copy updated, I do an SVN revert (to reverse the
>>>> changes made by the patch), then an SVN update, then re-apply the
>>>> patch. My custom development folder is untouched by the SVN
>>>> commands, because SVN doesn't "know" about the folder.
>>>>
>>>> This works really well and it doesn't involve any complicated
>>>> merging - since the configuration files changed by the patches
>>>> seldom change in the trunk.
>>>>
>>>> -Adrian
>>>>
>
Reply | Threaded
Open this post in threaded view
|

Re: Best stable version for production ecommerce web site

Bruno Busco
I like this production/development patching system, I was also looking for
an efficient way to follow ofbiz improvements while keeping my own
modifications, great!

BTW I find some difficulties working with binary files and patches (sorry if
OT); for instance my development patch should add to my working copy the
mysql-connector-java-5.1.5-bin.jar file in the entity lib folder.

I cannot make TortoiseSVN patch command to handle this; in the patch file I
find:

Index: entity/lib/jdbc/mysql-connector-java-5.1.5-bin.jar
===================================================================
Cannot display: file marked as a binary type.
svn:mime-type = application/octet-stream

Property changes on: entity\lib\jdbc\mysql-connector-java-5.1.5-bin.jar
___________________________________________________________________
Name: svn:mime-type
   + application/octet-stream

Do you think this is something that can be fixed? Or should I go with a
batch file that applies the patch for the text files and than add binary
files by copying them?

Thank you,
-Bruno

2008/5/23 Adrian Crum <[hidden email]>:

> The folder that contains our custom code is kept in a local SVN repository.
>
> -Adrian
>
>
> Ray Barlow wrote:
>
>> Adrian,
>>
>> When I thought through your method more and under what circumstances I
>> might adopt it I was a little unsure as to whether you do any source
>> control on your own changes other than effectively creating the patch.
>> Personally I like to have my mods committed to a source control system
>> as well so I can see history and manage change etc but wasn't sure if
>> you are doing that and how?
>>
>> I suppose as your custom app is not part of the standard SVN it could be
>> added to another local SVN server...although if you want to get the
>> product version on another machine you've got to checkout a specific
>> trunk revision that you need to document somewhere as well as apply the
>> production patch and checkout the custom app SVN which could be tagged
>> in the local SVN.
>>
>> Sorry Adrian email is rambling a bit as I think aloud. I like your idea
>> as it is certainly simper and as Jacques suggested it's good to add to
>> the list of options people can look at because it's very much an area
>> where people can choose to use a method that suits them or even
>> different for different projects.
>>
>> Thanks,
>>
>> Ray
>>
>>
>> Adrian Crum wrote:
>>
>>> Here is the system I use, for what it's worth:
>>>>>
>>>>> 1. I keep two main patch files - basic_development.patch and
>>>>> basic_production.patch. Both patch files change the OFBiz
>>>>> configuration to work with our network environment, each one using
>>>>> settings chosen for the task - development or production. Only one
>>>>> patch is used at a time.
>>>>>
>>>>> 2. I keep all of my custom development in a single folder under the
>>>>> ofbiz/applications folder. I avoid touching the trunk code at all
>>>>> costs - except for the configuration patches mentioned above.
>>>>>
>>>>> 3. To keep my local copy updated, I do an SVN revert (to reverse the
>>>>> changes made by the patch), then an SVN update, then re-apply the
>>>>> patch. My custom development folder is untouched by the SVN
>>>>> commands, because SVN doesn't "know" about the folder.
>>>>>
>>>>> This works really well and it doesn't involve any complicated
>>>>> merging - since the configuration files changed by the patches
>>>>> seldom change in the trunk.
>>>>>
>>>>> -Adrian
>>>>>
>>>>>
>>
Reply | Threaded
Open this post in threaded view
|

Re: Best stable version for production ecommerce web site

Jacques Le Roux
Administrator
In reply to this post by Jacques Le Roux
Done at
http://docs.ofbiz.org/display/OFBIZ/FAQ+-+Tips+-+Tricks+-+Cookbook+-+HowTo#FAQ-Tips-Tricks-Cookbook-HowTo-Howtomanageyoursourcedifferences

Jacques

From: "Jacques Le Roux" <[hidden email]>

>I think Andrew Sykes was doing something very near. I will create a page under the hat page suggested...
>
> Jacques
>
> From: "Adrian Crum" <[hidden email]>
>> If anyone finds it useful, sure - go ahead.
>>
>> The funny thing is, when I first got started with OFBiz I didn't ask anyone how they were doing it. I came up with this system on
>> my own, so I don't know if it's good or bad.
>>
>> -Adrian
>>
>> Jacques Le Roux wrote:
>>> Adrian,
>>>
>>> Maybe we could create a hat page for
>>>
>>> http://docs.ofbiz.org/x/l
>>> http://docs.ofbiz.org/x/8gI
>>>
>>> in Wiki and add your interesting suggestions below ?
>>>
>>> Jacques
>>>
>>> From: "Adrian Crum" <[hidden email]>
>>>> That's similar to how I do it.
>>>>
>>>> 1. Update local copy from the trunk.
>>>> 2. Apply the development patch.
>>>> 3. Test the local copy. If all is okay, then
>>>> 4. Revert local copy, apply production patch.
>>>> 5. Deploy local copy to the server. I have a script that does an SVN export, then zips it into a single file. Then I ftp the
>>>> zipped file to the server and unzip it.
>>>>
>>>> -Adrian
>>>>
>>>> Eric DE MAULDE wrote:
>>>>> Hi,
>>>>>
>>>>> Do you have a production server working every time (without failure) ?
>>>>> If an updated version of the trunk contains a bug, what happens ?
>>>>>
>>>>> Is the following system realistic ?
>>>>> I develop with a local copy from the OFBiz Trunk.
>>>>> *** At once this local copy is my working copy (client) from the official repository (OFBiz trunk server)
>>>>>        and the server (repository) to my OFBiz production copy  in the hosting computer.
>>>>>
>>>>> When I stabilize my local development copy (without bug)
>>>>> I upate my hosting production copy
>>>>> Then again I update and stabilize my local development copy
>>>>> ...
>>>>>
>>>>> Thanks
>>>>>
>>>>> Eric
>>>>>
>>>>>
>>>>>> Here is the system I use, for what it's worth:
>>>>>>
>>>>>> 1. I keep two main patch files - basic_development.patch and basic_production.patch. Both patch files change the OFBiz
>>>>>> configuration to work with our network environment, each one using settings chosen for the task - development or production.
>>>>>> Only one patch is used at a time.
>>>>>>
>>>>>> 2. I keep all of my custom development in a single folder under the ofbiz/applications folder. I avoid touching the trunk
>>>>>> code at all costs - except for the configuration patches mentioned above.
>>>>>>
>>>>>> 3. To keep my local copy updated, I do an SVN revert (to reverse the changes made by the patch), then an SVN update, then
>>>>>> re-apply the patch. My custom development folder is untouched by the SVN commands, because SVN doesn't "know" about the
>>>>>> folder.
>>>>>>
>>>>>> This works really well and it doesn't involve any complicated merging - since the configuration files changed by the patches
>>>>>> seldom change in the trunk.
>>>>>>
>>>>>> -Adrian
>>>>>>
>>>>>> Ray Barlow wrote:
>>>>>>> The release branch would hopefully be more stable, but it will be
>>>>>>> missing all of the features added to the main trunk since it branched.
>>>>>>> At the end of the day the choice is yours, if you are going to do enough
>>>>>>> testing then no reason you can't snapshot the trunk version test what
>>>>>>> you need to use, fix (and submit patches) and get the best of the recent
>>>>>>> changes.
>>>>>>>
>>>>>>> Re SVN updates read through these for some ideas:
>>>>>>>   http://docs.ofbiz.org/x/l
>>>>>>>   http://docs.ofbiz.org/x/8gI
>>>>>>>
>>>>>>> Ray
>>>>>>>
>>>>>>> PS: I don't think there is a "stable" tag, just the release branch and
>>>>>>> trunk.
>>>>>>>
>>>>>>> PPS: There have been rumours of doing a new release branch sometime
>>>>>>> soonish but no commitments on that one!
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Eric wrote:
>>>>>>>> Hello,
>>>>>>>>
>>>>>>>> I have read the documentation
>>>>>>>> http://docs.ofbiz.org/display/OFBADMIN/Release+Plan
>>>>>>>> What version is the best for a production ecommerce web site ? Branch
>>>>>>>> release.4.0
>>>>>>>>
>>>>>>>> Where is the tag "stable" ?
>>>>>>>> How can I download / update my package to this tag with subversion ?
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>>
>>>>>>>> Eric
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> No virus found in this incoming message.
>>>>>> Checked by AVG. Version: 7.5.524 / Virus Database: 269.24.0/1459 - Release Date: 21/05/2008 17:34
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>