Dev News
From UG
Links: Project Plan
2010 March
Arden Migration: March 8
We are migrating Elizabeth Arden to CT2 as of March 8th.
DUAL access will be given to EA until March 15th at which time CT1 access will be terminated for Elizabeth Arden users.
This means system will receive additional unusual load.
2010 February
New Mantis field: Requested for Release
Requested for Release - this field holds information provided by Module owners regarding what is desirable release # for this feature. This will be reviewed again on the Sprint planning meeting.
Feb 15: Plan For Tira for next 1.5 week (till Release)
Your most important task is to train Paul in CT2 support and system in general.
Investigate bugs together with him.
You will have daily meetings with me 11am - 12pm and 5pm - 5:30pm where I can help you you with whatever you need. Outside of these timeframes I will be focusing on specs.
! Please make sure that you do not assign anything directly to development unless it is super urgent bag.
Feb 15: Plan For Sasha for next 1.5 week (till Release)
The most critical tas is:
0001716 Misc (CT2 Misc) Com tab: update the URL link for client user to link to client interface.
After that all pdf Commodity tables. Make sure you get specs for Air commod table from Andrei.
After that other tasks on your list.
Pls keep in mind that in general Pdf cmponent priority / quality has been elevated.
Also pls update all emh in Dev so I know what to expect.
See below.
Mantis Snapshot
feb 15: Plan For Kostya for next 1.5 week (till Release)
- Highest priority, start them asap:
0001722 OpsRep (Daily- Elizabeth Arden)Implement the first version 0001535 OpsRep (Truck Billing Manifest) Implement this feature
- 1535 - spec is ready and I think it is very detailed
- 1722 - spec is ready but is not very detailed + plus has errors ; we need 1-2 day to clarify
- About started tasks: 1787, 1656 - not large so finish before above urg tasks. 1750 - if more than 2 hours needed - put on hold, come back after release. In general, I like your work with top bar but it was not high priority task and re-arranging fields on Gen Tab will make many people uncomfortable so do not commit this change.
- Tasks that are set as high are important, pls estimate so I can see if we need to postpone release
- 1673 - pls estimate
Mantis Snapshot
Chargeable weight formula in wiki has been corrected!
(Important!) Clean up schedulers/non jag user accounts when you migrate/copy production
This time we had a HUGE problem. We migrated prod to Demo and Staging and left schedulers running in all places. As a result all clients started to receive 3 copies of all scheduled reports and some of them of course were incorrect.
We should be careful not to repeat this in the future.
Read http://mantis.jaguarfreight.com/wiki/Data_Migration_From_Production_Envir_to_X_Envir_(procedure)
Pls confirm you understand and agree. If not pls let me know why.
Thanks, Alex
12 pdf tasks has been transfered from Andrei to Sasha
Sasha from now on will be main pdf developer:
- 0001694 (Arrival Notice) (Air and Ocean) bug: PDF prints “Continued on next page” for one-page document
- 0001689 (HBL) bug: Incorrect HU/AMS for grouped CTs
- 0001607 (MAWB) bug: for pre-printed version values fall in wrong places (framing); change: increase font
- 0000719 (Shipment Request) Implement this new doc
- 0000044 (Booking Request) Implement this new doc
- 0001433 (Air Cargo Manifest) Re-design layout to fit 2 times more commod lines on 1st page
- 0001562 (DO Air, Ocean) HU Maping Problem. Pieces in the body are different from the total pieces (tracie, 127090)
- 0001605 (MAWB) "Charges section": 1) Need 7 lines, not 4; 2) replace words Carrier and Agent with C and A
- 0000976 (Doc Receipt (M)) Implement this new doc
- 0001604 (MAWB) 1) Add JFS PARIS IATA code into the system 2) pull it into MAWB and HAWB automatically
- 0001603 (MAWB) Add new fields: carrier’s headquarter address; carrier's IATA code; carrier’s account number
- 0001053 (*Misc) DocCenterTab - add file counter as on Files tab
2010 January
Top Priorities: speed, stability (critical bugs), documents (OpsPdfs)
Everyone,
Please prioritize your work accordingly to the below priorities:
- speed
- stability (critical bugs must be fixed)
- documents (OpsPdfs)
Everything else must be done after above is addressed.
Thanks, Alex.
.6 server crashed and will not be available for some time
ETA is sometime today NY time. --Alex 15:06, 29 January 2010 (UTC)
Links for development environments (/CyberTrax, /staging, etc) has been changed to URL without 8080
All,
All links for development (not production) environments (/CyberTrax, /staging, etc) has been changed to URL without 8080.
Home page http://mantis.jaguarfreight.com/svn/ct2/links.html has been updated accordingly.
Regards, Alex.
The following customers have been added on “CT2 Only” clients list from Jan. 4th
PMC
ANWAL
ABU SHAKRA
ETAM
CACHE CACHE
JACADI
ORCHESTRA
JEDEX
HEAD
RHENUS
With best regards
Ph.DELORME
Managing Director
2009 December
Dec-23: CT2 Client Migrations
Dear All,
As of Jan 4th, we will add the following to “CT2 only” client list:
- Prestige Brands
More to follow shortly.
As of 12/28 we will add the following to the “CT2 only” client list:
- Jackel Inc
- Jackel International (Ceramics Shipments)
- Lipenwald
- MacDermid
The following accounts are now CT2 ONLY clients:
· Pak2000
· Morretec
· FPI Plastics
· Basic Fun
· JM Smucker
· L Lawrence
· World Casing
· XpedX-Lynchburg
· John Mills Ltd (first UK client to be migrated)
· XpedX (Greensboro)
· Knoll Printing & Packaging
· C&N
· Interasian Resources
· Titan Tool
· AMSCO Wear Products
--Alex 00:46, 24 December 2009 (UTC)
Dec-23: Weekly Spec / Design Review meetings will be held every Thursday, 2-4pm in New York
Permanent participants:
- Alex
- Tira
- Paul
Goals:
- To present / defend completed specification
- To analyze specification
- To explain new functionality
--Alex 18:38, 22 December 2009 (UTC)
Dec-22: (!) We need to finalize Individual Plans for next Sprint by Dec 29
- This plan is a List Of Tasks from Mantis that you will work on and complete between Dec 25 (Release of Sprint#2 to staging) and Jan 28 (Release of Sprint#3 to staging). These are the tasks that would become part of Sprint#3 Release.
- This list will be distributed to Jaguar management so that they know what and when will be delivered from Our Team.
- pick tasks accordingly to fields "T" ("high" first, etc) and "ds" ("ds0" first, etc)
- set Watch = s3:jan28
- set emh
- set Risk
- ! Make sure all tasks that you selected have "good quality, full" spec. If not call me or Tira so we can fix the spec for you
- Please reserve some time for urgent bugs, communication, planning, etc
- After that pull this list into Excel with these fields/columns: {T, emh, id, Summary}
- this could be done easily using "copy/paste" from Mantis:
- set Watch = s3:jan28, set sort by "T" ascending AND sort by "Issue Id" ascending
- click "Apply filter"
- highlight all, copy all into Notepad (to kill formatting)
- paste into xls
- delete all columns except {T, emh, id, Summary}
- attach this xls to your "*** SpecQA and Future Planning ..." mantis
- call me in Skype to discuss
- this could be done easily using "copy/paste" from Mantis:
- During the Sprint we will review several times to make sure you are on track
- At the end of the Sprint we will compare planned with actual
- Again the idea behind this is that we plan at least 80% of our work and work accordingly to plan.
- If you see that you deviate significantly (for any reason) from your Plan in the future please let me know immediately.
- Please start working on this today
- Please confirm that you read this and understood
Thanks! --Alex 16:03, 22 December 2009 (UTC)
Dec-21: "Watch" field is set to Last Day Of Sprint = Day of Release Of Sprint To Staging
Watch:
- s2:dec24 (end of Sprint#2)
- s3:jan28 (end of Sprint#3)
- s4:feb25 (end of Sprint#4)
- s5:mar25 (end of Sprint#5)
Until now this field was set to Release to Prod date which is misleading. In reality development for all tasks has to be completed by "Release to Staging Date". Even few days earlier so that QA has time to test.
--Alex 20:07, 21 December 2009 (UTC)
Dec-17: John Mills Ltd - first UK client to be migrated as of Monday 12/21
--Alex 22:39, 17 December 2009 (UTC)
Dec-17: Xpedx Lynchburg account will be a CT2 ONLY account from Monday December 21st.
--Alex 15:27, 17 December 2009 (UTC)
Dec-16: We are aiming to migrate over all JML CT1 users to CT2 on Monday (21st)
--Alex 17:16, 16 December 2009 (UTC)
Dec-15: (!) Xpedx Lynchburg demo tomorrow
Please be aware that we will demo CT2 to our client Xpedx Lynchburg tomorrow (Dec 16th) at approximately 12noon EST.
--Alex 14:41, 15 December 2009 (UTC)
Dec-11: (!) Third group of client companies will be migrated between Dec 17/19.
All,
The following clients will migrated CT2
- C&N
- MorreTec
- L. Lawrence
- JM Smuckers
- Basic Fun
- FPI Plastics
- World Casings
The process will be as follows:
1. Create test accounts for each clients, and OPS will review/update the information to ensure CT2 is current/up to date
2. Any existing CT1 in-transit reports will be migrated over to CT2, CT1 reports will be disabled
3. Active user accounts, if any, will be disabled in CT1 and transferred over to CT2
NOTE: Please make sure that Client Application that is linked to www.jaguarfreight.com is up and running 24x7
Dec-9: 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)
Dec-9: (!) 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)
Dec-7: (!) 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)
Dec-3: (!!!) 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
