Author: sebastien.lelong
Date: Sun Oct 12 00:23:41 2008
New Revision: 393

Modified:
    wiki/ValidationProcess.wiki

Log:
move => copy, don't forget to generate jalapi and testing matrix

Modified: wiki/ValidationProcess.wiki
==============================================================================
--- wiki/ValidationProcess.wiki (original)
+++ wiki/ValidationProcess.wiki Sun Oct 12 00:23:41 2008
@@ -21,11 +21,14 @@

   # for each file, people vote. If there's more than 50% positive opinion,  
the file can go to the _validated_ map
   # every jallib project member can vote
- # once a file has been promoted to _validated_, it is *moved*, using `svn  
move`
+ # once a file has been promoted to _validated_, it is *copied*, using  
`svn copy` (to keep history logs)


  Once enough files have been moved (there's no more enough positive votes),  
once everybody is happy, a new release _can_ be created. It's not mandatory.

+ # jalapi must be regenerated using the these new validated files.
+ # the testing matrix must be regenerated, too.
   # if a new release is created, a new svn branch is created, so we always  
have access to the release's content at this time.
   # once the branch is created, `svn export` will extract all files without  
SVN information. Files are then flatten in the include map. A new tarball  
and zip are created.
- # these tarball and zip files are uploaded to the *files* section of  
jallib google code project.
\ No newline at end of file
+ # these tarball and zip files are uploaded to the *files* section of  
jallib google code project.
+ # announce mail to jallist !!!
\ No newline at end of file

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/jallib?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to