Dev News
From UG
2009 December
Plan for urgent bug#0001571: After creating Credit Note system displays invoice pdf incorrectly
All,
This is an update for urgent bug # 0001571: (Sales&Intern) After creating Credit Note system displays invoice pdf incorrectly (header from invoice, TOC from credit note)
- Jaguar will hold off on issuing any credit notes in CT2 until Monday Dec 14th
- Bug fix is scheduled to be released into production by Monday Dec 14th
- We have to "recover" ONLY invoices for credit notes generated *after* CT2 Accounting lunch: Nov 09.
- Re-entering will be done manually by resources allocated in each local Jaguar office
- Dev Team must provide facility in CT2 to edit invoices. Ideally included in "Monday Dec 14th Emergency Release". If not then included in the next regular Release.
- IT will send backups of correct pdfs for invoices issued until Dec 1 - we do not have pdf files in electronic format for invoices issued after Dec 1. Instead paper based copies have to be discovered and used.
- This is approved by Simon
--Alex 23:56, 9 December 2009 (UTC)
(!) Second Client Company (Xpedx in Lynchburg) will be migrated this Wednesday (Dec 16th)
All,
- Jaguar President intends to demo CT2 Client App to our client Xpedx in Lynchburg this Wednesday (Dec 16th). This client has four (4) active users.
- Please make sure that Client Application that is linked to www.jaguarfreight.com is up and running 24x7
Thanks!
--Tira 04:27, 9 December 2009 (UTC)
(!) First Client Company (Pak2000) will be migrated this Tuesday (Dec 8th)
All,
- Jaguar President intends to demo CT2 Client App to our client Pak2000 this Tuesday (Dec 8th) at approx 11.30am (EST), and then have them use CT2 from Wednesday onwards as their primary program. This client has three (3) active users.
- Please make sure that Client Application that is linked to www.jaguarfreight.com is up and running 24x7
- If we are going to run Client App on .2 server then this server must be up 24x7
Thanks!
--Alex 04:27, 7 December 2009 (UTC)
Watch and due Mantis fields
- "Watch" field now contains Sprint number and scheduled Release Date for that Sprint. It indicates Sprint during which task is planned to be completed and released.
- "due" field now indicates week of the month for the month that is selected in Watch. For example if Watch=s3:feb2 and due=8-14 then it means that developer/QA are planning to complete this task during the 2nd week in feb (between feb 8 and 14)
(!!!) SVN Migration has been re-scheduled for Fri, Dec 4 (early morning or later Novosib time)
- SVN will be in read-only mode from Fri, Dec 4 (early morning or later Novosib time) to possibly Dec 7 or 8 or 9 depending on how successful we are with migration.
--Alex 15:50, 3 December 2009 (UTC)
SVN Migration is scheduled for Monday, Dec 7 (8 am Kiev time)
- Pls make sure you commit all your code before 8 am Kiev time (Noon Novosibirsk)
- SVN might not be available for 1-2 days
2009 November
SpecQA goal: complete all high/med tasks by Dec 15
Attn: Developers / Sys Analysts,
Tira and I agreed on this goal:
Complete all high/med tasks in SpecQA by Dec 15. This is to be able to create advanced plan for several months ahead. I would like to repeat that this is the most important task for the next 2 weeks (Of course this is AFTER we successfully release Dec 1).
Let me know if you have any questions.
Alex.
SpecQA and Future Planning
Attn: Developers / Sys Analysts,
We need to plan all Sprints in advance. In Sprint Plan we want to include only estimated and passed Spec QA tasks.
Next Sprints are:
- Sprint#1 (Dec 1-15)
- Sprint#2 (Dec 15-30)
- Sprint#3 (Jan 1-30)
- Sprint#4 (Feb 1-28)
The goal is to review, estimate enough tasks:
- for Sprint#1 by(on) Dec 1
- for Sprint#2 by Dec 15
- for Sprint#3,4 by Dec 30
Tasks must be reviewed / estimated in the order of priority. Urgent tasks first, then high, then med, etc.
All these tasks are assigned to specific developer and live in SpecQA mantis folder. As usual if you have questions set feedback/assigned to Sys Analyst. And if you finished then set task as completed and leave it in SpecQA folder.
Thx!
--Alex 19:25, 28 November 2009 (UTC)
Release to Staging has been moved AGAIN to earlier date: Fri, Nov 27
--Alex 21:02, 26 November 2009 (UTC)
Mantis folders re-organized
--Alex 22:31, 25 November 2009 (UTC)
I re-organized mantis folders. These are the folders that you should see: http://mantis.jaguarfreight.com/wiki/File:Mantis_projects.JPG
Tasks assigned to developers in SpecQA mantis folder (important!)
Developers are going to be assigned tasks in SpecQA. This is not for immediate coding! This is to QA the spec. Developers have to:
- set as accepted/started
- review task / read spec
- set emh
- set risk
- if there are questions - set to feedback, assign back to sys analyst (Alex or Tira)
- set as completed and leave it in specQA
After they pass your QA at some point they are going to appear in the Next Sprint folder which contains all tasks planned fro Next Sprint.
Release to Staging has been postponed until Monday, Nov 30
(Nov 24, Tue) from Alex
- We postponed because we want to test/fix all other reports as much as possible, not just List CTs/In Transit
- Priorities:
- p1) In Transit / List CTs
- p2) Main, Where Is, Daily
- p3) 6 internal reports
- I assume we can test Staging in one day and if no critical bugs found - we release into Production on Tuesday, Dec 1
Reminder: Thursday/Fri are holidays in the USA this week
(Nov 24, Tue) Alex
December Sprint - radically new approach
(Nov 24, Tue) from Alex This time we are dead serious about long term planning:
- Sprints period will be 1 month not 1 week as before
- Release to production will be always done once a month (before th 1st of the month)
- All specs must be completed, estimated and pass QA
- It will be very important not to over promise
- Currently PM Team is reviewing all tasks with stakeholders and assigning urg/high/med/low priorities to each task. After that each task will be assigned tentatively one of the Sprints in Dec, Jan, Feb, Spring, Summer
