You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ofbiz.apache.org by Jacopo Cappellato <ti...@sastau.it> on 2006/12/28 08:57:30 UTC

Community supported releases WAS [Re: Properly edited OFBiz manuals]

David E Jones wrote:
> 
> ...
> Still, the first priority after graduation is to do a community 
> supported branch "release". Again given the size of OFBiz relative to 
> the size of the community, we don't have resources to do a full QA pass 
> before issuing a release, so the release process for OFBiz will be 
> centered around a community effort to maintain a branch that will have 
> bug fixes, but not new features, as anything would be maintained with a 
> priority of stability over progress (new features, etc).
> 

Are we sure this is the best way to go? My fear is that no one will ever 
maintain these releases (submitting patches for them etc.).
A slightly different approach could be this:

1) we issue releases regularly and very often, let's say once every two 
months
2) each release will not undergo a full QA pass, however we will try to 
issue it when the code is pretty stable (e.g. not immediately after a 
big refactoring)
3) every time we do changes in the trunk that could cause backward 
compatibility issues (changes to the existing data model, seed data, 
jars etc...), we document them somewhere and if possible we provide 
upgrade scripts or instructions (in order to upgrade from the latest 
release only); when a release is done, these instructions are delivered 
with it ("Upgrade notes from release X to new release X+1").

I think this approach (with its pros and cons) is easier to maintain by 
the OFBiz community (because it's not so different from what we are 
doing now) and could be acceptable by the OFBiz's users (because it's 
similar to what most users are doing now, i.e. staying up-to-date with 
the trunk to minimize upgrade costs).

Jacopo

Re: Community supported releases WAS [Re: Properly edited OFBiz manuals]

Posted by David E Jones <jo...@undersunconsulting.com>.
On Dec 28, 2006, at 2:38 AM, Scott Gray wrote:

> Hi Jacopo, David
>
> I would just as happily submit patches for releases as I do for the  
> trunk, and perhaps we should just assume the community can handle  
> it until we are proven otherwise?  I would expect that we could  
> handle the first release easily, and it would just get harder as  
> the number of releases increases?

This is exactly what I'm hoping for... and I agree that things would  
get harder as the number of release branches increases so we'd want  
to do something to minimize this. Like I mentioned in the email I  
just wrote a somewhat happy medium might be doing a new release  
branch from the trunk once per year.

-David


>
> Regards
> Scott
>
> Jacopo Cappellato wrote:
>> Of course it would also be great to have a real 'stable' releases  
>> (with patches for them etc...) as you are suggesting (and I really  
>> think we could implement the two approaches simultaneously since  
>> what I've proposed could be the basis of a real release  
>> management) but I'm not sure the community will really maintain  
>> them...
>


Re: Community supported releases WAS [Re: Properly edited OFBiz manuals]

Posted by Scott Gray <le...@gmail.com>.
Hi Jacopo, David

I would just as happily submit patches for releases as I do for the 
trunk, and perhaps we should just assume the community can handle it 
until we are proven otherwise?  I would expect that we could handle the 
first release easily, and it would just get harder as the number of 
releases increases?

Regards
Scott

