Re: [WSG] Code management advice needed

2009-03-05 Thread Ben Rowe 




Hi
Jens,

In addition to what Rob wrote, check out the following resources.

http://svnbook.red-bean.com/en/1.0/ch05s04.html
http://svnbook.red-bean.com/en/1.0/ch04.html

Ben
fatpublisher.com.au

On 6/03/2009 9:13 AM, Robert Turner wrote:

  
  
Hi Jens,
  
You need to branch the codebase. A typical SVN repository is setup as:
  
repos/trunk
repos/tags
repos/branches
  
Most people will checkout repos/trunk and just work off that.
What you need to do is copy the trunk (svn cp/copy repos/trunk
repos/branches/branch-version). Then keep two
checkouts: repos/trunk (current versoin) and
repos/branches/branch-version (old version).
  
It is also advisable to 'tag' each release version by svn cp'ing it to
the tags directory.
  
Thanks,
Rob
  
  
Jens-Uwe Korff wrote:
  
Hi all,

this might be slightly off topic and I'm glad for any redirects.

We're managing our source code in a version control system called SVN.
This works as long as frontend carve and backend integration are linear.

Sometimes however we need to change code that's "old" from a frontend
perspective, because the frontend has already implemented new changes.
We struggle with how to properly implement a workflow in this case,
because we would need new versions of the old code while still working
on changes of the current "new" code.

I have posted a message on svnforum.org, but received no reply.

If you know SVN well or if you have any links, groups etc. to turn to
I'd be very thankful. You can reply off-list if necessary.

Thanks,
Jens 

The information contained in this e-mail message and any accompanying files is or may be confidential. If you are not the intended recipient, any use, dissemination, reliance, forwarding, printing or copying of this e-mail or any attached files is unauthorised. This e-mail is subject to copyright. No part of it should be reproduced, adapted or communicated without the written consent of the copyright owner. If you have received this e-mail in error please advise the sender immediately by return e-mail or telephone and delete all copies. Fairfax does not guarantee the accuracy or completeness of any information contained in this e-mail or attached files. Internet communications are not secure, therefore Fairfax does not accept legal responsibility for the contents of this message or attached files.


***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***

  
  
  
  
  -- 
  
  
   Rob Turner 
Company Leader 
   
  www. f l e
x a d a t a .com
   
   +1 415 448 7652
  
  +61 7 3040 1337
  
  
  
  
  
  
  
***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***




***List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfmUnsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfmHelp: memberh...@webstandardsgroup.org***

[WSG] Microformats Accessibility

2009-01-18 Thread Ben Rowe 
on microformats.org, it suggests the ABBR element and title attribute 
for machine code. however, title attribute for this element will be read 
out to a screen reader user. we are considering having an output of 
span class=namehuman valuespan class=value title=machine 
value/span/span however its an empty span. this method of empty 
spans is also suggested on microformats.org to combat accessibility 
issues, but wanted your suggestions / thoughts?


Obviously it is a clash of HTML standards VS accessibility. I've chosen 
the span option because I think accessibility is more important.


Ben


***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***