Re: [Dicuss] Github stats and lack of visibility by working not working in trunk/master
On Mon, May 13, 2013 at 3:32 PM, Justin Mclean jus...@classsoftware.comwrote: Hi, Cant we just remove it in our repo and let the mirroring process take care of it on github? I'll give it a go but I don't think branch changes are being mirrored in github. Can you point out some examples (with urls) of this issue? Will be easier for Infra to find out what is going wrong. eg No develop branch in TLF - although this may be that it still synced up with SVN and not Git. Thanks, Justin FYI, I have pinged Infra with these requests and I have updated the JIRA ticket here [1] Thanks, Om [1] https://issues.apache.org/jira/browse/INFRA-6108
Re: [Dicuss] Github stats and lack of visibility by working not working in trunk/master
Hi, Cant we just remove it in our repo and let the mirroring process take care of it on github? I'll give it a go but I don't think branch changes are being mirrored in github. Yep the github been updated but patches branch has not been removed. I'd guess it does't remove old branches and perhaps not pick up new branches. Good news it that it syncs other changes quick quickly. Thanks, Justin
Re: [Dicuss] Github stats and lack of visibility by working not working in trunk/master
Hi Justin, -1 to move to old trunk svn layout. People comming to this project could came from SVN or GIT background, so reverting to trunk while we are on GIT will be the cause of more confusion. Nowadays, people should take into account the conventions over configurations, and master/develop names are the GIT conventions. 2013/5/13 Justin Mclean jus...@classsoftware.com Hi, Is there anyway to change the stats on these pages: https://github.com/apache/flex-sdk/graphs So that they work off develop not trunk. (And for the other repos as well.) It's sort of giving the wrong idea (in a public way) re activity on the project. Alternatively what do people think about moving back to working in trunk and have a new branch that's the latest released version (which what trunk currently is). This would cause less confusion to new people on the project as there's been a couple of develop/trunk issues in the past and it's come up a few times on twitter I've seen. Thanks, Justin -- Carlos Rovira Director de Tecnología M: +34 607 22 60 05 F: +34 912 94 80 80 http://www.codeoscopic.com http://www.directwriter.es http://www.avant2.es
Re: [Dicuss] Github stats and lack of visibility by working not working in trunk/master
-1 We've a Git repo, and master develop is the regular structure. We must avoid mixing the things, to avoid the confusion increment -- Jose Barragan Chief Software Architect Codeoscopic Madrid C/. Infanta Mercedes, 92. Planta 5. 505. 28020 Madrid. Tel.: +34 912 94 80 80 On May 13, 2013, at 9:46 AM, Carlos Rovira carlos.rov...@codeoscopic.com wrote: Hi Justin, -1 to move to old trunk svn layout. People comming to this project could came from SVN or GIT background, so reverting to trunk while we are on GIT will be the cause of more confusion. Nowadays, people should take into account the conventions over configurations, and master/develop names are the GIT conventions. 2013/5/13 Justin Mclean jus...@classsoftware.com Hi, Is there anyway to change the stats on these pages: https://github.com/apache/flex-sdk/graphs So that they work off develop not trunk. (And for the other repos as well.) It's sort of giving the wrong idea (in a public way) re activity on the project. Alternatively what do people think about moving back to working in trunk and have a new branch that's the latest released version (which what trunk currently is). This would cause less confusion to new people on the project as there's been a couple of develop/trunk issues in the past and it's come up a few times on twitter I've seen. Thanks, Justin -- Carlos Rovira Director de Tecnología M: +34 607 22 60 05 F: +34 912 94 80 80 http://www.codeoscopic.com http://www.directwriter.es http://www.avant2.es
Re: [Dicuss] Github stats and lack of visibility by working not working in trunk/master
HI, We've a Git repo, and master develop is the regular structure. Then why does github assume trunk is the default and not develop? Can we get this changed? Every other major Apache project I've looked at uses trunk/master for regular updates: https://github.com/apache/lucene-solr https://github.com/apache/httpd https://github.com/apache/ant https://github.com/apache/subversion https://github.com/apache/cassandra https://github.com/apache/maven https://github.com/apache/couchdb Why are we special/different? We must avoid mixing the things, to avoid the confusion increment How does working in develop avoid this especially as we have to merge into trunk on each release. -1 to move to old trunk svn layout. I'm not suggesting that, I just suggestion that everyday work happen in the trunk/master branch rather than the develop branch as this is the branch that tools and people tend to look at by default to see what's going on. Thanks, Justin
Re: [Dicuss] Github stats and lack of visibility by working not working in trunk/master
Hi, We've a Git repo, and master develop is the regular structure. Can you point to a single other Apache project that has the same structure on github as us? Or any other project for that matter? We currently have 3 main branches in github they are master, trunk and develop which is rather confusing IMO. Their is also a release 4.9 branch and a patches branch and tags for the other releases. We seem to be missing a 4.8 branch in github. The patches branch probably should be deleted. Thanks, Justin
Re: [Dicuss] Github stats and lack of visibility by working not working in trunk/master
On May 13, 2013 2:20 AM, Justin Mclean jus...@classsoftware.com wrote: Hi, Because those repos are svn mirroring in git/github they're not really Git repos Cassandra, mavin and couchdb I believe use Git as their primary VC system (but not 100% sure) and are not SVN mirrors. in fact, if you review our flex-sdk repo in GitHub, you can found a trunk branch, from svn legacy. Yes and I think this should be deleted. We don't need a both a master and a trunk. That's just confusing. Well, most of Git applications, assumes these structure (master/develop/origin) to work, and is global agreement of use So currently our release procedure is incorrect and confusing (checking out of svn, merge into trunk etc etc ). https://cwiki.apache.org/FLEX/release-guide-for-the-sdk.html Can someone who knows git please correct this. Even if we remove the trunk branch how do we make github default to the develop branch? There are 3 options I see here. 1. Remove github mirrors altogether. 2. Change github to default to the development branch and delete trunk and patches branches. 3. Make all changes in master rather than develop. Continuing as we have been is not an option as it just causes confusion and give the wrong impression of progress/work to the wider community. but master must be preserved it's a Git requeriment. And that should stay. Thanks, Justin Once again, Git != GitHub. We should not make any changes to our repo to accommodate GitHub. Unless we have write privileges on this GitHub, like we do for the whiteboard repos wet have been working on. We can ask Infra to make minor tweaks like adding better descriptions to these github repos, and making develop as the default visible branch, etc. Other than that we should not spend more time on this 'issue'. Thanks, Om
Re: [Dicuss] Github stats and lack of visibility by working not working in trunk/master
+1 2013/5/13 OmPrakash Muppirala bigosma...@gmail.com On May 13, 2013 2:20 AM, Justin Mclean jus...@classsoftware.com wrote: Hi, Because those repos are svn mirroring in git/github they're not really Git repos Cassandra, mavin and couchdb I believe use Git as their primary VC system (but not 100% sure) and are not SVN mirrors. in fact, if you review our flex-sdk repo in GitHub, you can found a trunk branch, from svn legacy. Yes and I think this should be deleted. We don't need a both a master and a trunk. That's just confusing. Well, most of Git applications, assumes these structure (master/develop/origin) to work, and is global agreement of use So currently our release procedure is incorrect and confusing (checking out of svn, merge into trunk etc etc ). https://cwiki.apache.org/FLEX/release-guide-for-the-sdk.html Can someone who knows git please correct this. Even if we remove the trunk branch how do we make github default to the develop branch? There are 3 options I see here. 1. Remove github mirrors altogether. 2. Change github to default to the development branch and delete trunk and patches branches. 3. Make all changes in master rather than develop. Continuing as we have been is not an option as it just causes confusion and give the wrong impression of progress/work to the wider community. but master must be preserved it's a Git requeriment. And that should stay. Thanks, Justin Once again, Git != GitHub. We should not make any changes to our repo to accommodate GitHub. Unless we have write privileges on this GitHub, like we do for the whiteboard repos wet have been working on. We can ask Infra to make minor tweaks like adding better descriptions to these github repos, and making develop as the default visible branch, etc. Other than that we should not spend more time on this 'issue'. Thanks, Om -- Carlos Rovira Director de Tecnología M: +34 607 22 60 05 F: +34 912 94 80 80 http://www.codeoscopic.com http://www.directwriter.es http://www.avant2.es
Re: [Dicuss] Github stats and lack of visibility by working not working in trunk/master
Hi, Once again, Git != GitHub. So we should either support it or not support it. Having a mirror in Github and not supporting it reflects badly on the project. We should not make any changes to our repo to accommodate GitHub. Then we shouldn't support it and remove it. Is that what you want? Other than that we should not spend more time on this 'issue'. This is an issue because it's seen by the wider community. I agree it's mostly irrelevant to active committers but it is an issue for someone who does a pull request and that request is ignored for several months. It an issue because github says no changes have happened in the project for 3 months (and people tweet about it) when the actual fact is that changes happen every other day. Justin
Re: [Dicuss] Github stats and lack of visibility by working not working in trunk/master
Other than that we should not spend more time on this 'issue'. This is an issue because it's seen by the wider community. I agree it's mostly irrelevant to active committers but it is an issue for someone who does a pull request and that request is ignored for several months. It an issue because github says no changes have happened in the project for 3 months (and people tweet about it) when the actual fact is that changes happen every other day. A quick tour of search results shows that there is no way to get the graph to show a branch but implies that we will see all the last several months of activity in the graph when we merge the next release with trunk/master. Maybe that's one reason Cordova releases every month, or at least it is a side benefit? So let's see if we can get this next release out ASAP. And then if GitHub refuses to show activity then I would vote to not use GitHub as a mirror. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [Dicuss] Github stats and lack of visibility by working not working in trunk/master
On May 13, 2013 7:30 AM, Justin Mclean jus...@classsoftware.com wrote: Hi, Once again, Git != GitHub. So we should either support it or not support it. Having a mirror in Github and not supporting it reflects badly on the project. Define 'support'. How much support does a reasonable person expect from a 'mirror'? We should not make any changes to our repo to accommodate GitHub. Then we shouldn't support it and remove it. Is that what you want? I would leave it as it is and better educate folks about these mirrors in our documentation and website. Other than that we should not spend more time on this 'issue'. This is an issue because it's seen by the wider community. I agree it's mostly irrelevant to active committers but it is an issue for someone who does a pull request and that request is ignored for several months. It an issue because github says no changes have happened in the project for 3 months (and people tweet about it) when the actual fact is that changes happen every other day. Nothing you mention cannot be solved by some settings changes on GitHub and proper education/documentation of our process. It is a simple setting in GitHub to show a particular branch by default. But you need admin access for that, i.e. we will have to ask Infra to do this for us. For example, look at this repo: https://github.com/apacheflex/whiteboard_fthomas_developerToolSuite This shows the 'develop' branch by default. You can go into the 'Graphs' tab to see the activity in the 'develop' branch. GitHub apparently shows the graph only for the default branch. Also, every GitHub project has a description field where we can say in bold letters that we do not accept 'Pull requests' because it is a read-only mirorr. Again, Infra can make this change for us. For example, this repo: https://github.com/bigosmallm/MakeApacheFlexForFlashBuilder has info about the fact that active development is happening elsewhere. Thanks, Om
Re: [Dicuss] Github stats and lack of visibility by working not working in trunk/master
On Mon, May 13, 2013 at 8:52 AM, Alex Harui aha...@adobe.com wrote: Other than that we should not spend more time on this 'issue'. This is an issue because it's seen by the wider community. I agree it's mostly irrelevant to active committers but it is an issue for someone who does a pull request and that request is ignored for several months. It an issue because github says no changes have happened in the project for 3 months (and people tweet about it) when the actual fact is that changes happen every other day. A quick tour of search results shows that there is no way to get the graph to show a branch This is a quirk of GitHub. Once the default branch is changed to 'develop', the graphs will start showing activity for develop. but implies that we will see all the last several months of activity in the graph when we merge the next release with trunk/master. Maybe that's one reason Cordova releases every month, or at least it is a side benefit? So let's see if we can get this next release out ASAP. And then if GitHub refuses to show activity then I would vote to not use GitHub as a mirror. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [Dicuss] Github stats and lack of visibility by working not working in trunk/master
Om, you seem to know what needs to be done, can you make sure the required changes get made? On 5/13/13 11:10 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Mon, May 13, 2013 at 8:52 AM, Alex Harui aha...@adobe.com wrote: Other than that we should not spend more time on this 'issue'. This is an issue because it's seen by the wider community. I agree it's mostly irrelevant to active committers but it is an issue for someone who does a pull request and that request is ignored for several months. It an issue because github says no changes have happened in the project for 3 months (and people tweet about it) when the actual fact is that changes happen every other day. A quick tour of search results shows that there is no way to get the graph to show a branch This is a quirk of GitHub. Once the default branch is changed to 'develop', the graphs will start showing activity for develop. but implies that we will see all the last several months of activity in the graph when we merge the next release with trunk/master. Maybe that's one reason Cordova releases every month, or at least it is a side benefit? So let's see if we can get this next release out ASAP. And then if GitHub refuses to show activity then I would vote to not use GitHub as a mirror. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [Dicuss] Github stats and lack of visibility by working not working in trunk/master
On Mon, May 13, 2013 at 11:15 AM, Alex Harui aha...@adobe.com wrote: Om, you seem to know what needs to be done, can you make sure the required changes get made? I will as soon as we arrive at consensus here. Infra requests usually take time and I want to get what we want in one go :-) Thanks, Om On 5/13/13 11:10 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Mon, May 13, 2013 at 8:52 AM, Alex Harui aha...@adobe.com wrote: Other than that we should not spend more time on this 'issue'. This is an issue because it's seen by the wider community. I agree it's mostly irrelevant to active committers but it is an issue for someone who does a pull request and that request is ignored for several months. It an issue because github says no changes have happened in the project for 3 months (and people tweet about it) when the actual fact is that changes happen every other day. A quick tour of search results shows that there is no way to get the graph to show a branch This is a quirk of GitHub. Once the default branch is changed to 'develop', the graphs will start showing activity for develop. but implies that we will see all the last several months of activity in the graph when we merge the next release with trunk/master. Maybe that's one reason Cordova releases every month, or at least it is a side benefit? So let's see if we can get this next release out ASAP. And then if GitHub refuses to show activity then I would vote to not use GitHub as a mirror. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [Dicuss] Github stats and lack of visibility by working not working in trunk/master
Can we do it in two pieces? The first part is the subject of this email: Can we get the develop branch as the default and the graphs showing the develop branch activity? I guess that could also include removal of the trunk if that's old SVN stuff. I think we have consensus on this? The second part is about pull requests, and I think that will require some experimentation and will take longer to settle. Did I miss a topic? Anyway, if you agree, can you take care of that first part? Thanks, -Alex On 5/13/13 11:17 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Mon, May 13, 2013 at 11:15 AM, Alex Harui aha...@adobe.com wrote: Om, you seem to know what needs to be done, can you make sure the required changes get made? I will as soon as we arrive at consensus here. Infra requests usually take time and I want to get what we want in one go :-) Thanks, Om On 5/13/13 11:10 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Mon, May 13, 2013 at 8:52 AM, Alex Harui aha...@adobe.com wrote: Other than that we should not spend more time on this 'issue'. This is an issue because it's seen by the wider community. I agree it's mostly irrelevant to active committers but it is an issue for someone who does a pull request and that request is ignored for several months. It an issue because github says no changes have happened in the project for 3 months (and people tweet about it) when the actual fact is that changes happen every other day. A quick tour of search results shows that there is no way to get the graph to show a branch This is a quirk of GitHub. Once the default branch is changed to 'develop', the graphs will start showing activity for develop. but implies that we will see all the last several months of activity in the graph when we merge the next release with trunk/master. Maybe that's one reason Cordova releases every month, or at least it is a side benefit? So let's see if we can get this next release out ASAP. And then if GitHub refuses to show activity then I would vote to not use GitHub as a mirror. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [Dicuss] Github stats and lack of visibility by working not working in trunk/master
Sounds sensible enough ;-) Just adding my voice to the consensus. EdB On Mon, May 13, 2013 at 8:24 PM, Alex Harui aha...@adobe.com wrote: Can we do it in two pieces? The first part is the subject of this email: Can we get the develop branch as the default and the graphs showing the develop branch activity? I guess that could also include removal of the trunk if that's old SVN stuff. I think we have consensus on this? The second part is about pull requests, and I think that will require some experimentation and will take longer to settle. Did I miss a topic? Anyway, if you agree, can you take care of that first part? Thanks, -Alex On 5/13/13 11:17 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Mon, May 13, 2013 at 11:15 AM, Alex Harui aha...@adobe.com wrote: Om, you seem to know what needs to be done, can you make sure the required changes get made? I will as soon as we arrive at consensus here. Infra requests usually take time and I want to get what we want in one go :-) Thanks, Om On 5/13/13 11:10 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Mon, May 13, 2013 at 8:52 AM, Alex Harui aha...@adobe.com wrote: Other than that we should not spend more time on this 'issue'. This is an issue because it's seen by the wider community. I agree it's mostly irrelevant to active committers but it is an issue for someone who does a pull request and that request is ignored for several months. It an issue because github says no changes have happened in the project for 3 months (and people tweet about it) when the actual fact is that changes happen every other day. A quick tour of search results shows that there is no way to get the graph to show a branch This is a quirk of GitHub. Once the default branch is changed to 'develop', the graphs will start showing activity for develop. but implies that we will see all the last several months of activity in the graph when we merge the next release with trunk/master. Maybe that's one reason Cordova releases every month, or at least it is a side benefit? So let's see if we can get this next release out ASAP. And then if GitHub refuses to show activity then I would vote to not use GitHub as a mirror. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
Re: [Dicuss] Github stats and lack of visibility by working not working in trunk/master
On Mon, May 13, 2013 at 11:24 AM, Alex Harui aha...@adobe.com wrote: Can we do it in two pieces? The first part is the subject of this email: Can we get the develop branch as the default and the graphs showing the develop branch activity? I guess you meant this for flex-sdk. What about the others? Maybe we should list them and get everything set up properly at the same time. I guess that could also include removal of the trunk if that's old SVN stuff. I think we have consensus on this? Not sure what you mean by 'removal of trunk'. If we remove it from our apache git repo, it will automatically be removed from the GitHub mirror during the next sync. We dont need to ask Infra for this. That brings us to the question - do we really want to remove the 'trunk' branch? That is where the SVN history is (we were doing active development on the svn trunk for a period of time) We can remove it if we are okay with going back to our old, now read-only SVN repo for any related history. The second part is about pull requests, and I think that will require some experimentation and will take longer to settle. Did I miss a topic? Anyway, if you agree, can you take care of that first part? Thanks, -Alex On 5/13/13 11:17 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Mon, May 13, 2013 at 11:15 AM, Alex Harui aha...@adobe.com wrote: Om, you seem to know what needs to be done, can you make sure the required changes get made? I will as soon as we arrive at consensus here. Infra requests usually take time and I want to get what we want in one go :-) Thanks, Om On 5/13/13 11:10 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Mon, May 13, 2013 at 8:52 AM, Alex Harui aha...@adobe.com wrote: Other than that we should not spend more time on this 'issue'. This is an issue because it's seen by the wider community. I agree it's mostly irrelevant to active committers but it is an issue for someone who does a pull request and that request is ignored for several months. It an issue because github says no changes have happened in the project for 3 months (and people tweet about it) when the actual fact is that changes happen every other day. A quick tour of search results shows that there is no way to get the graph to show a branch This is a quirk of GitHub. Once the default branch is changed to 'develop', the graphs will start showing activity for develop. but implies that we will see all the last several months of activity in the graph when we merge the next release with trunk/master. Maybe that's one reason Cordova releases every month, or at least it is a side benefit? So let's see if we can get this next release out ASAP. And then if GitHub refuses to show activity then I would vote to not use GitHub as a mirror. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [Dicuss] Github stats and lack of visibility by working not working in trunk/master
On 5/13/13 11:31 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Mon, May 13, 2013 at 11:24 AM, Alex Harui aha...@adobe.com wrote: Can we do it in two pieces? The first part is the subject of this email: Can we get the develop branch as the default and the graphs showing the develop branch activity? I guess you meant this for flex-sdk. What about the others? Maybe we should list them and get everything set up properly at the same time. OK, can you do that? Or is there controversy? Flex-falcon and flex-asjs are also using develop branches Flex-tlf is not and there isn't much activity there Same for flex-external. I guess that could also include removal of the trunk if that's old SVN stuff. I think we have consensus on this? Not sure what you mean by 'removal of trunk'. If we remove it from our apache git repo, it will automatically be removed from the GitHub mirror during the next sync. We dont need to ask Infra for this. That brings us to the question - do we really want to remove the 'trunk' branch? That is where the SVN history is (we were doing active development on the svn trunk for a period of time) We can remove it if we are okay with going back to our old, now read-only SVN repo for any related history. OK, sounds like we can skip this for now. The second part is about pull requests, and I think that will require some experimentation and will take longer to settle. Did I miss a topic? Anyway, if you agree, can you take care of that first part? Thanks, -Alex On 5/13/13 11:17 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Mon, May 13, 2013 at 11:15 AM, Alex Harui aha...@adobe.com wrote: Om, you seem to know what needs to be done, can you make sure the required changes get made? I will as soon as we arrive at consensus here. Infra requests usually take time and I want to get what we want in one go :-) Thanks, Om On 5/13/13 11:10 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Mon, May 13, 2013 at 8:52 AM, Alex Harui aha...@adobe.com wrote: Other than that we should not spend more time on this 'issue'. This is an issue because it's seen by the wider community. I agree it's mostly irrelevant to active committers but it is an issue for someone who does a pull request and that request is ignored for several months. It an issue because github says no changes have happened in the project for 3 months (and people tweet about it) when the actual fact is that changes happen every other day. A quick tour of search results shows that there is no way to get the graph to show a branch This is a quirk of GitHub. Once the default branch is changed to 'develop', the graphs will start showing activity for develop. but implies that we will see all the last several months of activity in the graph when we merge the next release with trunk/master. Maybe that's one reason Cordova releases every month, or at least it is a side benefit? So let's see if we can get this next release out ASAP. And then if GitHub refuses to show activity then I would vote to not use GitHub as a mirror. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [Dicuss] Github stats and lack of visibility by working not working in trunk/master
On Mon, May 13, 2013 at 11:43 AM, Jose Barragan jose.barra...@codeoscopic.com wrote: Hi Om, In fact in our writable repo, doesn't have any branch called trunk, but we have one in Github, and is the default branch (this is the origin of this thread). That seems to an artifact from the days when we had our GitHub mirror pointing to SVN (i.e. pre git move) I will ping Infra and have them clean it up. Thanks, Om -- Jose Barragan Chief Software Architect Codeoscopic Madrid C/. Infanta Mercedes, 92. Planta 5. 505. 28020 Madrid. Tel.: +34 912 94 80 80 On May 13, 2013, at 8:31 PM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Mon, May 13, 2013 at 11:24 AM, Alex Harui aha...@adobe.com wrote: Can we do it in two pieces? The first part is the subject of this email: Can we get the develop branch as the default and the graphs showing the develop branch activity? I guess you meant this for flex-sdk. What about the others? Maybe we should list them and get everything set up properly at the same time. I guess that could also include removal of the trunk if that's old SVN stuff. I think we have consensus on this? Not sure what you mean by 'removal of trunk'. If we remove it from our apache git repo, it will automatically be removed from the GitHub mirror during the next sync. We dont need to ask Infra for this. That brings us to the question - do we really want to remove the 'trunk' branch? That is where the SVN history is (we were doing active development on the svn trunk for a period of time) We can remove it if we are okay with going back to our old, now read-only SVN repo for any related history. The second part is about pull requests, and I think that will require some experimentation and will take longer to settle. Did I miss a topic? Anyway, if you agree, can you take care of that first part? Thanks, -Alex On 5/13/13 11:17 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Mon, May 13, 2013 at 11:15 AM, Alex Harui aha...@adobe.com wrote: Om, you seem to know what needs to be done, can you make sure the required changes get made? I will as soon as we arrive at consensus here. Infra requests usually take time and I want to get what we want in one go :-) Thanks, Om On 5/13/13 11:10 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Mon, May 13, 2013 at 8:52 AM, Alex Harui aha...@adobe.com wrote: Other than that we should not spend more time on this 'issue'. This is an issue because it's seen by the wider community. I agree it's mostly irrelevant to active committers but it is an issue for someone who does a pull request and that request is ignored for several months. It an issue because github says no changes have happened in the project for 3 months (and people tweet about it) when the actual fact is that changes happen every other day. A quick tour of search results shows that there is no way to get the graph to show a branch This is a quirk of GitHub. Once the default branch is changed to 'develop', the graphs will start showing activity for develop. but implies that we will see all the last several months of activity in the graph when we merge the next release with trunk/master. Maybe that's one reason Cordova releases every month, or at least it is a side benefit? So let's see if we can get this next release out ASAP. And then if GitHub refuses to show activity then I would vote to not use GitHub as a mirror. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [Dicuss] Github stats and lack of visibility by working not working in trunk/master
On Mon, May 13, 2013 at 11:45 AM, Alex Harui aha...@adobe.com wrote: On 5/13/13 11:31 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Mon, May 13, 2013 at 11:24 AM, Alex Harui aha...@adobe.com wrote: Can we do it in two pieces? The first part is the subject of this email: Can we get the develop branch as the default and the graphs showing the develop branch activity? I guess you meant this for flex-sdk. What about the others? Maybe we should list them and get everything set up properly at the same time. OK, can you do that? Or is there controversy? Flex-falcon and flex-asjs are also using develop branches Flex-tlf is not and there isn't much activity there Same for flex-external. And flex-utilities, we can stick with master as the default branch. I guess that could also include removal of the trunk if that's old SVN stuff. I think we have consensus on this? Not sure what you mean by 'removal of trunk'. If we remove it from our apache git repo, it will automatically be removed from the GitHub mirror during the next sync. We dont need to ask Infra for this. That brings us to the question - do we really want to remove the 'trunk' branch? That is where the SVN history is (we were doing active development on the svn trunk for a period of time) We can remove it if we are okay with going back to our old, now read-only SVN repo for any related history. OK, sounds like we can skip this for now. The second part is about pull requests, and I think that will require some experimentation and will take longer to settle. Did I miss a topic? Anyway, if you agree, can you take care of that first part? Thanks, -Alex On 5/13/13 11:17 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Mon, May 13, 2013 at 11:15 AM, Alex Harui aha...@adobe.com wrote: Om, you seem to know what needs to be done, can you make sure the required changes get made? I will as soon as we arrive at consensus here. Infra requests usually take time and I want to get what we want in one go :-) Thanks, Om On 5/13/13 11:10 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Mon, May 13, 2013 at 8:52 AM, Alex Harui aha...@adobe.com wrote: Other than that we should not spend more time on this 'issue'. This is an issue because it's seen by the wider community. I agree it's mostly irrelevant to active committers but it is an issue for someone who does a pull request and that request is ignored for several months. It an issue because github says no changes have happened in the project for 3 months (and people tweet about it) when the actual fact is that changes happen every other day. A quick tour of search results shows that there is no way to get the graph to show a branch This is a quirk of GitHub. Once the default branch is changed to 'develop', the graphs will start showing activity for develop. but implies that we will see all the last several months of activity in the graph when we merge the next release with trunk/master. Maybe that's one reason Cordova releases every month, or at least it is a side benefit? So let's see if we can get this next release out ASAP. And then if GitHub refuses to show activity then I would vote to not use GitHub as a mirror. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [Dicuss] Github stats and lack of visibility by working not working in trunk/master
Hi, Sound good on the github changes. flex-tlf: master This also has a develop branch (in git but not in github) - shouldn't that be the default? 2. Ask Infra to clean up the 'trunk' branch from the flex-sdk GitHub mirror. Also ask to remove patches branch as well (not essential). I think there's another issue here in that new branches are not been carried across into github. This seems to be happening with other projects.. Justin
Re: [Dicuss] Github stats and lack of visibility by working not working in trunk/master
Hi, The second part is about pull requests, and I think that will require some experimentation and will take longer to settle. Issue as I see them are: 1. No visibility of pull requests - we had requests sit there for months unnoticed. Ideally it should mail the mailing list when a pull request occurs. 2. Someway of closing pull requests or indication they have been acted on. Did I miss a topic? Our release process documentation (including instructions on branching and merging) still refers to SVN and not Git. Thanks, Justin