Jacopo Cappellato wrote:
> Of course it would also be great to have a real 'stable' releases 
> (with patches for them etc...) as you are suggesting (and I really 
> think we could implement the two approaches simultaneously since what 
> I've proposed could be the basis of a real release management) but I'm 
> not sure the community will really maintain them...


Re: Community supported releases WAS [Re: Properly edited OFBiz manuals]

Posted by Jacques Le Roux <ja...@les7arts.com>.
Walter,

Of course I was not thinking of changing that's already exist :
SVN trunk will be always available...

Jacques

----- Original Message ----- 
From: "Walter Vaughan" <wv...@steelerubber.com>
To: <of...@incubator.apache.org>
Sent: Friday, December 29, 2006 2:54 AM
Subject: Re: Community supported releases WAS [Re: Properly edited OFBiz manuals]


> [..snip..]
> 
> Golly, what a can of worms is open here. Actually what drew me to ofBiz was the 
> amount of updates to the system.
> 
> The last commercial ERP solution we considered was SYSPRO. The folks at Syspro 
> PRIDE themselves on weekly ports to their software. I have/had an .iso of a 
> marketing DVD they have with almost two hours of non-stop preaching how ERP 
> systems must and should be updated on a continuous basis, and that point release 
> updates are evil. (e.g. 5.0 -> 6.0 on done every 18 months)
> 
> I was sold. Couldn't justify the seat costs for the number I needed, but I was 
> sold on the concept. During our courting period I also got a weekly email that 
> was similar to what Si Chen does with his blog listing the dozen or so 
> improvements to the system in the past week, and this in an ERP system with 
> 15,000 current installs.
> 
> As a end user, what I am looking for is non-failure. Thus far I have more than 
> enough trust in the core developers to always do the right thing.
> 
> --
> Walter
> 
> 

Re: Community supported releases WAS [Re: Properly edited OFBiz manuals]

Posted by David E Jones <jo...@undersunconsulting.com>.
On Dec 28, 2006, at 6:54 PM, Walter Vaughan wrote:

> [..snip..]
>
> Golly, what a can of worms is open here. Actually what drew me to  
> ofBiz was the amount of updates to the system.
>
> The last commercial ERP solution we considered was SYSPRO. The  
> folks at Syspro PRIDE themselves on weekly ports to their software.  
> I have/had an .iso of a marketing DVD they have with almost two  
> hours of non-stop preaching how ERP systems must and should be  
> updated on a continuous basis, and that point release updates are  
> evil. (e.g. 5.0 -> 6.0 on done every 18 months)
>
> I was sold. Couldn't justify the seat costs for the number I  
> needed, but I was sold on the concept. During our courting period I  
> also got a weekly email that was similar to what Si Chen does with  
> his blog listing the dozen or so improvements to the system in the  
> past week, and this in an ERP system with 15,000 current installs.
>
> As a end user, what I am looking for is non-failure. Thus far I  
> have more than enough trust in the core developers to always do the  
> right thing.

I think this really comes down to community needs. There is and  
always will be a trunk moving forward with both new features and bug  
fixes and we'll always want to keep it as stable as possible, and  
people can update whenever they want to.

This is another reason I like the idea of a long period between  
creating new release branches: developers will hopefully never think  
that they can commit something risky without checking it out thinking  
that it won't affect anyone...

Still, I think there is enough demand in the community for periodic  
releases. There is also a marketing aspect here that I think is  
important, especially as we get out as a real ASF project and are  
wanting to attract new users as well as help other people get an idea  
of what OFBiz is all about.

-David


Re: Community supported releases WAS [Re: Properly edited OFBiz manuals]

Posted by Jacques Le Roux <ja...@les7arts.com>.
I agree with Jacopo,

I have put in place a task that update OFBiz automatically. Actually I have 3 versions of OFBiz :
  std trunk
  for POS - I do most of my modifications there
  with Opentaps modules

I run by hand ant or ant run-install for each of them suiving if they are new data or not. It takes me less than 10' per day (and
during this elapse most of this time I do other tasks)

If someone is interested here is the batch I use on XP for that

__________________________________________________________________________________________________
@Echo off
d:
cd \WorkspaceNew\ofbiz
ECHO ofbiz======================================================================
call svn up
ECHO ofbiz======================================================================
ECHO                                                                           *
ECHO                                                                           *
cd \WorkspaceNew\ofbiz.pos
ECHO ofbiz.pos==================================================================
call svn up
ECHO ofbiz.pos==================================================================
ECHO                                                                           *
ECHO                                                                           *
cd \WorkspaceNew\opentaps
ECHO opentaps===================================================================
call svn up
cd \WorkspaceNew\opentaps\hot-deploy\crmsfa
call svn up
cd \WorkspaceNew\opentaps\hot-deploy\financials
call svn up
ECHO opentaps===================================================================
ECHO                                                                           *
ECHO                                                                           *

:menu
echo a) ant
echo b) install
echo q) quitter
choice /c:abq Quelle option ?
if errorlevel = 3 goto fin
if errorlevel = 2 goto install
if errorlevel = 1 goto ant

:ant
cd \WorkspaceNew\ofbiz
call ant
pause ofbiz ok ?
cd \WorkspaceNew\ofbiz.pos
call ant
pause ofbiz.pos ok ?
cd \WorkspaceNew\opentaps
call ant
pause opentaps ok ?
goto fin

:install
cd \WorkspaceNew\ofbiz
call ant run-install
pause ofbiz ok ?
cd \WorkspaceNew\ofbiz.pos
call ant run-install
pause ofbiz.pos ok ?
cd \WorkspaceNew\opentaps
call ant run-install
pause opentaps ok ?

:fin
__________________________________________________________________________________________________

Before the choise I have only to search for the token "data" and that's it.
This may be adapted easily even in a .sh I guess.

Jacques

From: "Jacopo Cappellato" <ti...@sastau.it>
> Andrew,
>
> Andrew Ballantine wrote:
> > ...
> > My own personal experience of downloading from the latest SVN of ofbiz is of
> > failure to build. Maybe I have been unlucky, but I would prefer there to be
> > a current release that has all major bugs resolved as a working whole.
>
>
> You have been really unlucky... I update the system mostly every day and
> very few times I failed to build the system.
>
> Jacopo


