Re: [JBoss-user] Confused about JBoss Version Control and versions

2002-10-28 Thread Emerson Cargnin - SICREDI Serviços
i have just reaserched about patterns on branches and releases (to 
define our way of doing this), and one of the most import detail when 
getting a bug fixed is do it first in the least modified branch (I thing 
this would be a stable branch , like 3.0) and after that propagate it to 
other branches until getting it to HEAD.


some stuff about SCM :

- Branching Patterns for Parallel Software Development
http://www.enteract.com/~bradapp/acme/branching
- Configuration Management Patterns 
http://www.bell-labs.com/cgi-user/OrgPatterns/OrgPatterns?ConfigurationManagementPatterns
- Zope Release Policy
http://dev.zope.org/CVS/ZopeReleasePolicy
- High-Level Best Practices in SCM
http://www.perforce.com/perforce/bestpractices.html
- Data Grid CVS policies
http://lindir.ics.muni.cz/dg_public/cederqvist-1.11.1p1.html/cvs.html
- And of course (maybe it should be updated a little):
http://www.jboss.org/developers/guides/cvs-admin.jsp


Scott M Stark wrote:
Its priorities and/or lazy developers. If a fix has not made it into a branch
you need it in create a context diff of the patch for the branch and submit
it to patches section of the jboss project on sourceforge.


Scott Stark
Chief Technology Officer
JBoss Group, LLC


- Original Message - 
From: Alwyn Schoeman [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, October 27, 2002 7:15 PM
Subject: [JBoss-user] Confused about JBoss Version Control and versions



JBoss consists of various CVS branches. What confuses me is that there
seems to be no consistent method of fixes to CVS head moving into
Release versions.  One example is the rollinglogged PersistenceManager
fix that has been existing in CVS Head now for 2 months, but has not
moved to 3.0 branch yet, although rollinglogged will not work at all in
3.0 without it.




Is this a matter of more important issues taking precedence or must
users specific request this action? If so, where?





---
This SF.net email is sponsored by: ApacheCon, November 18-21 in
Las Vegas (supported by COMDEX), the only Apache event to be
fully supported by the ASF. http://www.apachecon.com
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user




--

| Emerson Cargnin  |
| Analista de Sistemas Sr. |
| Tel : (051) 3358-4959|
| SICREDI Serviços |
| Porto Alegre - Brasil|
|xx|



---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user



Re: [JBoss-user] Confused about JBoss Version Control and versions

2002-10-27 Thread Scott M Stark
Its priorities and/or lazy developers. If a fix has not made it into a branch
you need it in create a context diff of the patch for the branch and submit
it to patches section of the jboss project on sourceforge.


Scott Stark
Chief Technology Officer
JBoss Group, LLC


- Original Message - 
From: Alwyn Schoeman [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, October 27, 2002 7:15 PM
Subject: [JBoss-user] Confused about JBoss Version Control and versions


 JBoss consists of various CVS branches. What confuses me is that there
 seems to be no consistent method of fixes to CVS head moving into
 Release versions.  One example is the rollinglogged PersistenceManager
 fix that has been existing in CVS Head now for 2 months, but has not
 moved to 3.0 branch yet, although rollinglogged will not work at all in
 3.0 without it.

 Is this a matter of more important issues taking precedence or must
 users specific request this action? If so, where?



---
This SF.net email is sponsored by: ApacheCon, November 18-21 in
Las Vegas (supported by COMDEX), the only Apache event to be
fully supported by the ASF. http://www.apachecon.com
___
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user