Hi all, as you probably know, the CVS tree can have branches. We have - one stable rel_2_2. - one unstable, but actively developped & that will result in official koha 3.0 "soon". - one managed by Tumer Garip, that is, actually in HEAD. some interesting features from head have been ported to rel_3_0. Many things don't. with rel_3_0 becoming stable, we think we should reorganize the CVS a little bit : - tumer stuff would be branched to a "tumer" branch (rel_TG ?), from actual head. - rel_3_0 will be feature freezed and only bugfixed. - rel_3_0 will be copied to head (overwriting actual head), to be the official HEAD. any interesting stuff from tumer would be ported here from rel_TG To do this, we have to do things one after the other : - 1st tumer : could you confirm you don't have anything waiting to be commited to head (i've been told that there are things in fact ;-) ). Once it's done, we will be able to : - create rel_TG branch from HEAD - copy all scripts from rel_3_0 to a local HEAD copy - commit all those scripts to have HEAD= rel_3_0. Once it will have been done : - tumer, you'll have to be carefull to branch your local copy to rel_TG to avoid commiting stuff into head by mistake - we will have rel_3_0 for bugfixes only - we will have HEAD for new ideas & coding. A last question : does someone candidate to synch stable rel_3_0 into HEAD ? toins may take care of it, but I would prefer someone else (and I remind you that he works with us till july, nothing sure for september -august being for wedding ;-) ). -- Paul POULAIN et Henri Damien LAURENT Consultants indépendants en logiciels libres et bibliothéconomie (http://www.koha-fr.org) Tel : 04 91 31 45 19
Hi all, I missed the IRC-meeting yesterday due to unforseen matters. Regarding HEAD, currently i am not being able to commit to it. I have always been slow in learning the cvs process. When i try to commit its telling me that its newer than my version while its not and i am fed up. 1- Just delete the whole thing. 2-Start a blank rel_TG 3-Most of the stuff allready in files are useless with my edition anyway 4- I will commit everything to rel_TG including my NPL templates as default and NEU specific OPAC as well 5- This way it will be a working rel_TG 6- I will organize the folder structure so do not put the empty folders there either 7- This branch can than be used as it is on its own or for things you may like to backport. 8- If you are not going to use the meta-record structure of this release why bother about 1-7 since i cannot keep it it sync with SAN-OP or rel_3 anyway? If the above is making anysense than i am prepared to do 4-7 anytime you are ready. I am veeeeeery busy this month so sorry about late responses. St. Valentines Day is almost here and i havent got her anything yet, I have to rush, see you all. Tumer ________________________________ From: koha-devel-bounces+tgarip=neu.edu.tr@nongnu.org on behalf of Paul POULAIN Sent: Thu 08/02/2007 16:06 To: koha-devel Subject: [Koha-devel] rel_3_0, head & tumer stuff Hi all, as you probably know, the CVS tree can have branches. We have - one stable rel_2_2. - one unstable, but actively developped & that will result in official koha 3.0 "soon". - one managed by Tumer Garip, that is, actually in HEAD. some interesting features from head have been ported to rel_3_0. Many things don't. with rel_3_0 becoming stable, we think we should reorganize the CVS a little bit : - tumer stuff would be branched to a "tumer" branch (rel_TG ?), from actual head. - rel_3_0 will be feature freezed and only bugfixed. - rel_3_0 will be copied to head (overwriting actual head), to be the official HEAD. any interesting stuff from tumer would be ported here from rel_TG To do this, we have to do things one after the other : - 1st tumer : could you confirm you don't have anything waiting to be commited to head (i've been told that there are things in fact ;-) ). Once it's done, we will be able to : - create rel_TG branch from HEAD - copy all scripts from rel_3_0 to a local HEAD copy - commit all those scripts to have HEAD= rel_3_0. Once it will have been done : - tumer, you'll have to be carefull to branch your local copy to rel_TG to avoid commiting stuff into head by mistake - we will have rel_3_0 for bugfixes only - we will have HEAD for new ideas & coding. A last question : does someone candidate to synch stable rel_3_0 into HEAD ? toins may take care of it, but I would prefer someone else (and I remind you that he works with us till july, nothing sure for september -august being for wedding ;-) ). -- Paul POULAIN et Henri Damien LAURENT Consultants indépendants en logiciels libres et bibliothéconomie (http://www.koha-fr.org) Tel : 04 91 31 45 19 _______________________________________________ Koha-devel mailing list Koha-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/koha-devel
Tümer, Is your own need for a separate branch exclusively related to your problems with committing updates to the CVS server? Do you otherwise have some need for a separate branch, because synching with HEAD on your production system is a hazard or requires you to do too much work fixing things before you would commit to HEAD if you could actually commit to HEAD? Is there a problem for what others have been working on in HEAD if you do not have a separate branch? I was about to send a long reply raising the importance of your code to the future of the main branch in perhaps version 4 and suggesting workarounds for your problem committing to HEAD so as to avoid unnecessary code forking. I want to have a better understanding of the issues before I post with an improper understanding. Thomas Dukleth Agogme 109 E 9th Street, 3D New York, NY 10003 USA http://www.agogme.com 212-674-3783 On Thu, February 8, 2007 6:04 pm, Tumer Garip wrote:
Hi all, I missed the IRC-meeting yesterday due to unforseen matters.
Regarding HEAD, currently i am not being able to commit to it. I have always been slow in learning the cvs process. When i try to commit its telling me that its newer than my version while its not and i am fed up. 1- Just delete the whole thing. 2-Start a blank rel_TG 3-Most of the stuff allready in files are useless with my edition anyway 4- I will commit everything to rel_TG including my NPL templates as default and NEU specific OPAC as well 5- This way it will be a working rel_TG 6- I will organize the folder structure so do not put the empty folders there either 7- This branch can than be used as it is on its own or for things you may like to backport. 8- If you are not going to use the meta-record structure of this release why bother about 1-7 since i cannot keep it it sync with SAN-OP or rel_3 anyway?
If the above is making anysense than i am prepared to do 4-7 anytime you are ready.
I am veeeeeery busy this month so sorry about late responses. St. Valentines Day is almost here and i havent got her anything yet, I have to rush, see you all. Tumer
________________________________
From: koha-devel-bounces+tgarip=neu.edu.tr@nongnu.org on behalf of Paul POULAIN Sent: Thu 08/02/2007 16:06 To: koha-devel Subject: [Koha-devel] rel_3_0, head & tumer stuff
Hi all,
as you probably know, the CVS tree can have branches. We have - one stable rel_2_2. - one unstable, but actively developped & that will result in official koha 3.0 "soon". - one managed by Tumer Garip, that is, actually in HEAD.
some interesting features from head have been ported to rel_3_0. Many things don't. with rel_3_0 becoming stable, we think we should reorganize the CVS a little bit : - tumer stuff would be branched to a "tumer" branch (rel_TG ?), from actual head. - rel_3_0 will be feature freezed and only bugfixed. - rel_3_0 will be copied to head (overwriting actual head), to be the official HEAD. any interesting stuff from tumer would be ported here from rel_TG
To do this, we have to do things one after the other : - 1st tumer : could you confirm you don't have anything waiting to be commited to head (i've been told that there are things in fact ;-) ). Once it's done, we will be able to : - create rel_TG branch from HEAD - copy all scripts from rel_3_0 to a local HEAD copy - commit all those scripts to have HEAD= rel_3_0.
Once it will have been done : - tumer, you'll have to be carefull to branch your local copy to rel_TG to avoid commiting stuff into head by mistake - we will have rel_3_0 for bugfixes only - we will have HEAD for new ideas & coding.
A last question : does someone candidate to synch stable rel_3_0 into HEAD ? toins may take care of it, but I would prefer someone else (and I remind you that he works with us till july, nothing sure for september -august being for wedding ;-) ). -- Paul POULAIN et Henri Damien LAURENT Consultants indépendants en logiciels libres et bibliothéconomie (http://www.koha-fr.org) Tel : 04 91 31 45 19
_______________________________________________ Koha-devel mailing list Koha-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/koha-devel
_______________________________________________ Koha-devel mailing list Koha-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/koha-devel
OK, If I understand correctly, tumer, you say that we can do the job, you'll commit your stuf into rel_TG branch later, right ? To answer your question "If you are not going to use the meta-record structure of this release why bother about 1-7 since i cannot keep it it sync with SAN-OP or rel_3 anyway", I think we will need that code one day, maybe not as quickly as you, but it's important to have it in CVS to avoid reinventing the wheel in a future. So, the timing now : the operation needs only a few hours I think. BUT [ VERY IMPORTANT] : once it is done, the rel_3_0 branch will be dead *immediatly*. Thus, it's important to be sure that no rel_3_0 developper will be scared by the move. I don't have anything waiting for a commit on rel_3_0 branch atm. Does hdl, LibLime, katipo and or other developper have something waiting ? Otherwise, I could do the job. But i'm waiting for your position. So, pls, tell me ;-) -- Paul POULAIN et Henri Damien LAURENT Consultants indépendants en logiciels libres et bibliothéconomie (http://www.koha-fr.org) Tel : 04 91 31 45 19
participants (3)
-
Paul POULAIN -
Thomas Dukleth -
Tumer Garip