Re: Community supported releases WAS [Re: Properly edited OFBiz manuals]

Posted by Jacopo Cappellato <ti...@sastau.it>.
Andrew,

Andrew Ballantine wrote:
> ...
> My own personal experience of downloading from the latest SVN of ofbiz is of
> failure to build. Maybe I have been unlucky, but I would prefer there to be
> a current release that has all major bugs resolved as a working whole.


You have been really unlucky... I update the system mostly every day and 
very few times I failed to build the system.

Jacopo

Re: Community supported releases WAS [Re: Properly edited OFBiz manuals]

Posted by Andrew Sykes <an...@sykesdevelopment.com>.
Andrew,

I'd agree with this, about 95% of the time everything builds just fine.

If you are getting a problem like this make sure you post here, such
problems are normally fixed VERY quickly!

- Andrew (Sykes)

On Tue, 2007-01-02 at 11:59 +0100, Jacopo Cappellato wrote:
> Andrew,
> 
> Andrew Ballantine wrote:
> > ...
> > My own personal experience of downloading from the latest SVN of ofbiz is of
> > failure to build. Maybe I have been unlucky, but I would prefer there to be
> > a current release that has all major bugs resolved as a working whole.
> 
> 
> You have been really unlucky... I update the system mostly every day and 
> very few times I failed to build the system.
> 
> Jacopo
-- 
Kind Regards
Andrew Sykes <an...@sykesdevelopment.com>
Sykes Development Ltd
http://www.sykesdevelopment.com


RE: Community supported releases WAS [Re: Properly edited OFBiz manuals]

Posted by Andrew Ballantine <ac...@willowbrook.co.uk>.
Hi,

Continual update is fine as long as the update process is:
a) Automatic ( like MS Windows updates)
b) Controllable ( Administrator decides when to implement)
c) Reversable (when the update causes a problem)

In order to do that you need a very strict testing program of all updates,
which I do not believe your community, though enthusiastic, can manage.

You will also come to a point where you want to implement something that
breaks previous compatibility and the only way to do that is to have a new
version. In the history of computing all projects reach a point where new
stuff cannot be implemented under the old rules/methods of the project and a
new version is created which has little compatibility with the last version.
There are various reasons for this, but I won't go into them here for the
sake of brevity.

My own personal experience of downloading from the latest SVN of ofbiz is of
failure to build. Maybe I have been unlucky, but I would prefer there to be
a current release that has all major bugs resolved as a working whole.
Revisions to the major release should be made available as updates to the
current stable release, but also added to a newer revised release that will
become the next stable release.

The updates could also be graded so that administrators of production
systems could gain confidence as to whether the update is safe to install.
Any update must be reversible in order to quickly undo an update which gave
unpredicted results.

Kind regards,

Andrew Ballantine.

-----Original Message-----
From: Walter Vaughan [mailto:wvaughan@steelerubber.com]
Sent: 29 December 2006 01:54
To: ofbiz-user@incubator.apache.org
Subject: Re: Community supported releases WAS [Re: Properly edited OFBiz
manuals]


[..snip..]

Golly, what a can of worms is open here. Actually what drew me to ofBiz was
the
amount of updates to the system.

The last commercial ERP solution we considered was SYSPRO. The folks at
Syspro
PRIDE themselves on weekly ports to their software. I have/had an .iso of a
marketing DVD they have with almost two hours of non-stop preaching how ERP
systems must and should be updated on a continuous basis, and that point
release
updates are evil. (e.g. 5.0 -> 6.0 on done every 18 months)

I was sold. Couldn't justify the seat costs for the number I needed, but I
was
sold on the concept. During our courting period I also got a weekly email
that
was similar to what Si Chen does with his blog listing the dozen or so
improvements to the system in the past week, and this in an ERP system with
15,000 current installs.

As a end user, what I am looking for is non-failure. Thus far I have more
than
enough trust in the core developers to always do the right thing.

--
Walter





--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.432 / Virus Database: 268.16.2/613 - Release Date: 01/01/2007
14:50


--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.432 / Virus Database: 268.16.2/613 - Release Date: 01/01/2007
14:50

--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.432 / Virus Database: 268.16.2/613 - Release Date: 01/01/2007
14:50



*****************************************************************
This email has been checked by the altohiway Mailcontroller Service
*****************************************************************

Re: Community supported releases WAS [Re: Properly edited OFBiz manuals]

Posted by Walter Vaughan <wv...@steelerubber.com>.
[..snip..]

