Posts Tagged Mercurial Project
A New Beginning
Posted by Sid in DPS911, Mercurial Project, Open Source on January 15th, 2009
I’m finally back from my month long vacation and a new semester at Seneca College has begun. I spent most of the holidays trying to take it easy and get some rest. It was a welcome change from the frenzied quick pace of last semester.
This semester (my last at Seneca) I will be continuing my work with hgweb but in a new course setting, DPS911 the successor of my previous open source course. David Humphery will be mentoring us once again but the onus is on the students to get the work done.
For this course the goal is to make 7 releases so that the project goes from a version 0.3 to a version 1.0 in a matter of 3 months. We will be making a release at a rate of 1 every 2 weeks so the students will have to be constantly working on their projects to keep up.
I’ve created a project description and plan for this course which will help me visualize and keep track of what needs to be done. Lets hope things go well
Ready, set, GO!
v0.3 Release - Problem with my Patch for bug 445560
Posted by Sid in Mercurial Project, Open Source on November 24th, 2008
I had a discussion with ted today relating to my patch for bug 445560 for the pushlog. There seems to be a slight problem with it. When there are 2 merges on one page, if one clicks the second expand link, it shows those changesets, but the row with the [Expand] link disappears (example of the problem). This is a problem that we don’t want happening.
Problem
Currently I’m using the date as a unique identifier (view here for full details) but if somehow (very unlikely, but possible) two rows have the same date then there will be a problem, which is the case with the example linked above.
Fix
This problem can be solved by using the id as the unique identifier instead of the date. This will work because each changeset has a different id and each set merge changesets have the same id so it will allow one to identify all the merge changesets to hide on a page and not hide the ones that shouldn’t be hidden.
I will be putting up a new patch to fix this issue.
Edit: I didn’t read the comments (comment #6) that ted put on bug 445560 for my patch before I made this post. There is another problem that he identified, which I need to fix. Apparently I’m not allowed to have multiple elements with the same id so I can’t be putting my unique identifiers in the id of the tag. ted recommended putting them in the class of the tag which is what I will be doing. Look out for a new blog post explaining the code.