[Phpmyadmin-devel] Upgrading sf.net project
Hi maybe you've noticed, maybe not, but sf.net is slowly moving to new platform called Allura [1] and projects can opt in for upgrading. There seems to be quite a lot of improvements [2], especially in the Issue tracking (you can see Allura's own tickes [3] as an example). There are upgrading information on separate page [4] and none of not migrated things does not affect us, so I'd go for upgrade. Any comments on that? [1]:https://sourceforge.net/p/allura/ [2]:https://sourceforge.net/p/allura/wiki/Features/ [3]:https://sourceforge.net/p/allura/tickets/ [4]:https://sourceforge.net/p/upgrade/ -- Michal Čihař | http://cihar.com | http://blog.cihar.com
Le 2012-07-20 04:24, Michal Čihař a écrit :
Hi
maybe you've noticed, maybe not, but sf.net is slowly moving to new platform called Allura [1] and projects can opt in for upgrading. There seems to be quite a lot of improvements [2], especially in the Issue tracking (you can see Allura's own tickes [3] as an example).
There are upgrading information on separate page [4] and none of not migrated things does not affect us, so I'd go for upgrade. Any comments on that?
[1]:https://sourceforge.net/p/allura/ [2]:https://sourceforge.net/p/allura/wiki/Features/ [3]:https://sourceforge.net/p/allura/tickets/ [4]:https://sourceforge.net/p/upgrade/
One thing I don't like: it seems that all references we have in the ChangeLog to bug, rfe and patches would no longer be valid... -- Marc Delisle http://infomarc.info
2012/7/20 Marc Delisle <marc@infomarc.info>:
Le 2012-07-20 04:24, Michal Čihař a écrit :
Hi
maybe you've noticed, maybe not, but sf.net is slowly moving to new platform called Allura [1] and projects can opt in for upgrading. There seems to be quite a lot of improvements [2], especially in the Issue tracking (you can see Allura's own tickes [3] as an example).
There are upgrading information on separate page [4] and none of not migrated things does not affect us, so I'd go for upgrade. Any comments on that?
[1]:https://sourceforge.net/p/allura/ [2]:https://sourceforge.net/p/allura/wiki/Features/ [3]:https://sourceforge.net/p/allura/tickets/ [4]:https://sourceforge.net/p/upgrade/
One thing I don't like: it seems that all references we have in the ChangeLog to bug, rfe and patches would no longer be valid...
I moved my project a few months ago and had some issues, mainly with moving the svn/git repo's (having more than 1 repo was not supported at that time), but that's not an issue for us, as our repo's are at github at the moment. Considering the trackers, they were migrated to the new tracker system (if I remember correctly), but they loose the ID we rely on for reference in the changelog, so there might be an issue there, as Marc mentions. About the new issue tracker : batch operations (on multiple items at the same time) are not possible anymore. -- Kind regards, Dieter Adriaenssens
Hi Dne Fri, 20 Jul 2012 13:42:58 +0200 Dieter Adriaenssens <dieter.adriaenssens@gmail.com> napsal(a):
I moved my project a few months ago and had some issues, mainly with moving the svn/git repo's (having more than 1 repo was not supported at that time), but that's not an issue for us, as our repo's are at github at the moment.
Right, these are non issue for us.
Considering the trackers, they were migrated to the new tracker system (if I remember correctly), but they loose the ID we rely on for reference in the changelog, so there might be an issue there, as Marc mentions.
Could you check if at least you will get redirected from old URL to new one? Otherwise it would be really pain :-(.
About the new issue tracker : batch operations (on multiple items at the same time) are not possible anymore.
There is "Bulk edit" at top of the tracker (pen icon), what should do it, though I did not check how it compares to current batch operations as I don't have any migrated project which would use tracker/tickets. -- Michal Čihař | http://cihar.com | http://blog.cihar.com
2012/7/20 Michal Čihař <michal@cihar.com>:
Hi
Dne Fri, 20 Jul 2012 13:42:58 +0200 Dieter Adriaenssens <dieter.adriaenssens@gmail.com> napsal(a):
I moved my project a few months ago and had some issues, mainly with moving the svn/git repo's (having more than 1 repo was not supported at that time), but that's not an issue for us, as our repo's are at github at the moment.
Right, these are non issue for us.
Considering the trackers, they were migrated to the new tracker system (if I remember correctly), but they loose the ID we rely on for reference in the changelog, so there might be an issue there, as Marc mentions.
Could you check if at least you will get redirected from old URL to new one? Otherwise it would be really pain :-(.
When following a link to an 'old' tracker item, I get redirected to the project page, not the 'new' tracker item. :(
About the new issue tracker : batch operations (on multiple items at the same time) are not possible anymore.
There is "Bulk edit" at top of the tracker (pen icon), what should do it, though I did not check how it compares to current batch operations as I don't have any migrated project which would use tracker/tickets.
Failed to notice this before. I tried it and it works fine. -- Kind regards, Dieter Adriaenssens
2012/7/20 Dieter Adriaenssens <dieter.adriaenssens@gmail.com>:
2012/7/20 Michal Čihař <michal@cihar.com>:
Hi
Dne Fri, 20 Jul 2012 13:42:58 +0200 Dieter Adriaenssens <dieter.adriaenssens@gmail.com> napsal(a):
Considering the trackers, they were migrated to the new tracker system (if I remember correctly), but they loose the ID we rely on for reference in the changelog, so there might be an issue there, as Marc mentions.
Could you check if at least you will get redirected from old URL to new one? Otherwise it would be really pain :-(.
When following a link to an 'old' tracker item, I get redirected to the project page, not the 'new' tracker item. :(
Hi, I opened an issue [0] with sourceforge to ask to keep a reference between the old and the new tracker items. I'll keep you informed of their reply. Apparently we are not the only project having an issue with losing the old tracker ID's [1] [0] https://sourceforge.net/p/forge/site-support/637/ [1] https://sourceforge.net/p/forge/site-support/623/ -- Kind regards, Dieter Adriaenssens
Hi Dne Tue, 18 Sep 2012 10:59:02 +0200 Dieter Adriaenssens <dieter.adriaenssens@gmail.com> napsal(a):
I opened an issue [0] with sourceforge to ask to keep a reference between the old and the new tracker items. I'll keep you informed of their reply. Apparently we are not the only project having an issue with losing the old tracker ID's [1]
[0] https://sourceforge.net/p/forge/site-support/637/ [1] https://sourceforge.net/p/forge/site-support/623/
Also I've asked the question in their blog [1] and the answer is "old tracker URLs will redirect to the new tickets". But there is no time estimate for that... [1]:http://sourceforge.net/blog/who-else-has-upgraded/ -- Michal Čihař | http://cihar.com | http://phpmyadmin.cz
2012/9/18 Michal Čihař <michal@cihar.com>:
Hi
Dne Tue, 18 Sep 2012 10:59:02 +0200 Dieter Adriaenssens <dieter.adriaenssens@gmail.com> napsal(a):
I opened an issue [0] with sourceforge to ask to keep a reference between the old and the new tracker items. I'll keep you informed of their reply. Apparently we are not the only project having an issue with losing the old tracker ID's [1]
[0] https://sourceforge.net/p/forge/site-support/637/ [1] https://sourceforge.net/p/forge/site-support/623/
Also I've asked the question in their blog [1] and the answer is "old tracker URLs will redirect to the new tickets". But there is no time estimate for that...
The mentioned issue with the tracker redirects is solved now. See : https://sourceforge.net/p/forge/site-support/637/ Unless there is another issue that concerns us, we could prepare moving to the new project interface of sourceforge.net Because the old tracker items will be redirected to the new interface, there is no need to convert all current references (f.e. in ChangeLog or on the wiki), but future/new issues will not have an 'old style' tracker ID, so the scripts converting the changelog file into changelog.php will have to be updated. The SF.net newsletter mentioned that this year all projects will be migrated to the new project. If they mean 2012, phpMyAdmin will be moved in 1,5 month time automatically.
-- Kind regards, Dieter Adriaenssens
Hi Dne Thu, 15 Nov 2012 20:59:59 +0100 Dieter Adriaenssens <dieter.adriaenssens@gmail.com> napsal(a):
The mentioned issue with the tracker redirects is solved now. See : https://sourceforge.net/p/forge/site-support/637/
Unless there is another issue that concerns us, we could prepare moving to the new project interface of sourceforge.net
Rich Bowen from sf.net offered us test migration some time ago, so that we will be able to check what would be possibly broken. But I haven't heard from him since two weeks ago, so I have no clue what is status there... -- Michal Čihař | http://cihar.com | http://phpmyadmin.net
Michal Čihař a écrit :
Hi
Dne Thu, 15 Nov 2012 20:59:59 +0100 Dieter Adriaenssens <dieter.adriaenssens@gmail.com> napsal(a):
The mentioned issue with the tracker redirects is solved now. See : https://sourceforge.net/p/forge/site-support/637/
Unless there is another issue that concerns us, we could prepare moving to the new project interface of sourceforge.net
Rich Bowen from sf.net offered us test migration some time ago, so that we will be able to check what would be possibly broken. But I haven't heard from him since two weeks ago, so I have no clue what is status there...
Got a reply from Rich Bowen; there are a few issues that have a high probability of breaking our upgrade and they are looking at them. -- Marc Delisle http://infomarc.info
participants (3)
-
Dieter Adriaenssens -
Marc Delisle -
Michal Čihař