Golly, what a can of worms is open here. Actually what drew me to ofBiz was the 
amount of updates to the system.

The last commercial ERP solution we considered was SYSPRO. The folks at Syspro 
PRIDE themselves on weekly ports to their software. I have/had an .iso of a 
marketing DVD they have with almost two hours of non-stop preaching how ERP 
systems must and should be updated on a continuous basis, and that point release 
updates are evil. (e.g. 5.0 -> 6.0 on done every 18 months)

I was sold. Couldn't justify the seat costs for the number I needed, but I was 
sold on the concept. During our courting period I also got a weekly email that 
was similar to what Si Chen does with his blog listing the dozen or so 
improvements to the system in the past week, and this in an ERP system with 
15,000 current installs.

As a end user, what I am looking for is non-failure. Thus far I have more than 
enough trust in the core developers to always do the right thing.

--
Walter




Re: Community supported releases WAS [Re: Properly edited OFBiz manuals]

Posted by Jacques Le Roux <ja...@les7arts.com>.
I agree with David.

IMHO tt seems the best way to go. Having to support 2 or 3 releases seems reasonable. More seems infeasible in our actual reality.

I don't know much about it but it looks like how Debian is driven and that way seems to work well.
If on the road we are lucky and find more ressources (I mean human ressources ;o) we may then go the way Ubuntu is going : creating
a new release every 6 months (Debian frequency is 18 months if I'm not wrong).
Also Ubuntu has chosen to support versions during 18 months. Ubuntu 6.06 LTS being the 1st exception : LTS stands for Long Time
Support meaning 3 years for desktop 5 years for server here (BTW 6.06 means june 2006). I think we may inspire ourself by this
support policy (inspiring is not copying ;o) and external releases numbering. We may have other release number in intern but that
may complicate things a bit.

In conclusion : I like this way to go because it's not too techie and simple to understand for end users (meaning not developpers
here)

WDYT ?

Jacques


----- Original Message ----- 
From: "David E Jones" <jo...@undersunconsulting.com>
To: <of...@incubator.apache.org>
Sent: Thursday, December 28, 2006 9:15 PM
Subject: Re: Community supported releases WAS [Re: Properly edited OFBiz manuals]


