Forum OpenACS Development: Current Stable Release

Collapse
1: Current Stable Release
Posted by Steve Manning on 11/17/10 05:46 PM
Hi

Could someone confirm the version number which is considered to be the current stable release?

The home page suggests that its 5.6.0 but when I install that there are no packages available in the repository - Install From Repository gives "Couldn't Get Package List" as noted here https://openacs.org/forums/message-view?message_id=3416012

The OpenACS Release Status page https://openacs.org/xowiki/openacs-release-status suggests that the current release is 5.5.0 but that is 06/2009, so I'm thinking thats just not up to date.

Can anyone shed a little light on this?

Thanks

Steve

Collapse
2: Re: Current Stable Release (response to 1)
Posted by Ryan Gallimore on 11/18/10 01:29 AM
Hi Steve,

Current stable release is 5.6. Missing CVS tags are causing the "Couldn't Get Package List" error. This should be resolved shortly.

Regards,
Ryan

Collapse
3: Re: Current Stable Release (response to 2)
Posted by Jim Lynch on 11/18/10 02:30 AM
how does this part work, does it look for specific tagnames in cvs, and create .apms from cvs checkout automatically?

how could this work in git?

Collapse
4: Re: Current Stable Release (response to 3)
Posted by Gustaf Neumann on 11/18/10 09:01 AM
Yes, exactly. The automatic build mechanism gets the release tags from a "cvs ... log ..." command, checks out all releases and builds apms from that. So, the automatic build mechanism of the apm repositories depends on the CVS tag names (as defined in https://openacs.org/doc/cvs-guidelines.html).

Yes, on a move to git, the apm rebuild code has to be redone (along with the cvs-guidelines, we need then git-guidelines, etc.). One could more or less translate the tagging rules, release guidelines and apm-rebuild mechanisms 1:1 into git (or for example, drop the apm mechanisms, i would not be in favor of that), but one has certainly to evaluate the tradeoff between effort and benefits carefully.

Collapse
5: Re: Current Stable Release (response to 1)
Posted by Steve Manning on 11/18/10 10:58 AM
Thanks for the replies.

So regardless of the finer points of the automatic checkout or any proposed move to Git at the moment it looks as if the procedure has failed for 5.6.0 and given that it was release back in June it doesn't look like a fix is coming any time soon.

So I have to use 5.5.0 or checkout the 5.5.0 packages manually from cvs and apply them locally?

Steve

Collapse
6: Re: Current Stable Release (response to 1)
Posted by Dave Bauer on 11/18/10 03:14 PM
Steve, the best bet is to get 5.6.0 core packages. You can most likely use the optional packages from HEAD, but the 5.5 packages should also work.
Collapse
7: Re: Current Stable Release (response to 6)
Posted by Steve Manning on 11/18/10 05:57 PM
Thanks Dave, that is indeed what I have done.