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 > >> > >> > >