>
> On Dec 28, 2006, at 2:09 AM, Jacopo Cappellato wrote:
>
> > David E Jones wrote:
> >> I guess it depends on what the goal of doing a release is. In my
> >> mind the goal should be to create (over time...) a stable set of
> >> artifacts that people can build and deploy on if they choose not
> >> to go with the latest/greatest.
> >> What you're describing is interesting, but how is that any
> >> different than just using the latest from SVN with a little timing
> >> based on knowing what is going on added in, and keeping a list
> >> somewhere of all non-backwards compatible changes and their
> >> revision numbers?
> >
> > Yes, you have described pretty well what I'm suggesting; I'd only
> > add to these that we should also create the upgrade services (and/
> > or upgrade instructions) every time we commit a non-backwards
> > compatible change in svn. As you said, this is not so different
> > from what we are (implicitly) suggesting to do right now (as a best
> > practice to stay up-to-date with the trunk) but I think that it
> > would be nice if the community will officially support it for a few
> > reasons:
> >
> > 1) it's often difficult for users to pick a 'stable' svn snapshot
> > 2) it's often difficult for users to keep track of important
> > changes between their revision and the trunk
> > 3) since it is not so different from what we are suggesting right
> > now, it will not add a huge cost maintaining these extra processes/
> > releases
>
> The problem I see, trying to look at it from the point of a
> prospective end-user, is that this sort of frequent release doesn't
> help me a lot.
>
> 1. If I want a good, stable version where I don't have to worry about
> bugs, which one do I choose?
>
> 2. If I realize there is no perfect version because of constrained
> community resources but at least want to group together with others
> to support a certain release, which one do I choose when there are so
> many coming out so fast?
>
> 3. Once I have chosen and have been running for a while and want to
> upgrade OFBiz, which newer version do I choose (related to the above
> questions) and how much work is it going to be to not be able to
> update from that version to the version I choose, but instead go
> through the upgrade processes for every version between that one and
> the one I choose?
>
>
> >> But, back to the main point: what is the goal of a release in your
> >> mind (and in the mind of anyone else reading in too)?
> >
> > I'd like to get the opinions from others too.
> > Personally I think that releases (or release instructions/plans)
> > should at least help users to keep their system/data in sync with
> > the main trunk, minimizing the upgrade costs and simplifying the
> > users' decisions (i.e. "should I upgrade now?").
> > Of course it would also be great to have a real 'stable' releases
> > (with patches for them etc...) as you are suggesting (and I really
> > think we could implement the two approaches simultaneously since
> > what I've proposed could be the basis of a real release management)
> > but I'm not sure the community will really maintain them...
>
> I'd say if people want to stay in sync with the trunk, there is
> nothing better than the trunk for doing so... In my opinion doing
> some sort of regular "release" would only make it more difficult for
> people to keep up with the trunk and participate in or contribute to
> OFBiz because they would never be quite up to date.
>
> What I'm hoping for is a single, infrequent branch that people can
> rally around and maintain together. If we only do one of these each
> year or so then there will never be a question about which one needs
> fixes back patched to it as we'd only support at MOST 2-3 of these at
> any given time. That would mean people would need to update at least
> once every 3 years, but of course that's just a random artificial
> number and being a community driven thing if there is a group that
> wants to continue to maintain an older branch then great, more power
> to them!
>
> People looking for a good release to use if they are asking question
> #1 above would use the latest release in the latest stable branch
> that is at least, say, 3 months old. For people asking question #2
> above they could just use the latest stable branch as-is from the SVN
> directory for that branch and participate in making the branch better.
>
> -David


Re: Community supported releases WAS [Re: Properly edited OFBiz manuals]

Posted by David E Jones <jo...@undersunconsulting.com>.
On Dec 28, 2006, at 2:09 AM, Jacopo Cappellato wrote:

> David E Jones wrote:
>> I guess it depends on what the goal of doing a release is. In my  
>> mind the goal should be to create (over time...) a stable set of  
>> artifacts that people can build and deploy on if they choose not  
>> to go with the latest/greatest.
>> What you're describing is interesting, but how is that any  
>> different than just using the latest from SVN with a little timing  
>> based on knowing what is going on added in, and keeping a list  
>> somewhere of all non-backwards compatible changes and their  
>> revision numbers?
>
> Yes, you have described pretty well what I'm suggesting; I'd only  
> add to these that we should also create the upgrade services (and/ 
> or upgrade instructions) every time we commit a non-backwards  
> compatible change in svn. As you said, this is not so different  
> from what we are (implicitly) suggesting to do right now (as a best  
> practice to stay up-to-date with the trunk) but I think that it  
> would be nice if the community will officially support it for a few  
> reasons:
>
> 1) it's often difficult for users to pick a 'stable' svn snapshot
> 2) it's often difficult for users to keep track of important  
> changes between their revision and the trunk
> 3) since it is not so different from what we are suggesting right  
> now, it will not add a huge cost maintaining these extra processes/ 
> releases

The problem I see, trying to look at it from the point of a  
prospective end-user, is that this sort of frequent release doesn't  
help me a lot.

1. If I want a good, stable version where I don't have to worry about  
bugs, which one do I choose?

2. If I realize there is no perfect version because of constrained  
community resources but at least want to group together with others  
to support a certain release, which one do I choose when there are so  
many coming out so fast?

3. Once I have chosen and have been running for a while and want to  
upgrade OFBiz, which newer version do I choose (related to the above  
questions) and how much work is it going to be to not be able to  
update from that version to the version I choose, but instead go  
through the upgrade processes for every version between that one and  
the one I choose?


