Thanks Gabor, I look forward to having this issue fixed soon.
Padre Dev Team, I am thinking about skipping this bug and moving forward with a release because this bug is not consistently reproducible in Windows 10 and I was not able to reproduce the bug in Ubuntu linux 14.04. Since we are in sort of a maintenance release phase we can move forward with the current fixes in Padre 1.01 and then just release a few set of fixes in the near future. Hopefully announcing a new release of Padre to the public will add more traffic to Padre irc chat rooms/mailing list with developers who have issues or bug fixes ready to be applied. Last release of Padre ( 1.00 ) was on Nov 2013 and if I am not mistaken we have changes in Padre 1.01 that resolves some issues from Padre 1.00 so we should definitely move forward. I am open for suggestions and concerns on this approach. Charlie Gonzalez (E) itchar...@gmail.com Github Profile <https://github.com/itcharlie> On Sun, Feb 28, 2016 at 1:57 AM, Gabor Szabo <ga...@szabgab.com> wrote: > Hi Charlie, > > thanks for working on Padre. > > By the time you have the release ready to upload I'll give you the > necessary rights on PAUSE. > Marking the release with a tag is fine, as far as I remember the tagging > in SVN was the same as branching. That's why we had that. > > As of the the Mac issues, I've been using Mac for a few years now and so > far have not managed to make Padre work, but I have no tried > it too hard either. > > The crash you mentioned sound a critical bug to me too :) > > I hope you'll be able to fix it soon. > > regards > Gabor > > > > On Sun, Feb 28, 2016 at 5:14 AM, Charlie Gonzalez <itchar...@gmail.com> > wrote: > >> Hi Claudio, >> >> Thanks for your response. I started doing some testing myself and sent >> out an email recently of a bug that is ( what I believe ) critical to fix >> before the next release of Padre. >> >> Yes I agree with you in regards to tagging for a release.We can go with >> tags for now since not much development activity is going on at the moment. >> >> If I don't get access to cpan, I can generate the distribution file and >> give it to one of the maintainers so they can upload to cpan. >> >> I will keep the Padre version to 1.01 unless someone disagrees and has a >> good argument against it. >> >> I hope to figure out how 'Padre crashes when opening a file' soon if not >> I'll have to wait for someone with more experience to get involved. >> >> Feel free to test in Mac and document the issues via Padre github issues >> page >> >> Best, >> Charlie >> >> Charlie Gonzalez >> (E) itchar...@gmail.com >> Github Profile <https://github.com/itcharlie> >> >> >> On Fri, Feb 26, 2016 at 4:46 AM, Claudio Ramirez < >> padre.clau...@apt-get.be> wrote: >> >>> Hi Chartlie, >>> >>> Big kudos for pushing the padre development forward. Great news. >>> >>> My 2 cents for your questions: >>> >>> 1. This are the people with PAUSE ownership: >>> *module**userid**type**owner*Padre >>> <https://pause.perl.org/pause/authenquery?pause99_peek_perms_by=me&pause99_peek_perms_query=Padre&pause99_peek_perms_sub=1> >>> ADAMK >>> <https://pause.perl.org/pause/authenquery?pause99_peek_perms_by=a&pause99_peek_perms_query=ADAMK&pause99_peek_perms_sub=1> >>> co-maint SZABGAB Padre >>> <https://pause.perl.org/pause/authenquery?pause99_peek_perms_by=me&pause99_peek_perms_query=Padre&pause99_peek_perms_sub=1> >>> AZAWAWI >>> <https://pause.perl.org/pause/authenquery?pause99_peek_perms_by=a&pause99_peek_perms_query=AZAWAWI&pause99_peek_perms_sub=1> >>> co-maint SZABGAB Padre >>> <https://pause.perl.org/pause/authenquery?pause99_peek_perms_by=me&pause99_peek_perms_query=Padre&pause99_peek_perms_sub=1> >>> GARU >>> <https://pause.perl.org/pause/authenquery?pause99_peek_perms_by=a&pause99_peek_perms_query=GARU&pause99_peek_perms_sub=1> >>> co-maint SZABGAB Padre >>> <https://pause.perl.org/pause/authenquery?pause99_peek_perms_by=me&pause99_peek_perms_query=Padre&pause99_peek_perms_sub=1> >>> PLAVEN >>> <https://pause.perl.org/pause/authenquery?pause99_peek_perms_by=a&pause99_peek_perms_query=PLAVEN&pause99_peek_perms_sub=1> >>> co-maint SZABGAB Padre >>> <https://pause.perl.org/pause/authenquery?pause99_peek_perms_by=me&pause99_peek_perms_query=Padre&pause99_peek_perms_sub=1> >>> RSN >>> <https://pause.perl.org/pause/authenquery?pause99_peek_perms_by=a&pause99_peek_perms_query=RSN&pause99_peek_perms_sub=1> >>> co-maint SZABGAB Padre >>> <https://pause.perl.org/pause/authenquery?pause99_peek_perms_by=me&pause99_peek_perms_query=Padre&pause99_peek_perms_sub=1> >>> SMUELLER >>> <https://pause.perl.org/pause/authenquery?pause99_peek_perms_by=a&pause99_peek_perms_query=SMUELLER&pause99_peek_perms_sub=1> >>> co-maint SZABGAB Padre >>> <https://pause.perl.org/pause/authenquery?pause99_peek_perms_by=me&pause99_peek_perms_query=Padre&pause99_peek_perms_sub=1> >>> SZABGAB >>> <https://pause.perl.org/pause/authenquery?pause99_peek_perms_by=a&pause99_peek_perms_query=SZABGAB&pause99_peek_perms_sub=1> >>> first-come SZABGAB Padre >>> <https://pause.perl.org/pause/authenquery?pause99_peek_perms_by=me&pause99_peek_perms_query=Padre&pause99_peek_perms_sub=1> >>> THEREK >>> <https://pause.perl.org/pause/authenquery?pause99_peek_perms_by=a&pause99_peek_perms_query=THEREK&pause99_peek_perms_sub=1> >>> co-maint SZABGAB >>> >>> >>> They can give you acess. >>> >>> 2. If only small changes are included, just make it a dot release. >>> >>> 3. I think this is probably up to you. Not much development going on. >>> Tags looks OK to me. Branches can be good for big changes. If more >>> development was going on the branches-vs-tags strategy can be reviewed. >>> >>> 4. No idea. >>> >>> 5. Mac has always been a problem. But it's better to have releases with >>> bug fixes, than no release at all because no mac is available. Contact me >>> on irc, I'll try to get hold of a mac to run the tests once the release >>> candidate is working on Win and Linux. >>> >>> 6. Bug fixes can be released continuously. Bigger releases depends if >>> the development kickstarts again. >>> >>> C. >>> >>> On Fri, Feb 26, 2016 at 12:01 AM, Charlie Gonzalez <itchar...@gmail.com> >>> wrote: >>> >>>> Hello Padre Dev Team, >>>> >>>> I reviewed the prerelease checklist ( >>>> http://padre.perlide.org/pre-release-checklist.html) and release ( >>>> http://padre.perlide.org/release.html ) page for Padre and here are >>>> some things I need to know before I start a release. >>>> >>>> 1- I need access to Padre distribution via PAUSE so I can upload the >>>> new release of Padre. ( my pause account is ITCHARLIE ) >>>> >>>> 2- What version number I should setup for this release? >>>> >>>> 3- In the past Padre was released via svn and now we are using Github. >>>> Should we follow the same procedure and create a branch for every release >>>> moving forward or can we just the tag github with a release version ? >>>> >>>> 4- There are tools ( i.e tools/release.pl ) that were executed before >>>> a distribution was uploaded to CPAN and so far it seems like the only >>>> relevant scripts to run from tools repo is ( tidy_project.pl and >>>> update_version_number.pl ) is my assumption correct? >>>> >>>> 5- As far as testing goes. I can only test with a windows 7 machine and >>>> a linux box running Ubuntu. Is testing on these 2 environments sufficient ? >>>> >>>> >>>> 6- After performing this release. how can we determine when to have >>>> another release? >>>> >>>> >>>> >>>> For #3 I would prefer tagging since developers will be creating pull >>>> requests against Padre and most pull requests will be merged against master >>>> branch anyways. >>>> >>>> >>>> Charlie Gonzalez >>>> (E) itchar...@gmail.com >>>> Github Profile <https://github.com/itcharlie> >>>> >>>> >>>> _______________________________________________ >>>> Padre-dev mailing list >>>> Padre-dev@perlide.org >>>> http://mail.perlide.org/mailman/listinfo/padre-dev >>>> >>>> >>> >>> _ >> >> > > _______________________________________________ > Padre-dev mailing list > Padre-dev@perlide.org > http://mail.perlide.org/mailman/listinfo/padre-dev > >
_______________________________________________ Padre-dev mailing list Padre-dev@perlide.org http://mail.perlide.org/mailman/listinfo/padre-dev
