Thread: [limesurvey-developers] Iimportant information regarding commits (and 1.91-RC6 realease :)
The leading Open Source survey tool
Brought to you by:
c_schmitz
From: Thibault Le M. <Thi...@su...> - 2011-04-11 06:42:53
|
Hi guys, I'd like to let you know that 1.91-RC6 is now released on Sourceforge.net with buildnumber 9986. I also like to remind some important points to the community regarding commits: 1) We now commit our patches to both directory limesurvey/ (stable branch) and limesurvey_dev (unstable branch) because this will workaround some issues while mering the branches and will greatly help the devloppers on the unstable branch since they will always have the very latest version with all fix included. 2) commit messages are not always compliant with the standard which helps generating the Changelog. Common errors include forgetting the "prefix" (which will remove the commit message from the changelog), forget the ticket number, using "Fix" instead of "Fixed", ... moreover there are too much variations in the way we capitalize the messages. I also think it is time to refine this standard commit messages. My proposal For a new translation ================ "New translation: <English name of the language/dialect> <optionnal comment>" For an updated translation ===================== "Updated translation: <English name of the language/dialect> <optionnal comment>" For a new feature: ============= "New feature #xxxxxx: <descriptive line>" where xxxxxx is the full ticket Id related to the feature. The "descriptive line" doesn't include any newline character and is a meaningful description for end-users. Any comment aimed at developpers must be in a separate line beginning with "Dev " or "New feature: <descriptive line>" if not ticket Id was registered for this feature For an updated feature: ================== "Updated feature #xxxxxx: <descriptive line>" where xxxxxx is the full ticket Id related to the feature. The "descriptive line" doesn't include any newline character and is a meaningful description for end-users. Any comment aimed at developpers must be in a separate line beginning with "Dev " or "Updated feature: <descriptive line>" if not ticket Id was registered for this feature For a fix: ======= "Fixed issue #xxxxxx: <descriptive line>" where xxxxxx is the full ticket Id related to the feature. The "descriptive line" doesn't include any newline character and is a meaningful description for end-users. Any comment aimed at developpers must be in a separate line beginning with "Dev " or "Fixed issue: <descriptive line>" if not ticket Id was registered for this feature Let me know if you have any question or comment. Thanks in advance, Thibault |
From: Marcel M. (Limesurvey) <mar...@li...> - 2011-04-11 13:32:49
|
Sounds fine, can you update the according wiki page? Best regards, Marcel Am 11.04.2011 08:42, schrieb Thibault Le Meur: > Hi guys, > > I'd like to let you know that 1.91-RC6 is now released on > Sourceforge.net with buildnumber 9986. > > I also like to remind some important points to the community regarding > commits: > > 1) We now commit our patches to both directory limesurvey/ (stable > branch) and limesurvey_dev (unstable branch) because this will > workaround some issues while mering the branches and will greatly help > the devloppers on the unstable branch since they will always have the > very latest version with all fix included. > > 2) commit messages are not always compliant with the standard which > helps generating the Changelog. > Common errors include forgetting the "prefix" (which will remove the > commit message from the changelog), forget the ticket number, using > "Fix" instead of "Fixed", ... moreover there are too much variations in > the way we capitalize the messages. > > I also think it is time to refine this standard commit messages. My proposal > > For a new translation > ================ > > "New translation:<English name of the language/dialect> <optionnal > comment>" > > For an updated translation > ===================== > > "Updated translation:<English name of the language/dialect> <optionnal > comment>" > > For a new feature: > ============= > > "New feature #xxxxxx:<descriptive line>" where xxxxxx is the full > ticket Id related to the feature. The "descriptive line" doesn't include > any newline character and is a meaningful description for end-users. > Any comment aimed at developpers must be in a separate line beginning > with "Dev " > > or > > "New feature:<descriptive line>" if not ticket Id was registered for > this feature > > > For an updated feature: > ================== > > "Updated feature #xxxxxx:<descriptive line>" where xxxxxx is the full > ticket Id related to the feature. The "descriptive line" doesn't include > any newline character and is a meaningful description for end-users. > Any comment aimed at developpers must be in a separate line beginning > with "Dev " > > or > > "Updated feature:<descriptive line>" if not ticket Id was registered > for this feature > > For a fix: > ======= > > "Fixed issue #xxxxxx:<descriptive line>" where xxxxxx is the full > ticket Id related to the feature. The "descriptive line" doesn't include > any newline character and is a meaningful description for end-users. > Any comment aimed at developpers must be in a separate line beginning > with "Dev " > > or > > "Fixed issue:<descriptive line>" if not ticket Id was registered for > this feature > > > Let me know if you have any question or comment. > > Thanks in advance, > Thibault > > ------------------------------------------------------------------------------ > Xperia(TM) PLAY > It's a major breakthrough. An authentic gaming > smartphone on the nation's most reliable network. > And it wants your games. > http://p.sf.net/sfu/verizon-sfdev > _______________________________________________ > limesurvey-developers mailing list > lim...@li... > https://lists.sourceforge.net/lists/listinfo/limesurvey-developers > > |