>> But, back to the main point: what is the goal of a release in your  
>> mind (and in the mind of anyone else reading in too)?
>
> I'd like to get the opinions from others too.
> Personally I think that releases (or release instructions/plans)  
> should at least help users to keep their system/data in sync with  
> the main trunk, minimizing the upgrade costs and simplifying the  
> users' decisions (i.e. "should I upgrade now?").
> Of course it would also be great to have a real 'stable' releases  
> (with patches for them etc...) as you are suggesting (and I really  
> think we could implement the two approaches simultaneously since  
> what I've proposed could be the basis of a real release management)  
> but I'm not sure the community will really maintain them...

I'd say if people want to stay in sync with the trunk, there is  
nothing better than the trunk for doing so... In my opinion doing  
some sort of regular "release" would only make it more difficult for  
people to keep up with the trunk and participate in or contribute to  
OFBiz because they would never be quite up to date.

What I'm hoping for is a single, infrequent branch that people can  
rally around and maintain together. If we only do one of these each  
year or so then there will never be a question about which one needs  
fixes back patched to it as we'd only support at MOST 2-3 of these at  
any given time. That would mean people would need to update at least  
once every 3 years, but of course that's just a random artificial  
number and being a community driven thing if there is a group that  
wants to continue to maintain an older branch then great, more power  
to them!

People looking for a good release to use if they are asking question  
#1 above would use the latest release in the latest stable branch  
that is at least, say, 3 months old. For people asking question #2  
above they could just use the latest stable branch as-is from the SVN  
directory for that branch and participate in making the branch better.

-David


Re: Community supported releases WAS [Re: Properly edited OFBiz manuals]

Posted by Jacques Le Roux <ja...@les7arts.com>.
From: "Jacopo Cappellato" <ti...@sastau.it>
> Of course it would also be great to have a real 'stable' releases (with 
> patches for them etc...) as you are suggesting (and I really think we 
> could implement the two approaches simultaneously since what I've 
> proposed could be the basis of a real release management) but I'm not 
> sure the community will really maintain them...

Why not ? We may take the challenge...

Jacques

Re: Community supported releases WAS [Re: Properly edited OFBiz manuals]

Posted by Jacopo Cappellato <ti...@sastau.it>.
David E Jones wrote:
> 
> I guess it depends on what the goal of doing a release is. In my mind 
> the goal should be to create (over time...) a stable set of artifacts 
> that people can build and deploy on if they choose not to go with the 
> latest/greatest.
> 
> What you're describing is interesting, but how is that any different 
> than just using the latest from SVN with a little timing based on 
> knowing what is going on added in, and keeping a list somewhere of all 
> non-backwards compatible changes and their revision numbers?
> 

Yes, you have described pretty well what I'm suggesting; I'd only add to 
these that we should also create the upgrade services (and/or upgrade 
instructions) every time we commit a non-backwards compatible change in 
svn. As you said, this is not so different from what we are (implicitly) 
suggesting to do right now (as a best practice to stay up-to-date with 
the trunk) but I think that it would be nice if the community will 
officially support it for a few reasons:

1) it's often difficult for users to pick a 'stable' svn snapshot
2) it's often difficult for users to keep track of important changes 
between their revision and the trunk
3) since it is not so different from what we are suggesting right now, 
it will not add a huge cost maintaining these extra processes/releases

> On that last bit, whatever we do with the releases having an official 
> wiki page with all non-backward-compatible changes listed on it with the 
> revision number for each would be a good thing to do...
> 

+1

> But, back to the main point: what is the goal of a release in your mind 
> (and in the mind of anyone else reading in too)?
> 

I'd like to get the opinions from others too.
Personally I think that releases (or release instructions/plans) should 
at least help users to keep their system/data in sync with the main 
trunk, minimizing the upgrade costs and simplifying the users' decisions 
(i.e. "should I upgrade now?").
Of course it would also be great to have a real 'stable' releases (with 
patches for them etc...) as you are suggesting (and I really think we 
could implement the two approaches simultaneously since what I've 
proposed could be the basis of a real release management) but I'm not 
sure the community will really maintain them...

Jacopo

> -David
> 


Re: Community supported releases WAS [Re: Properly edited OFBiz manuals]

Posted by David E Jones <jo...@undersunconsulting.com>.
On Dec 28, 2006, at 2:06 AM, Torsten Schlabach wrote:

> Have you thought about not having releases of the whole package at  
> a time, but releasing components. You could version the framework,  
> the "execution environment" so to say and then version the indidual  
> modules (Marketing, Partners, ...). That would allow for a user to  
> upgrade what he needs to upgrade. You should still use some Linux  
> package maintainance system as a guide how to manage compatibility,  
> basically how to do SCM in the original sense of the word.
>
> So I could find out, that in my installation I am running:
>
> OFBiz Base:       1.0.12
> OFBiz CRM:        1.1.3
> OFBiz Accounting: 1.0.0
>
> Now the team which is maintaining the accounting module feels like  
> releasing version 1.1.0 which still requires OFBiz Base 1.0.5 or  
> higher. I have 1.0.12, so I should be ok.
>
> Next month, you might have a release of CRM which is 2.0.1 because  
> is has made a major leap forward in functionality. For that to  
> happen, you had to update the Base framework as well. So CRM 2.0.1  
> requires at least OFBiz Base 1.1.0. Get the idea?

This has been discussed a number of times and I am 100% against it at  
this point. If we had 100 developers and we were trying to figure out  
how to keep everything moving smoothly this might be okay, assuming  
about 10 of those 100 developers contributing on a regular basis were  
doing package management, then maybe.

Personally, the library management in Linux is one thing I HATE HATE  
HATE about it. It makes the system a nightmare and sometimes because  
there are system level libraries you have to do super-funky stuff to  
get 2 different programs that require different versions of non- 
backward compatible libraries to run together...

We may very well start versioning the framework separately at some  
point in the future, and you can already run the framework without  
the applications (just delete the applications and specialpurpose  
directories). Totally separating them would mean moving the  
applications to somewhere else in SVN and including the built  
framework but not the code of the framework with the applications (in  
SVN anyway).

