Re: [Dspace-devel] Request for delay of feature freeze.
Hi Mark, I'm generally in agreement. At last weeks developers meeting it was agreed to extend the feature freeze for 'a few days' in order to get these features in. That was a bit vague, but that is not necessarily a bad thing. I would be loathe to set a new deadline as that may encourage people to take their foot off the peddle a little and obviously the sooner things are committed the better. Either Tim or myself continue to be in contact with the developers of all the issues you list and I am hopeful we will see them all being resolved soon. With regards to DS-881, I think there was general agreement that this issue could be considered a bug fix and was therefore not subject to the feature freeze deadline. Its worth pointing out to all that bug fixes are permitted until the testathon. Obviously though that particular issue will require a significant change to the build process so it would be good to have it discussed on Wednesday. Cheers, Robin. On Mon, 2011-08-22 at 19:48 +0100, Mark Diggory wrote: I'm noticing that there are a number of remaining issues that we would all benefit from seeing get into DSpace 1.8. I'd like to propose that the feature freeze be delayed another week to assure these can be included into DSpace. 1.) add the capability to indicate a withdraw reason to an item ( tombstone ) (https://jira.duraspace.org/browse/DS-587) 2.) additional work around it by Richard Rodgers (https://jira.duraspace.org/browse/DS-996) 3.) Add allow/deny rules for self-registration in the simple password authentication module (https://jira.duraspace.org/browse/DS-994) 4.) allow for bitstream display order to be changed (https://jira.duraspace.org/browse/DS-749) 5.) Implement Creative Commons Web Service API with the Submission Process (https://jira.duraspace.org/browse/DS-964) I would also propose that we add the following to the list and focus on a consensus about this in the Wednesday Meeting. 6.) DSpace doesn't build properly with Maven 3 (https://jira.duraspace.org/browse/DS-881 There are a number of fixes in DS-818 that will resolve the above issue but require some reorganization of our build process. I would like to assure that there is concensus around these for DSpace 1.8 Cheers, Mark -- Get a FREE DOWNLOAD! and learn more about uberSVN rich system, user administration capabilities and model configuration. Take the hassle out of deploying and managing Subversion and the tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2 ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
Re: [Dspace-devel] Request for delay of feature freeze.
I mostly wanted to second what Robin said below. Essentially, if anyone has a feature that barely missed the freeze, they should get in touch with Robin to discuss it. If something is 90-95% complete, chances are we still have enough time to get it in (but again talk to Robin first). As Robin mentioned, he I are working to shepherd in those features that barely missed the freeze but are very close to completion. Turnaround is very quick on some of these features -- so, please take part in the discussion on JIRA for each of the features (mentioned by MarkD previously). If any others come up that need immediate quick feedback, Robin or I will make everyone aware of them. We'll also be able to use our meeting tomorrow to discuss all of this, and try to finalize our dates for the 1.8.0 Testathon (so we can start to get the word out). I agree with everyone else that DS-881 (Maven 3) would also be good to discuss. If you have questions, comments or conce rns, let us know! - Tim On Tuesday, August 23, 2011 6:53:18 AM, Robin Taylor wrote: Hi Mark, I'm generally in agreement. At last weeks developers meeting it was agreed to extend the feature freeze for 'a few days' in order to get these features in. That was a bit vague, but that is not necessarily a bad thing. I would be loathe to set a new deadline as that may encourage people to take their foot off the peddle a little and obviously the sooner things are committed the better. Either Tim or myself continue to be in contact with the developers of all the issues you list and I am hopeful we will see them all being resolved soon. With regards to DS-881, I think there was general agreement that this issue could be considered a bug fix and was therefore not subject to the feature freeze deadline. Its worth pointing out to all that bug fixes are permitted until the testathon. Obviously though that particular issue will require a significant change to the build process so it would be good to have it discussed on Wednesday. Cheers, Robin. On Mon, 2011-08-22 at 19:48 +0100, Mark Diggory wrote: I'm noticing that there are a number of remaining issues that we would all benefit from seeing get into DSpace 1.8. I'd like to propose that the feature freeze be delayed another week to assure these can be included into DSpace. 1.) add the capability to indicate a withdraw reason to an item ( tombstone ) (https://jira.duraspace.org/browse/DS-587) 2.) additional work around it by Richard Rodgers (https://jira.duraspace.org/browse/DS-996) 3.) Add allow/deny rules for self-registration in the simple password authentication module (https://jira.duraspace.org/browse/DS-994) 4.) allow for bitstream display order to be changed (https://jira.duraspace.org/browse/DS-749) 5.) Implement Creative Commons Web Service API with the Submission Process (https://jira.du raspace.org/browse/DS-964) I would also propose that we add the following to the list and focus on a consensus about this in the Wednesday Meeting. 6.) DSpace doesn't build properly with Maven 3 (https://jira.duraspace.org/browse/DS-881 There are a number of fixes in DS-818 that will resolve the above issue but require some reorganization of our build process. I would like to assure that there is concensus around these for DSpace 1.8 Cheers, Mark -- Get a FREE DOWNLOAD! and learn more about uberSVN rich system, user administration capabilities and model configuration. Take the hassle out of deploying and managing Subversion and the tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2 ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/ lists/listinfo/dspace-devel -- Get a FREE DOWNLOAD! and learn more about uberSVN rich system, user administration capabilities and model configuration. Take the hassle out of deploying and managing Subversion and the tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2 ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
Re: [Dspace-devel] Request for delay of feature freeze.
I think this is a sensible proposal. And I agree that 881 is a bug fix and shouldn't be subject to deferral by the Feature Freeze, though I'd be concerned if a fix didn't land well in advance of Testathon. -- Mark H. Wood, Lead System Programmer mw...@iupui.edu Asking whether markets are efficient is like asking whether people are smart. pgp9BHC75oiPR.pgp Description: PGP signature -- Get a FREE DOWNLOAD! and learn more about uberSVN rich system, user administration capabilities and model configuration. Take the hassle out of deploying and managing Subversion and the tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2 ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
Re: [Dspace-devel] Request for delay of feature freeze.
Hi Mark, I'd like to see these fixes get into the release too. I became overwhelmed in the past week and was unable to complete/test/commit all the issues I had on my plate. Peter Dietz On Mon, Aug 22, 2011 at 2:48 PM, Mark Diggory mdigg...@atmire.com wrote: I'm noticing that there are a number of remaining issues that we would all benefit from seeing get into DSpace 1.8. I'd like to propose that the feature freeze be delayed another week to assure these can be included into DSpace. 1.) add the capability to indicate a withdraw reason to an item ( tombstone ) (https://jira.duraspace.org/browse/DS-587) 2.) additional work around it by Richard Rodgers (https://jira.duraspace.org/browse/DS-996) 3.) Add allow/deny rules for self-registration in the simple password authentication module (https://jira.duraspace.org/browse/DS-994) 4.) allow for bitstream display order to be changed (https://jira.duraspace.org/browse/DS-749) 5.) Implement Creative Commons Web Service API with the Submission Process (https://jira.duraspace.org/browse/DS-964) I would also propose that we add the following to the list and focus on a consensus about this in the Wednesday Meeting. 6.) DSpace doesn't build properly with Maven 3 (https://jira.duraspace.org/browse/DS-881 There are a number of fixes in DS-818 that will resolve the above issue but require some reorganization of our build process. I would like to assure that there is concensus around these for DSpace 1.8 Cheers, Mark -- Mark R. Diggory @mire - www.atmire.com 2888 Loker Avenue East - Suite 305 - Carlsbad - CA - 92010 Esperantolaan 4 - Heverlee 3001 - Belgium -- uberSVN's rich system and user administration capabilities and model configuration take the hassle out of deploying and managing Subversion and the tools developers use with it. Learn more about uberSVN and get a free download at: http://p.sf.net/sfu/wandisco-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel -- uberSVN's rich system and user administration capabilities and model configuration take the hassle out of deploying and managing Subversion and the tools developers use with it. Learn more about uberSVN and get a free download at: http://p.sf.net/sfu/wandisco-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
