Thanks Andrea, I released a few historical releases myself (using the email list as a record of when the releases where made).
-- Jody Garnett On 25 October 2015 at 02:15, Andrea Aime <[email protected]> wrote: > Hi, > after some time working on our new jira tracker I noticed that I kept on > considering the old migrated > ticket troublesome and "to stay away from", mostly because they are still > lacking a number > of information in them. > > So this week I decided to move from complaint to action and wrote myself a > set of > small throwaway utilities to migrate some other bits from the xml dumps we > have handy > > For those interested, the dumps are avaiable at > http://webextra.osgeo.osuosl.org/codehaus/ > and the utils I'm using (pretty ugly code, you're warned) are available > at https://github.com/aaime/jira-migration > > For the moment I've migrated all "affect version", "fix for version", and > issue type > from those files back in Jira, for GeoTools and GeoServer. > > The process is pretty long, as the hosting tries to actively fight off > mass changes and > logs me out, makes requests fail and so on (so I built a retry mechanism > that stubbornly > retries the migration of a given issue if it fails). > Sometimes the migration has to be re-run 2-3 times regardless, and each > run can take 2-3 hours, > but oh well, in the end the tickets get updated. > > I've looked into removing the HTML tags, but that's quite a bit of work > that I'm not really prepared > to take on. > > I've also tried to re-establish the relations between tasks and sub-tasks, > in this case it's the > little jira-client library I'm using that's not playing ball, not sure if > anything wants to take time to fix it, > right not I'm leaning towards migrating sub-tasks to tasks (sub-task > cannot be assigned without > a parent, the parent is apparently not editable though with the library), > and then link them back > to their parent as a "blocks" link. > > Anyways, next on my plate is to try to reattach components, if at all > possible, see if I can > relink issues, and again if it does not take too much time, try to > re-attach authors now > that we have some user base logged into Jira. No promises, depending on > how hard > and how inspired I am, I might do all or none of them (or something else > entirely!) ;-) > > The tools are generic, so they could be used to perform the same > migrations for UDIG > and GeoApi, if anyone is interested, just run the MigrateApp and answer > the questions > (warning, when it asks for the Jira password, it will show up in > cleartext, so make sure you're > alone when you run them... I've tried using the Console class, but it does > not work > with the Eclipse console view, and I did not want to waste time setting up > a maven > launcher...). Oh well, if you find it useful fork it, improve it, and if > you feel like, send over pull requests. > > Cheers > Andrea > > PS: I wanted to re-release all the released versions in Jira (which are > now un-released) > but the dumps do not contain any info about the release dates... so we're > out of luck date wise, > but the release notes seem to be working fine, e.g..: > > > https://osgeo-org.atlassian.net/jira/secure/ReleaseNote.jspa?projectId=10000&version=10139 > > -- > == > GeoServer Professional Services from the experts! Visit > http://goo.gl/it488V for more information. > == > > Ing. Andrea Aime > @geowolf > Technical Lead > > GeoSolutions S.A.S. > Via Poggio alle Viti 1187 > 55054 Massarosa (LU) > Italy > phone: +39 0584 962313 > fax: +39 0584 1660272 > mob: +39 339 8844549 > > http://www.geo-solutions.it > http://twitter.com/geosolutions_it > > *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003* > > Le informazioni contenute in questo messaggio di posta elettronica e/o > nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il > loro utilizzo è consentito esclusivamente al destinatario del messaggio, > per le finalità indicate nel messaggio stesso. Qualora riceviate questo > messaggio senza esserne il destinatario, Vi preghiamo cortesemente di > darcene notizia via e-mail e di procedere alla distruzione del messaggio > stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, > divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od > utilizzarlo per finalità diverse, costituisce comportamento contrario ai > principi dettati dal D.Lgs. 196/2003. > > > > The information in this message and/or attachments, is intended solely for > the attention and use of the named addressee(s) and may be confidential or > proprietary in nature or covered by the provisions of privacy act > (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection > Code).Any use not in accord with its purpose, any disclosure, reproduction, > copying, distribution, or either dissemination, either whole or partial, is > strictly forbidden except previous formal approval of the named > addressee(s). If you are not the intended recipient, please contact > immediately the sender by telephone, fax or e-mail and delete the > information in this message that has been received in error. The sender > does not give any warranty or accept liability as the content, accuracy or > completeness of sent messages and accepts no responsibility for changes > made after they were sent or for other risks which arise as a result of > e-mail transmission, viruses, etc. > > ------------------------------------------------------- > > > ------------------------------------------------------------------------------ > > _______________________________________________ > GeoTools-Devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/geotools-devel > >
------------------------------------------------------------------------------
_______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