Splitting out each component to have a different version number: I'll  
fight that pretty hard because I think it would just waste a bunch of  
effort and eventually fail. I don't think it would bring down the  
project, but it would kill progress on various things for a while...


> IMO the key to success of OFBiz will be to make sure you have  
> enough sub-communities which are going to focus on vertical  
> functionality as well as on locales. But keep them on apache.org  
> and by all means avoid a situation where a "basic OFBiz" is real  
> OSS but to really use it in a business, you need the X, Y and Z  
> components which are 300 USD, 2500 USD and 400 USD per seat and  
> only work with an outdated version of the package itself. Or even  
> worse: You are not going to find any compatible versions of X, Y  
> and Z at all to even get them installed.
>
> This kind of threading and pseudo-commercialization was and is a  
> massive road-block to the success of something like Compiere and  
> IMO OFBiz biggest opportunity is to just do better here.


Unfortunately we can't do ANYTHING about what other people decide to  
build based on OFBiz and how they decide to distribute it. We aren't  
in the business of doing things in a GPL way, and we want to  
encourage commercial as well as open source derivative works. That is  
very explicit in the Apache 2.0 license and in how OFBiz has been run  
since the beginning.

Fortunately there aren't any forks of the base OFBiz code base, and I  
think that is partially because of this openness. There are a few  
derivatives where people have chosen to do them as open source (or  
semi-open source with a GPL/commercial dual license), and these to  
some extent do compete with functionality in OFBiz. That's their  
choice unfortunately and can make things more confusing for  
prospective users, but in general it's a healthy thing to build up  
more around OFBiz.

-David



Re: Community supported releases WAS [Re: Properly edited OFBiz manuals]

Posted by Torsten Schlabach <ts...@gmx.net>.
Hi David (and others),

 > But, back to the main point: what is the goal of a release in your
 > mind (and in the mind of anyone else reading in too)?

To have a reproduceable and tested state of code. I would like to take 
the perspective of a business end-user here once again. If I was running 
my company on OFBiz (we plan to do so, by the way) I would want to make 
sure that a release contains code that has been properly tested. So if I 
run 1.0 now and I get the chance to upgrade to 1.1, I would expect that 
there is no broken functionality because I have real people doing their 
daily work using that software and also our customers would not be too 
happy if they receive wrong invoices because some developer felt like 
checking in some untested changes to invoice generation and I just had 
the bad luck to update to the SVN version which had that in.

Also a release is about support. Put yourself in the shoes of someone 
making a living of implementing and supporting several customers that 
run their individual OFBiz installations. How are you ever going to 
compare behaviour, against what would you ever file a bug, how would the 
customer ever be able to tell what version he's running if there are no 
releases?

What I could imaging and would like to suggest though:

Have you thought about not having releases of the whole package at a 
time, but releasing components. You could version the framework, the 
"execution environment" so to say and then version the indidual modules 
(Marketing, Partners, ...). That would allow for a user to upgrade what 
he needs to upgrade. You should still use some Linux package 
maintainance system as a guide how to manage compatibility, basically 
how to do SCM in the original sense of the word.

So I could find out, that in my installation I am running:

OFBiz Base:       1.0.12
OFBiz CRM:        1.1.3
OFBiz Accounting: 1.0.0

Now the team which is maintaining the accounting module feels like 
releasing version 1.1.0 which still requires OFBiz Base 1.0.5 or higher. 
I have 1.0.12, so I should be ok.

Next month, you might have a release of CRM which is 2.0.1 because is 
has made a major leap forward in functionality. For that to happen, you 
had to update the Base framework as well. So CRM 2.0.1 requires at least 
OFBiz Base 1.1.0. Get the idea?

IMO the key to success of OFBiz will be to make sure you have enough 
sub-communities which are going to focus on vertical functionality as 
well as on locales. But keep them on apache.org and by all means avoid a 
situation where a "basic OFBiz" is real OSS but to really use it in a 
business, you need the X, Y and Z components which are 300 USD, 2500 USD 
and 400 USD per seat and only work with an outdated version of the 
package itself. Or even worse: You are not going to find any compatible 
versions of X, Y and Z at all to even get them installed.

This kind of threading and pseudo-commercialization was and is a massive 
road-block to the success of something like Compiere and IMO OFBiz 
biggest opportunity is to just do better here.

Regards,
Torsten


