Thread: [limesurvey-developers] Merging 2.0 to master - stopping 1.92+ releases
The leading Open Source survey tool
Brought to you by:
c_schmitz
From: Carsten S. <car...@li...> - 2012-08-10 12:23:52
|
Hello everyone, the number of issues reported for 1.92+ dropped to a couple per weeks - where most issues reported are really minor. Under that point of view I would like to declare 1.92+ mature and und stop 1.92+ releases. In a next move I would merge the 2.0 branch to master upcoming Wednesday - after a last 1.92+ release. Sam Mousa already created a 2.1 branch in our repository which is now open for new features ;). If possible Aaron should merge his extensive changes so far to the new 2.1 branch as soon as possible - so everyone works on the same code base. Does that sounds right to everyone? Any comments or remarks? Please let me know. Best regards from Hamburg/Germany Carsten Schmitz LimeSurvey Project Leader car...@li... http://www.limesurvey.org |
From: Thibault Le M. <Thi...@su...> - 2012-08-10 14:04:20
|
Hi everyone, This is very great news and I also think it is time to switch to 2.x. Though I haven't been able to be active on the community the lasts monthes, I still value all efforts from you contributors so this email is just a way for me to say thanks to all of you who give time to this project. Thibault ----- Message de car...@li... --------- Date : Fri, 10 Aug 2012 14:24:26 +0200 De : Carsten Schmitz <car...@li...> Répondre à : lim...@li... Objet : [limesurvey-developers] Merging 2.0 to master - stopping 1.92+ releases À : lim...@li... > Hello everyone, > > the number of issues reported for 1.92+ dropped to a couple per weeks - > where most issues reported are really minor. > Under that point of view I would like to declare 1.92+ mature and und > stop 1.92+ releases. > > In a next move I would merge the 2.0 branch to master upcoming Wednesday > - after a last 1.92+ release. > > Sam Mousa already created a 2.1 branch in our repository which is now > open for new features ;). If possible Aaron should merge his extensive > changes so far to the new 2.1 branch as soon as possible - so everyone > works on the same code base. > > Does that sounds right to everyone? Any comments or remarks? Please let > me know. > > > Best regards from Hamburg/Germany > > Carsten Schmitz > > LimeSurvey Project Leader > car...@li... > > http://www.limesurvey.org > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > limesurvey-developers mailing list > lim...@li... > https://lists.sourceforge.net/lists/listinfo/limesurvey-developers > ----- Fin du message de car...@li... ----- |
From: Thomas W. <tom...@gm...> - 2012-08-11 00:18:55
|
As long as we can continue to do 1.92+ releases if really needed, I'm fine with eliminating the weekly ones. -Tom On Fri, Aug 10, 2012 at 9:00 AM, Thibault Le Meur < Thi...@su...> wrote: > Hi everyone, > > This is very great news and I also think it is time to switch to 2.x. > > Though I haven't been able to be active on the community the lasts > monthes, I still value all efforts from you contributors so this email > is just a way for me to say thanks to all of you who give time to this > project. > > Thibault > > > ----- Message de car...@li... --------- > Date : Fri, 10 Aug 2012 14:24:26 +0200 > De : Carsten Schmitz <car...@li...> > Répondre à : lim...@li... > Objet : [limesurvey-developers] Merging 2.0 to master - stopping > 1.92+ releases > À : lim...@li... > > > > Hello everyone, > > > > the number of issues reported for 1.92+ dropped to a couple per weeks - > > where most issues reported are really minor. > > Under that point of view I would like to declare 1.92+ mature and und > > stop 1.92+ releases. > > > > In a next move I would merge the 2.0 branch to master upcoming Wednesday > > - after a last 1.92+ release. > > > > Sam Mousa already created a 2.1 branch in our repository which is now > > open for new features ;). If possible Aaron should merge his extensive > > changes so far to the new 2.1 branch as soon as possible - so everyone > > works on the same code base. > > > > Does that sounds right to everyone? Any comments or remarks? Please let > > me know. > > > > > > Best regards from Hamburg/Germany > > > > Carsten Schmitz > > > > LimeSurvey Project Leader > > car...@li... > > > > http://www.limesurvey.org > > > > > > > ------------------------------------------------------------------------------ > > Live Security Virtual Conference > > Exclusive live event will cover all the ways today's security and > > threat landscape has changed and how IT managers can respond. Discussions > > will include endpoint security, mobile security and the latest in malware > > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > > _______________________________________________ > > limesurvey-developers mailing list > > lim...@li... > > https://lists.sourceforge.net/lists/listinfo/limesurvey-developers > > > > > ----- Fin du message de car...@li... ----- > > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > limesurvey-developers mailing list > lim...@li... > https://lists.sourceforge.net/lists/listinfo/limesurvey-developers > |
From: Holger R. <ho...@ro...> - 2012-08-11 16:58:56
|
What does that mean for translations? Does this mean we should move to 2.0 or still 1.92? On Fri, Aug 10, 2012 at 9:18 PM, Thomas White <tom...@gm...>wrote: > As long as we can continue to do 1.92+ releases if really needed, I'm fine > with eliminating the weekly ones. > -Tom > On Fri, Aug 10, 2012 at 9:00 AM, Thibault Le Meur < > Thi...@su...> wrote: > >> Hi everyone, >> >> This is very great news and I also think it is time to switch to 2.x. >> >> Though I haven't been able to be active on the community the lasts >> monthes, I still value all efforts from you contributors so this email >> is just a way for me to say thanks to all of you who give time to this >> project. >> >> Thibault >> >> >> ----- Message de car...@li... --------- >> Date : Fri, 10 Aug 2012 14:24:26 +0200 >> De : Carsten Schmitz <car...@li...> >> Répondre à : lim...@li... >> Objet : [limesurvey-developers] Merging 2.0 to master - stopping >> 1.92+ releases >> À : lim...@li... >> >> >> > Hello everyone, >> > >> > the number of issues reported for 1.92+ dropped to a couple per weeks - >> > where most issues reported are really minor. >> > Under that point of view I would like to declare 1.92+ mature and und >> > stop 1.92+ releases. >> > >> > In a next move I would merge the 2.0 branch to master upcoming Wednesday >> > - after a last 1.92+ release. >> > >> > Sam Mousa already created a 2.1 branch in our repository which is now >> > open for new features ;). If possible Aaron should merge his extensive >> > changes so far to the new 2.1 branch as soon as possible - so everyone >> > works on the same code base. >> > >> > Does that sounds right to everyone? Any comments or remarks? Please let >> > me know. >> > >> > >> > Best regards from Hamburg/Germany >> > >> > Carsten Schmitz >> > >> > LimeSurvey Project Leader >> > car...@li... >> > >> > http://www.limesurvey.org >> > >> > >> > >> ------------------------------------------------------------------------------ >> > Live Security Virtual Conference >> > Exclusive live event will cover all the ways today's security and >> > threat landscape has changed and how IT managers can respond. >> Discussions >> > will include endpoint security, mobile security and the latest in >> malware >> > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> > _______________________________________________ >> > limesurvey-developers mailing list >> > lim...@li... >> > https://lists.sourceforge.net/lists/listinfo/limesurvey-developers >> > >> >> >> ----- Fin du message de car...@li... ----- >> >> >> >> >> ------------------------------------------------------------------------------ >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respond. Discussions >> will include endpoint security, mobile security and the latest in malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> _______________________________________________ >> limesurvey-developers mailing list >> lim...@li... >> https://lists.sourceforge.net/lists/listinfo/limesurvey-developers >> > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > limesurvey-developers mailing list > lim...@li... > https://lists.sourceforge.net/lists/listinfo/limesurvey-developers > > |
From: Denis C. <cou...@sh...> - 2012-08-12 12:57:28
Attachments:
signature.asc
|
Hello, I think it's a good idea : only Priority/High for 1.92 ( or X priority/Normal ;) ) For : 2.1 : can we add some little functionality to 2.0 (like http://bugs.limesurvey.org/view.php?id=6451 ( array filter for ranking). or it's only for 2.1. Or did we fix only bug for 2.0. For 2.1 merging: i don't make last patch for 2.0 AND 2.1, did we have to make patch for both or git merging is OK ? For translation: I think it's OK to ending 1.92 translation and after upload the po file for 2.0 ? Don't know. Denis Le 11/08/2012 18:58, Holger Rothemund a écrit : > What does that mean for translations? Does this mean we should move to > 2.0 or still 1.92? > > On Fri, Aug 10, 2012 at 9:18 PM, Thomas White <tom...@gm... > <mailto:tom...@gm...>> wrote: > > As long as we can continue to do 1.92+ releases if really needed, > I'm fine with eliminating the weekly ones. > -Tom > On Fri, Aug 10, 2012 at 9:00 AM, Thibault Le Meur > <Thi...@su... <mailto:Thi...@su...>> > wrote: > > Hi everyone, > > This is very great news and I also think it is time to switch > to 2.x. > > Though I haven't been able to be active on the community the lasts > monthes, I still value all efforts from you contributors so > this email > is just a way for me to say thanks to all of you who give time > to this > project. > > Thibault > > > ----- Message de car...@li... > <mailto:car...@li...> --------- > Date : Fri, 10 Aug 2012 14:24:26 +0200 > De : Carsten Schmitz <car...@li... > <mailto:car...@li...>> > Répondre à : lim...@li... > <mailto:lim...@li...> > Objet : [limesurvey-developers] Merging 2.0 to master - stopping > 1.92+ releases > À : lim...@li... > <mailto:lim...@li...> > > > > Hello everyone, > > > > the number of issues reported for 1.92+ dropped to a couple > per weeks - > > where most issues reported are really minor. > > Under that point of view I would like to declare 1.92+ > mature and und > > stop 1.92+ releases. > > > > In a next move I would merge the 2.0 branch to master > upcoming Wednesday > > - after a last 1.92+ release. > > > > Sam Mousa already created a 2.1 branch in our repository > which is now > > open for new features ;). If possible Aaron should merge his > extensive > > changes so far to the new 2.1 branch as soon as possible - > so everyone > > works on the same code base. > > > > Does that sounds right to everyone? Any comments or remarks? > Please let > > me know. > > > > > > Best regards from Hamburg/Germany > > > > Carsten Schmitz > > > > LimeSurvey Project Leader > > car...@li... > <mailto:car...@li...> > > > > http://www.limesurvey.org > > > > > > > ------------------------------------------------------------------------------ > > Live Security Virtual Conference > > Exclusive live event will cover all the ways today's > security and > > threat landscape has changed and how IT managers can > respond. Discussions > > will include endpoint security, mobile security and the > latest in malware > > threats. > http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > > _______________________________________________ > > limesurvey-developers mailing list > > lim...@li... > <mailto:lim...@li...> > > > https://lists.sourceforge.net/lists/listinfo/limesurvey-developers > > > > > ----- Fin du message de car...@li... > <mailto:car...@li...> ----- > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. > Discussions > will include endpoint security, mobile security and the latest > in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > limesurvey-developers mailing list > lim...@li... > <mailto:lim...@li...> > https://lists.sourceforge.net/lists/listinfo/limesurvey-developers > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. > Discussions > will include endpoint security, mobile security and the latest in > malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > limesurvey-developers mailing list > lim...@li... > <mailto:lim...@li...> > https://lists.sourceforge.net/lists/listinfo/limesurvey-developers > > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > > > _______________________________________________ > limesurvey-developers mailing list > lim...@li... > https://lists.sourceforge.net/lists/listinfo/limesurvey-developers |
From: Thomas W. <tom...@gm...> - 2012-08-12 13:38:36
|
I'd vote to continue the translations for 1.92 until 2.0 becomes truly stable/mature (probably a few months after the first stable release, if it is anything like 1.92). /Tom On Sat, Aug 11, 2012 at 12:58 PM, Holger Rothemund <ho...@ro...>wrote: > What does that mean for translations? Does this mean we should move to 2.0 > or still 1.92? > > > On Fri, Aug 10, 2012 at 9:18 PM, Thomas White <tom...@gm...>wrote: > >> As long as we can continue to do 1.92+ releases if really needed, I'm >> fine with eliminating the weekly ones. >> -Tom >> On Fri, Aug 10, 2012 at 9:00 AM, Thibault Le Meur < >> Thi...@su...> wrote: >> >>> Hi everyone, >>> >>> This is very great news and I also think it is time to switch to 2.x. >>> >>> Though I haven't been able to be active on the community the lasts >>> monthes, I still value all efforts from you contributors so this email >>> is just a way for me to say thanks to all of you who give time to this >>> project. >>> >>> Thibault >>> >>> >>> ----- Message de car...@li... --------- >>> Date : Fri, 10 Aug 2012 14:24:26 +0200 >>> De : Carsten Schmitz <car...@li...> >>> Répondre à : lim...@li... >>> Objet : [limesurvey-developers] Merging 2.0 to master - stopping >>> 1.92+ releases >>> À : lim...@li... >>> >>> >>> > Hello everyone, >>> > >>> > the number of issues reported for 1.92+ dropped to a couple per weeks - >>> > where most issues reported are really minor. >>> > Under that point of view I would like to declare 1.92+ mature and und >>> > stop 1.92+ releases. >>> > >>> > In a next move I would merge the 2.0 branch to master upcoming >>> Wednesday >>> > - after a last 1.92+ release. >>> > >>> > Sam Mousa already created a 2.1 branch in our repository which is now >>> > open for new features ;). If possible Aaron should merge his extensive >>> > changes so far to the new 2.1 branch as soon as possible - so everyone >>> > works on the same code base. >>> > >>> > Does that sounds right to everyone? Any comments or remarks? Please let >>> > me know. >>> > >>> > >>> > Best regards from Hamburg/Germany >>> > >>> > Carsten Schmitz >>> > >>> > LimeSurvey Project Leader >>> > car...@li... >>> > >>> > http://www.limesurvey.org >>> > >>> > >>> > >>> ------------------------------------------------------------------------------ >>> > Live Security Virtual Conference >>> > Exclusive live event will cover all the ways today's security and >>> > threat landscape has changed and how IT managers can respond. >>> Discussions >>> > will include endpoint security, mobile security and the latest in >>> malware >>> > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >>> > _______________________________________________ >>> > limesurvey-developers mailing list >>> > lim...@li... >>> > https://lists.sourceforge.net/lists/listinfo/limesurvey-developers >>> > >>> >>> >>> ----- Fin du message de car...@li... ----- >>> >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> Live Security Virtual Conference >>> Exclusive live event will cover all the ways today's security and >>> threat landscape has changed and how IT managers can respond. Discussions >>> will include endpoint security, mobile security and the latest in malware >>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >>> _______________________________________________ >>> limesurvey-developers mailing list >>> lim...@li... >>> https://lists.sourceforge.net/lists/listinfo/limesurvey-developers >>> >> >> >> >> ------------------------------------------------------------------------------ >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respond. Discussions >> will include endpoint security, mobile security and the latest in malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> _______________________________________________ >> limesurvey-developers mailing list >> lim...@li... >> https://lists.sourceforge.net/lists/listinfo/limesurvey-developers >> >> > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > limesurvey-developers mailing list > lim...@li... > https://lists.sourceforge.net/lists/listinfo/limesurvey-developers > > |
From: Thomas W. <tom...@gm...> - 2012-08-15 14:42:54
|
What is the value of actually merging the Yii branch into master? Isn't another option to re-name the master branch "1.92", and rename the Yii branch "2.0", and instructing people to commit to the 2.0 branch instead of 1.92? The reason I ask is I'm trying to picture how debugging might be affected after such a merge: (1) In many cases, we have identical commit messages for Yii and master. Will it be easy to search the logs for the Yii vs. 1.92 commits for a particular bug and checkout the right code (e.g. the version right before that fix)? I guess it will be obvious if we've checked out Yii instead of 1.92 (since the code organization is different), but that sounds like a it of a pain and trial and error to get the right version, especially if you need to step back through several code iterations (2) Would that affect the ability to use the git commands that let you find the source of an error (the ones where you write a test case, and you tell git that the error happened sometimes in the last 6 months, and it iteratively checks out code, runs the test, and keeps splitting the difference until it finds the earliest code where the test fails)? (3) If we found we needed to make a high priority fix to 1.92 and to 2.0, would that be harder after merging the 1.92 and Yii branches? Seems you'd need to checkout the final 1.92 branch, make the changes - but then commit them to which branch? At that point, committing to master wouldn't make sense, since master would be based upon Yii, so you'd need to maintain a newly created 1.92plus branch for the critical fix, in which case, why bother merging Yii into 1.92 in the first place. So, I'm not convinced that merging Yii into master gains us anything; and it seems to risk making maintenance considerably harder. Instead, can we just rename the branches and/or simply instruct authors to only commit to the 2.x branches? |