Re: [GUSDEV] bug in GUS schema, evidentiated by InsertSequenceFeatures

[Fernan A. <fe...@ii...>]

+----[ an...@ne... <an...@ne...> (19.Oct.2006 13:13):
|
| Quoting Fernan Aguero <fe...@ii...>:
| 
| > So I'd say that you're safe using the trunk ... at least
| > until 3.6 comes out (because then the 3.6 branch will be
| > merged to trunk, correct?. At least this is how I now understand it.
| > Others please correct me if I'm wrong).

This is the idea I got after a discussion regarding the GUS
development process in the context of how it deals with the
version control repository (branches, tags, etc.) 

http://sourceforge.net/mailarchive/message.php?msg_id=12227127

| I've been re-reading the install documentation, and that's what made us take
| the decision of avoiding SVN in the first place:
| 
|   Warning
| 
|   Since the 3.5 release of GUS, the source repository is no longer the
|   preferred or recommended method for downloading GUS. The source repository
|   contains the most recent additions and changes to GUS, which may be
|   inconsistent with this and other documentation, and which may include changed
|   APIs that could cause data loss.
| 
| If this information no longer applies, that's probably a part that should be
| corrected, isn't it?

I've also re-read the docs, and also found this in the wiki:
http://www.gusdb.org/wiki/index.php/GusVersionBranch

"Up until release 3.5 GUS has not had any systematic or
rigorous approaches to releases. Instead, users of GUS
acquired the development version of the system directly from
the repository. This has the obvoius drawback that users
have unstable software, and no two users are likely to have
exactly the same software.

GUS will now adopt standard practice for releases.

[...]

Now that release 3.5 is complete, the trunk of the
repository is presumed to hold development that is aiming
towards release 3.6. When the feature set designated for 3.6
is complete, we create a branch in the repository tagged
"3.6". The trunk is now available for 3.7 development. The
3.6 branch undergoes final testing and corrections. When
that process is complete the branch is tagged with "3.6.0",
and source is bundled for distribution and made available on
the download site. Inevitably minor problems or "bugs" will
be unearthed by the users. As these are corrected, the
source is advanced through the 3.6.1, 3.6.2, etc. The branch
is tagged each time and the source rebundled for
distribution"

The question would now be:

is this still a proposal? Or is it being enforced as we
speak?


| > But in any case you can always checkout a snapshot from any point back in
| > time...
| 
| I've tried to, but just don't seem to be able to: gusTrunk is an empty
| container that relies on other external trunks for getting the real software.

Mmm ... 

| No matter what release I ask for, I always end up with the latest tree being
| checked out for these external sources. For instance, the command

yes, this seems to be the case.
| 
| svn co --revision {2006-04-11} https://www.cbil.upenn.edu/svn/gus/gusTrunk .
| 
| terminates with the following lines:
| 
| ------------------------------------------------------
| Fetching external item into 'project_home/install'
|  ...
| Checked out external at revision 5069.
| 
| 
| Fetching external item into 'project_home/GusSchema'
|  ...
| Checked out external at revision 5069.
| 
| Checked out revision 4752.
| ------------------------------------------------------

Indeed. Rev 4752 should be the one we fetched back in April,
but the gusTrunk container seems to be pointing to the latest
revision (5069) of GusApplication and GusSchema ...

I have just checked out a new snapshot using
svn co --revision "{2006-04-11}" https://www.cbil.upenn.edu/svn/gus/gusTrunk GUS
into a directory named gus-23Oct2006

and extracted a tarball of the snapshot I took in
11/Apr/2006 into a directory named gus-11Apr2006

and the diff between the two is not null:

diff -ruN --exclude=.svn gus-11Apr2006/ gus-23Oct2006/ > gus.diff

In any case, the container helps users just by letting them check
out a GUS environment (gus_home, project_home) ready to be
installed.

I guess that the --revision "{date}" option of svn should
work when checking out the separate modules independently:
GusSchema
install
CBIL
GusAppFramework

Fernan


| Regards,
| 
| Antonio
|
+----]