David E Jones schrieb:
> 
> On Dec 28, 2006, at 12:57 AM, Jacopo Cappellato wrote:
> 
>> David E Jones wrote:
>>
>>> ...
>>> Still, the first priority after graduation is to do a community  
>>> supported branch "release". Again given the size of OFBiz relative  
>>> to the size of the community, we don't have resources to do a full  
>>> QA pass before issuing a release, so the release process for OFBiz  
>>> will be centered around a community effort to maintain a branch  that 
>>> will have bug fixes, but not new features, as anything would  be 
>>> maintained with a priority of stability over progress (new  features, 
>>> etc).
>>
>>
>> Are we sure this is the best way to go? My fear is that no one will  
>> ever maintain these releases (submitting patches for them etc.).
>> A slightly different approach could be this:
>>
>> 1) we issue releases regularly and very often, let's say once every  
>> two months
>> 2) each release will not undergo a full QA pass, however we will  try 
>> to issue it when the code is pretty stable (e.g. not  immediately 
>> after a big refactoring)
>> 3) every time we do changes in the trunk that could cause backward  
>> compatibility issues (changes to the existing data model, seed  data, 
>> jars etc...), we document them somewhere and if possible we  provide 
>> upgrade scripts or instructions (in order to upgrade from  the latest 
>> release only); when a release is done, these  instructions are 
>> delivered with it ("Upgrade notes from release X  to new release X+1").
>>
>> I think this approach (with its pros and cons) is easier to  maintain 
>> by the OFBiz community (because it's not so different from  what we 
>> are doing now) and could be acceptable by the OFBiz's users  (because 
>> it's similar to what most users are doing now, i.e.  staying 
>> up-to-date with the trunk to minimize upgrade costs).
> 
> 
> I guess it depends on what the goal of doing a release is. In my mind  
> the goal should be to create (over time...) a stable set of artifacts  
> that people can build and deploy on if they choose not to go with the  
> latest/greatest.
> 
> What you're describing is interesting, but how is that any different  
> than just using the latest from SVN with a little timing based on  
> knowing what is going on added in, and keeping a list somewhere of  all 
> non-backwards compatible changes and their revision numbers?
> 
> On that last bit, whatever we do with the releases having an official  
> wiki page with all non-backward-compatible changes listed on it with  
> the revision number for each would be a good thing to do...
> 
> But, back to the main point: what is the goal of a release in your  mind 
> (and in the mind of anyone else reading in too)?
> 
> -David
> 

Re: Community supported releases WAS [Re: Properly edited OFBiz manuals]

Posted by David E Jones <jo...@undersunconsulting.com>.
On Dec 28, 2006, at 12:57 AM, Jacopo Cappellato wrote:

> David E Jones wrote:
>> ...
>> Still, the first priority after graduation is to do a community  
>> supported branch "release". Again given the size of OFBiz relative  
>> to the size of the community, we don't have resources to do a full  
>> QA pass before issuing a release, so the release process for OFBiz  
>> will be centered around a community effort to maintain a branch  
>> that will have bug fixes, but not new features, as anything would  
>> be maintained with a priority of stability over progress (new  
>> features, etc).
>
> Are we sure this is the best way to go? My fear is that no one will  
> ever maintain these releases (submitting patches for them etc.).
> A slightly different approach could be this:
>
> 1) we issue releases regularly and very often, let's say once every  
> two months
> 2) each release will not undergo a full QA pass, however we will  
> try to issue it when the code is pretty stable (e.g. not  
> immediately after a big refactoring)
> 3) every time we do changes in the trunk that could cause backward  
> compatibility issues (changes to the existing data model, seed  
> data, jars etc...), we document them somewhere and if possible we  
> provide upgrade scripts or instructions (in order to upgrade from  
> the latest release only); when a release is done, these  
> instructions are delivered with it ("Upgrade notes from release X  
> to new release X+1").
>
> I think this approach (with its pros and cons) is easier to  
> maintain by the OFBiz community (because it's not so different from  
> what we are doing now) and could be acceptable by the OFBiz's users  
> (because it's similar to what most users are doing now, i.e.  
> staying up-to-date with the trunk to minimize upgrade costs).

I guess it depends on what the goal of doing a release is. In my mind  
the goal should be to create (over time...) a stable set of artifacts  
that people can build and deploy on if they choose not to go with the  
latest/greatest.

What you're describing is interesting, but how is that any different  
than just using the latest from SVN with a little timing based on  
knowing what is going on added in, and keeping a list somewhere of  
all non-backwards compatible changes and their revision numbers?

On that last bit, whatever we do with the releases having an official  
wiki page with all non-backward-compatible changes listed on it with  
the revision number for each would be a good thing to do...

But, back to the main point: what is the goal of a release in your  
mind (and in the mind of anyone else reading in too)?

-David