Difference between revisions of "Talk:Patches Installation"

From ADempiere
Jump to: navigation, search
This Wiki is read-only for reference purposes to avoid broken links.
(Identifying need for patches)
(Identifying need for patches)
Line 13: Line 13:
  
 
The process for installing patches seems clear and simple enough. My question is "how do you know if your installation needs a patch?" --[[User:Vjg|Vjg]] 14:31, 12 January 2008 (EST)
 
The process for installing patches seems clear and simple enough. My question is "how do you know if your installation needs a patch?" --[[User:Vjg|Vjg]] 14:31, 12 January 2008 (EST)
 +
:IMHO all installations needs patches. MS, SUN, Oracle, HP those i have worked with comes with never ending stream of patches. No such thing as a 100% stable software unless it is dead and gone and useless. So my recommendation is to always read the patches section or news in the forum. - [[User:Red1|Red1]] 20:11, 13 January 2008 (EST)

Revision as of 18:11, 13 January 2008

Hi Carlos Ruiz, While u re away, I have moved the patches in SF to its own exclusive and single location for convenience of finding them. I m removing the previous one in the Release Package so that it doesn't obscure the standard release file. Hope it is ok with you. If not, tell me and i will revert. - Red1 21:00, 5 May 2007 (EDT)

Red1, I really didn't understand the changes you did - "KEEP CHANGING WITHOUT REAL IMPROVEMENT OF MEANING." ??? :-) You know what I'm quoting.
I find the convention of date more convenient than alphabet, we don't know how many patches are we going to release, but is very possible more than 26. And date convention is auto-ordered and immediate to know what is the latest.
About putting patch_3.2_20070505.jar besides the release is also to make visible that release is patched (IMHO) - even I was thinking initially to release patches in the same package "Adempiere 3.2.0 Mayday Edition" (that will be direct for anyone downloading the release that is already patched) - So I would prefer to keep the patches closer to the release (or even thinking now that is better in the same release)
And also (this is just for information) that is possible that in future we'll have at the same time patches for 3.2, 3.4, 4.0 and so on (similar to postgres, they are maintaining three main versions at the same time)
CarlosRuiz 23:32, 5 May 2007 (EDT)
I think that Carlos is totally right! And btw - very good installation instructions :) Kthiemann 04:59, 6 May 2007 (EDT)
Yes, alphabet is silly and inadequate as u explained. I will do the date revert. About location, the package naming place Pacthes next door to Package. I think it look nice. Anyway will discuss further, U have final say. I was just beautifying, not changing the meaning. :D - Red1 05:53, 6 May 2007 (EDT)
Looking for a possible path for users -> Open the Release_320 page and follow the link at the end of the page. You don't notice that version is patched. Also there may be more links outside pointing directly to Adempiere 3.2.0 Mayday Edition. So, I'm now strongly convinced that patches must be kept in the same place as release, not a new package. CarlosRuiz 13:23, 6 May 2007 (EDT)

Identifying need for patches

The process for installing patches seems clear and simple enough. My question is "how do you know if your installation needs a patch?" --Vjg 14:31, 12 January 2008 (EST)

IMHO all installations needs patches. MS, SUN, Oracle, HP those i have worked with comes with never ending stream of patches. No such thing as a 100% stable software unless it is dead and gone and useless. So my recommendation is to always read the patches section or news in the forum. - Red1 20:11, 13 January 2008 (EST)