Posts Tagged v0.2

Looking Forward to v0.3 Release

The end of the semester is approaching fast and so the due of my  v0.3 release. I’ve had a talk with jorendorff about what I should do for my next release. We discussed working on the ability to filter by file/directory or a graph view for the pushlog. In the end we decided that working on a graph view for the pushlog would be a pretty amazing thing to work on.

Dirkjan Ochtman (djc) has already done some work on this graph view feature which you can see here. So now my job is to adapt and adjust the work done by djc for the pushlog. At this point I can’t really say how hard or easy this is going to be. All I know is that this feature would be quite awesome to have as far as the users are concerned.

I also will be looking to make fixes to the patches I submitted for my v0.2 release as the reviews come in.

With all the other assignments I have due the time to work on my v0.3 release isn’t too much so I need to be efficient with my work. Here’s hoping things go well…

, , , , , ,

No Comments

v0.2 Complete

“Takes a deep breath”

Well, I’ve finally completed my v0.2 release. I have to say that it has been tough and grueling. Throughout this period I have struggled to get things done countless times. I’ve hit the proverbial brick wall on so many occasions that I feel like I’m part of the wall now (the wall is like the annoying neighbor that won’t go away). Open source is definitely the course I have spent the most time on this semester. I’ve spent countless hours on this release (I’m guessing around 50-60hrs, at least it feels like that but I may be way off). But don’t get me wrong here. I’m not complaining. I’ve enjoyed myself too. These projects are hard and they will take time to complete. I know and accept that. I am getting better at working with my project too as with everyday that passes I feel I am more confident about my work.

I plan to release the patches for my 3 tasks (view here) tomorrow morning. They will all get reviewed by the Mozilla elders and I hope they get accepted. But, I am not naive. I don’t think they will get accepted immediately. This will be my first time providing a Mozilla patch and so I am sure that I probably have done something that they will not agree with. This is fine. It is all a learning process. Even people that have years of experience can get their patches rejected. Such a thing will not deter me if it happens.

ted, jorendorff and djc have been very helpful. Whenever I have had a question they have guided me onto the right track. Just have a look at my project page to see how many times I have discussed something with them.

We have less than a month left till the semester ends and I need to decide quickly on what I will be working on for my v0.3 release. At this moment I am too exhausted to decide. I will probably make my decision very soon so that I can get going on it. There isn’t much time left. Look out for a future blog post explaining what I will be doing.

, , , , ,

No Comments

Looking Forward to v0.2 Release

The date for my v0.2 Release is approaching rapidly and it’s time that I decide on what exactly I will be working on. After a good bit of thought I have decided that my best option is to work on the following:

  • Continue working on bug 459727 to make pushloghtml show more entries onScroll
  • Add a fix to ted’s patch for bug 445560 so that when the user clicks on a particular [Expand] link it only expands the changesets belonging to it and not all changesets on the page.
  • Add functionality to show which files were touched by a changeset and roughly the size of the diffs. Maybe add onMouseOver functionality to show it in an unobtrusive way.

I think adding these 3 features will be more than enough for v0.2 release in terms of work load. I have already spent countless hours working on the  first 2 features. Also I think these 3 features will benefit the community the most by improving the core features of the pushlog. I’ve consulted with jorendorff on this and he seems to agree that these 3 features would be good enough for my next release.

, , , , , , ,

No Comments