Re: [Koha-devel] Koha 3.8 release schedule & perltidy process -- more time?
Hi Paul, we have been caught off-guard by this schedule. We have a lot of stuff to submit but March 23rd is too little time. If we have 2 more weeks, we can get good stuff included. Possible? Thanks, Savitra Sirohi Nucsoft OSS Labs http://www.osslabs.biz On Thu, Mar 8, 2012 at 6:29 PM, Paul Poulain <paul.poulain@biblibre.com>wrote:
Hello koha-devel,
I just updated the 3.8 release process with the schedule/planning of the release: http://wiki.koha-community.org/wiki/Roadmap_to_3.8
Here it is: March, 23th (1 month before the release) = feature freeze. April, 6th = strong feature freeze, string freeze April 20th = starting release process, everything frozen April 23th = release of Koha 3.8.0
IMPORTANT = perltidy process
In january IRC meeting we spoke of perltidy thing. We have a coding guideline rule that says code must be perltidied. However, all the existing code is not perltidied, and it's hard to mix perltidied and non perltidied code. Thus, we have investigated the idea of doing a "perltidy big-bang" just when releasing 3.8.0, for all the code.
Pro: * the code will be perltidied, the coding guideline will be applicable * all perltidy being made at the same time, it will be easier to read the git log. (One of the argument against perltidying is that it's a problem for reading git history) * doing that for a release is better for future bugfixes means that patches will apply on 3.8 as well as on master.
Cons: * patches that are waiting may become "does not apply" because of the perltidy thing * patches submitted to fix bugs in 3.8 may not apply on 3.6 easily, that will add more work for 3.6 releases.
All in one, our conclusion was that the best solution is to do that during a release process. So I plan do it during 3.8 release.
(I have a (small ?) question about that : do you think I should make only one huge commit with perltidy ? one for each directory ? one for each file ?)
-- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08 _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
-- Thanks, Savitra Sirohi Nucsoft OSS Labs Professional Support for Open Source Software Ph: +91 89718 06111 Web: http://www.osslabs.biz
Le 09/03/2012 05:09, savitra sirohi a écrit : > Hi Paul, Hi Savitra, > we have been caught off-guard by this schedule. The schedule is the same as what we had for previous time-based-release. I agree that my announcement could have be made a little bit earlier, but you can, for future releases, consider the "1 month before the release" as the "feature freeze" limit. We need time to do some tests, translations,... so we can't freeze things only a few days before the release. > We have a lot of stuff to submit but March 23rd is too little time. If > we have 2 more weeks, we can get good stuff included. Possible? Well, I can't answer this question so easily, I'll start by asking more questions: * could you give us more details about the stuff that will be submitted ? * are you aware that, even if you submit before march 23, it must also be signed-off, QAed, and, if it's large change, that won't be made in a second ? atm, there are 82 patches waiting for sign-off, 12 of them being waiting for more than 2 months ! * Is there a really strong reason to have those features need for 3.8 ? all/many of us have a lot of nice/cool stuff that is waiting for inclusion (almost 50% of the patches waiting for signoff are coming from BibLibre 39/82). -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08
Thanks Paul, I guess we will go ahead and start submitting and hope some of our submissions gets included. No strong reason to get this included in 3.8, other than us having to rebase multiple times. In any case, here are some of the changes we want to submit at this stage, some already have bugzilla entries, I will create new ones for others: Major Maintain exchange rate history, Indian libraries need to pay for items with rates as on invoice date, which can be in the past Events on OPAC - create events with date, description, images, and other fields (similar to News) for display on OPAC Mobile friendly site, modified template files Capture photo, signature via webcam and electronic signature pad Fees - registration, renewal, duplicate card, holds at library and category level Minor Forgot password link, so users can request a new password to be sent to them Fee receipts for printing, including auto receipt no. generation Show links to possible duplicate orders/catalog records in order basket. Staff can verify duplicate before issuing firm orders Renew serials subscriptions in batch Quick patron card print (from patron record after registration) Show entitlements to members in OPAC, essentially make circ rules that apply to a member visible to them via OPAC Allow holds on "on display" items even when allowonshelfholds is off (system pref based) Based on a new system preference set email as default user name (instead of combination of first and surnames) when member is created Setup barcode and member card prefixes at branch level Kid friendlly OPAC system preference, e.g. large call numbers, buttons for search by title, author, subject instead of a drop down list Allow search by Lexile no. and Accelerated reading point and level ranges on OPAC and staff search filters Better items.content for use in notices, e.g. due date, price to be added Allow SIP authentication using userid or cardnumber (currently works only with cardnumber) Save or Export reports output in PDF and text formats (currently only delimited files are exported) Export/print new arrivals reports in ISBD formats Add new tables, keys and criteria in guided reports wizards Add several new fields such as statement of responsibility to normal view (TT and XSLT) in catalog details page in OPAC/Staff Capture suggestor's id when library staff create suggestions More statuses when managing suggestions (e.g. duplicate) Capture accepted, rejected date of suggestions for reporting purposes Several new fields/tables available for use in notice templates Display link to items in PROC (processing center) in cataloging home, this will allow processing center staff to easily identify records they need to work on Include Syspref based Google (or other) Analytics JS code Add more languages to Google Indic Transliteration tool availble with the masthead search box Allow extend patron attributes to be included in patron card templates Syspref to not do remote ip check, this will allow uninterrupted Koha access from locations where ip address changs dynamically Change default password length to 7 Open Library - Larger image, Read, borrow and checked-out status Send renewal notice Send membership expiry reminder notices Add Item availability status to cart Batch userid, password generation and email Display barcode on OPAC detail page Thanks, Savitra Sirohi Nucsoft OSS Labs http://www.osslabs.biz On Fri, Mar 9, 2012 at 2:08 PM, Paul Poulain <paul.poulain@biblibre.com>wrote: > Le 09/03/2012 05:09, savitra sirohi a écrit : > > Hi Paul, > Hi Savitra, > > > we have been caught off-guard by this schedule. > The schedule is the same as what we had for previous time-based-release. > I agree that my announcement could have be made a little bit earlier, > but you can, for future releases, consider the "1 month before the > release" as the "feature freeze" limit. We need time to do some tests, > translations,... so we can't freeze things only a few days before the > release. > > > We have a lot of stuff to submit but March 23rd is too little time. If > > we have 2 more weeks, we can get good stuff included. Possible? > Well, I can't answer this question so easily, I'll start by asking more > questions: > * could you give us more details about the stuff that will be submitted ? > * are you aware that, even if you submit before march 23, it must also > be signed-off, QAed, and, if it's large change, that won't be made in a > second ? atm, there are 82 patches waiting for sign-off, 12 of them > being waiting for more than 2 months ! > * Is there a really strong reason to have those features need for 3.8 ? > all/many of us have a lot of nice/cool stuff that is waiting for > inclusion (almost 50% of the patches waiting for signoff are coming from > BibLibre 39/82). > > -- > Paul POULAIN > http://www.biblibre.com > Expert en Logiciels Libres pour l'info-doc > Tel : (33) 4 91 81 35 08 > -- Thanks, Savitra Sirohi Nucsoft OSS Labs Professional Support for Open Source Software Ph: +91 89718 06111 Web: http://www.osslabs.biz
participants (2)
-
Paul Poulain -
savitra sirohi