Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Joomla! CMS Development
Home
About this group
Apply for group membership
Bugfixes on Github
Options
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
   10 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Nils Rückmann  
View profile  
 More options Mar 24 2012, 11:45 am
From: Nils Rückmann <i...@nils-rueckmann.de>
Date: Sat, 24 Mar 2012 08:45:53 -0700 (PDT)
Local: Sat, Mar 24 2012 11:45 am
Subject: Bugfixes on Github
Print | Individual message | Show original | Report this message | Find messages by this author

After some trouble with sending a bugfix, i'm wondering if there's a
current documentation about how we want to
track bugs, add patches, pull request etc...

On docs.joomla.org we only talk about joomlacode.org


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Rouven Weßling  
View profile  
 More options Mar 24 2012, 11:47 am
From: Rouven Weßling <m...@rouvenwessling.de>
Date: Sat, 24 Mar 2012 16:47:49 +0100
Local: Sat, Mar 24 2012 11:47 am
Subject: Re: [jcms] Bugfixes on Github
Print | Individual message | Show original | Report this message | Find messages by this author

joomlacode is still the point of truth, anything committed will have to go trough it.

Elin was looking into a replacement tracker (github won't cut it) but I don't know how far she got.

Best regards
Rouven

On 24.03.2012, at 16:45, Nils Rückmann wrote:


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Mark Dexter  
View profile  
 More options Mar 24 2012, 12:36 pm
From: Mark Dexter <dextercow...@gmail.com>
Date: Sat, 24 Mar 2012 09:36:30 -0700
Local: Sat, Mar 24 2012 12:36 pm
Subject: Re: [jcms] Bugfixes on Github
Print | Individual message | Show original | Report this message | Find messages by this author

Yes, please use the Joomlacode tracker here:
http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBr....
Thanks! Mark

On Sat, Mar 24, 2012 at 8:47 AM, Rouven Weßling <m...@rouvenwessling.de>wrote:


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
elin  
View profile  
 More options Mar 24 2012, 1:52 pm
From: elin <elin.war...@gmail.com>
Date: Sat, 24 Mar 2012 10:52:46 -0700 (PDT)
Local: Sat, Mar 24 2012 1:52 pm
Subject: Re: [jcms] Bugfixes on Github
Print | Individual message | Show original | Report this message | Find messages by this author

Mark and I are working on the replacement tracker issue but for now we are
still using the current processes although you can add alink to a git hub
diff (these work best). However for most of the JBS testers the actual
patch file is preferred, so if you would do that it would be awesome in
terms of getting things tested.

In ubuntu anyway if you have master as matching the trunk and the branch
you are in with your changes you can do
git diff --no-prefix > myfilename.patch

I think we'd like to standardize on no prefix as much as possible.  I would
guess even once we have a new tracker many jbs people will prefer patches
and thus a good way to get things tested will be to supply patches.

Elin


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Rouven Weßling  
View profile  
 More options Mar 24 2012, 2:25 pm
From: Rouven Weßling <m...@rouvenwessling.de>
Date: Sat, 24 Mar 2012 19:25:11 +0100
Local: Sat, Mar 24 2012 2:25 pm
Subject: Re: [jcms] Bugfixes on Github
Print | Individual message | Show original | Report this message | Find messages by this author

On 24.03.2012, at 18:52, elin wrote:

> I think we'd like to standardize on no prefix as much as possible.  I would guess even once we have a new tracker many jbs people will prefer patches and thus a good way to get things tested will be to supply patches.

According to JM the no prefix patches don't work with Eclipse.

I think we should start considering how to slowly phase out the SVN system. The only thing missing in terms of infrastructure that the SVN repro still offers is the commit mailing list, that'd need be changed.

I wonder how many devs/bug squadder are using SVN vs. git? Maybe a survey would be good.

Rouven


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
elin  
View profile  
 More options Mar 24 2012, 3:08 pm
From: elin <elin.war...@gmail.com>
Date: Sat, 24 Mar 2012 12:08:03 -0700 (PDT)
Local: Sat, Mar 24 2012 3:08 pm
Subject: Re: [jcms] Bugfixes on Github
Print | Individual message | Show original | Report this message | Find messages by this author

They work fine, it is prefixes that cause problems, but the important thing
is to standardize one way or the other since it is annoying to have to
adjust constantly.

SVN really has nothing to do with it, people are happy and comfortable
using it and there is not any particular reason for them to rush to change
as long as testing gets done. That's the most important thing, that people
who do that work be comfortable.  It's just like all b/c issues :P.

Elin


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Hannes Papenberg  
View profile  
 More options Mar 24 2012, 3:19 pm
From: Hannes Papenberg <hackwa...@googlemail.com>
Date: Sat, 24 Mar 2012 20:19:30 +0100
Local: Sat, Mar 24 2012 3:19 pm
Subject: Re: [jcms] Bugfixes on Github
Print | Individual message | Show original | Report this message | Find messages by this author

Maybe with the github api in the platform we could build something that
builds the patches automatically from a pull and can be linked into the
(new) tracker. Maybe even with a handy overview of all active pulls and
their patches...

Hannes
Am 24.03.2012 18:52 schrieb "elin" <elin.war...@gmail.com>:


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Nikolai Plath  
View profile  
 More options Mar 24 2012, 3:24 pm
From: Nikolai Plath <der.el.k...@gmail.com>
Date: Sat, 24 Mar 2012 14:24:20 -0500
Local: Sat, Mar 24 2012 3:24 pm
Subject: Re: [jcms] Bugfixes on Github
Print | Individual message | Show original | Report this message | Find messages by this author

Well.. GitHub creates patches automagically for every pull request - if
they are needed ..

Ian already has created a very simple yet powerful extension for the
Joomla! CMS called patchtester that makes testing patches / pull
requests a breeze. => https://github.com/ianmacl/patchtester

Depending on the new tracker this could be nicely integrated..

Am 24.03.2012 14:19, schrieb Hannes Papenberg:


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
elin  
View profile  
 More options Mar 24 2012, 6:53 pm
From: elin <elin.war...@gmail.com>
Date: Sat, 24 Mar 2012 15:53:18 -0700 (PDT)
Local: Sat, Mar 24 2012 6:53 pm
Subject: Re: [jcms] Bugfixes on Github
Print | Individual message | Show original | Report this message | Find messages by this author

All you need to do is put .diff on the end of the pull url and download
what you get.

Elin


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
El KuKu  
View profile  
 More options Mar 25 2012, 3:32 pm
From: El KuKu <der.el.k...@gmail.com>
Date: Sun, 25 Mar 2012 12:32:56 -0700 (PDT)
Local: Sun, Mar 25 2012 3:32 pm
Subject: Re: Bugfixes on Github
Print | Individual message | Show original | Report this message | Find messages by this author
Yes, that’s what I meant with "automagically" ;)

On 24 Mar, 17:53, elin <elin.war...@gmail.com> wrote:


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google