[#23049] - remove duplicated meaning comment
- Fixed in Code Base
- 12 Nov 2018
- Medium
- Build: 3.10-dev
- # 23049
- Diff
- PhilETaylor:patch-47
User tests: Successful: Unsuccessful:
Removed duplicated meaning comment
pretty obvious :)
| Status | New | ⇒ | Pending |
joomla-cms-bot
- | Category | ⇒ | Front End com_contact |
I have tested this item
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/23049.
I have tested this item
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/23049.
| Status | Pending | ⇒ | Ready to Commit |
RTC
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/23049.
RTC
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/23049.
wilsonge
- | Status | Ready to Commit | ⇒ | Fixed in Code Base |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2018-11-12 20:33:07 |
| Closed_By | ⇒ | wilsonge | |
| Labels |
Added:
?
|
||
@wilsonge why did you tag this as 4.0 when it got merged into 3.10? Why at all was this be send against 3.10-dev and not against staging? @PhilETaylor
No idea - I was pretty sure everything was made against staging.
I'm kind confused what staging actually contains, as there is a 3.10 and 4.0 branch too - so always stick to staging or the 4.0-dev branch.
Is there a document that helps developers understand what branches are being used for what purpose?
Always use staging for 3.x stuff, 3.10 is the bridge to 4. Release lead will merge staging in 3.10 when needed. If you do work for 4 the use 4.0-dev
well as 3.10 is over 200 commits behind staging, and 4.0-dev is over 5440 commits behind... someone has a lot of work to do!
not your problem
Are you sure you're not looking at your fork? There's no way in hell there have been 200 commits since 3.9.0 release, when I last branch merged to 3.10.
not your problem
What a bad attitude to have. Its all our problem. Its strange that so few people are actually working on Joomla development, so few ...
@mbabker Im just reporting what I see, and no, this is not my fork:
see: http://screenshot.myjoom.la/672d79e251bf
EDIT: Actually - Im wrong, thats the AHEAD commits, its the other number - much lower 27 :)
Well, your image link is broken, but...
The left side of that bar is commits behind the default branch (staging), right side is commits ahead (and there's a tooltip explaining that). So 3.10 is 27 commits behind and 202 ahead staging.
To point with your finger that someone has a lot of work to do, wasn't a better attitude. Look at yourself before you criticise others
Wow... simply pathetic attitude. And you wonder why people dont contribute to Joomla...
Is there a document that helps developers understand what branches are being used for what purpose?
Yes and GitHub shows you that all the time you do a PR, even when it is a bit hidden now days ;)
https://github.com/joomla/joomla-cms/blob/staging/.github/CONTRIBUTING.md
I have tested this item✅ successfully on 33bedad
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/23049.