Needs review
Project:
Site Documentation
Version:
6.x-1.3
Component:
Miscellaneous
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
23 Feb 2011 at 14:03 UTC
Updated:
9 Jan 2012 at 21:26 UTC
Jump to comment: Most recent file
Comments
Comment #1
nancydruComment #2
izmeez commentedI just downloaded sitedoc-6.x-1.3.tar.gz but the files are all from 2008,
Whereas the files in the last dev release from 2010-Feb-16 includes:
sitedoc.css 2009-02-10
sitedoc.module 2010-02-16
Shouldn't these be in new version?
Thanks.
Comment #3
izmeez commentedbump, I have changed the status to needs review. Can maintainers please look at comment #2 and respond. Thanks.
Comment #4
izmeez commented+bump. I almost regret having opened this issue. I thought it would be a simple request, but seeing the outcome of a release with older files than in the last committed dev surprises me and wasn't what I expected. Can you please take a look and sort out what files should be in the release. Meanwhile I am staying with the old dev release.
Thanks,
Izzy
Comment #5
nancydruMy computer died and the hard disk had to be rebuilt. I checked out what was supposed to be the most current code and created a release with it. Apparently CVS lied to me. But now, we've switched to Git and I have not yet been able to figure out how to get it to work for me. If you are a Git guru and would like to walk through using it (with a GUI), I'd welcome the help.
Comment #6
izmeez commented@nancydru Thanks for the reply. I'm sorry to hear of your disaster and sorry to say that I am just trying to get a handle on Git myself. Maybe someone else can step in and help.
Comment #7
izmeez commentedThe last dev release was from 2010-Feb-16 and that is the one I have been using.
I took a look at the current dev release and the only differences with the move to Git are that the translation directories are now gone and the title line
-// $Id: sitedoc.module,v 1.46.2.2.2.19 2010/02/16 18:00:28 nancyw Exp $is gone from the module, install, css, and inc files. So it looks good to go. Just a question of how to make that into a release.
Thanks,
Izzy
Comment #8
izmeez commentedHaving caused so much grief when I first opened this issue I almost hate to bump it up again.
First, thank you for this module. It is very useful.
The version tag 1.3 is to the same point in the commits as the version tag 1.2 so these versions are the same despite the dates of the releases appearing different.
The shortlog shows some significant fixes committed to the dev release from 2008-09-16 to 2010-02-16 and the dev release from that date forward has been working well for me.
I wonder if it is possible to make the dev version a full release as 6.x-1.4 and if this may help with some of the comments that have arisen on other existing issues since the 1.3 release in Feb 2011?
Comment #9
petsagouris commentedI have begun porting this to D7. I am keeping all the changes in a local git repository.
Nancy, I can help you with git if you want although I am not really sure about the smallest details on how git is being used by the drupal community. I come from github :)
Comment #10
petsagouris commentedWell, the main conversion (code) is done, but the functionality provided by the sitedoc module is in some places irrelevant after the D7 release. I need some information on the ways this project will be useful to its users.
I can provide the code up to this point but in reality this is not even a dev version (no real output yet).
The code is telling me that it needs to be spread out into sub-modules or even plugins (from ctools suite) but I am not really familiar with those kind of development practices.
Comment #11
nancydruI know a few things that need changing to be relevant. Would you mind sharing your list?
Comment #12
petsagouris commentedThere is no list on my part, I am trying to follow the initial functionality but I am at a loss at the moment.
Here is the pre-prealpha code exactly as it is now on my dev machine and it is really filthy and broken.