[Awsversionmgmt-developers] Project roadmap - explanation and next steps
Command line utility for versioning-enabled S3 buckets in AWS
Brought to you by:
liviutudor
|
From: Liviu T. <liv...@gm...> - 2013-03-08 06:25:07
|
Hi everyone, I'm hoping by now you all have studied the roadmap (please take the time to visit, I have made a few updates recently: http://sourceforge.net/p/awsversionmgmt/wiki/Features%20for%20Future%20Versi ons%20And%20Roadmap/) so I wanted to explain a bit my vision on this project and the plan ahead of us so we're all on the same page. Please note that this is my plan for moving the project forwards, but I am always interested in hearing ideas on this so if you have ideas around the things I'm going to talk about and / or you want to suggest different approaches please reply back (preferably not to me individually, but using this mailing list) and I would be more than glad to incorporate such suggestions in the plans for the project. Hopefully by now you have all downloaded the sources and tried the command-line utility in case you haven't, I can give you a brief overview of it: right now it's just a command-line application which allows a few operations to be performed on a versioning enabled S3 bucket. I suggest strongly you look at the links I've put on the wiki about versioning in S3 if you are familiar with other versioning systems (including for instance SVN!), it's a bit similar to that, but obviously it has its particular issues hence this project! Now, at the moment, as I said, the application only offers the following functionality: * Purge a bucket * List versions And allows for limiting this via a few filters: * Before a certain date * After a certain date * Based on a directory name. Moving the project forward, I have so far planned 2 versions for the future, but this would be an ongoing task I typically prepare the next minor version (in this case 1.0.1) which contains small improvements and bug fixes and basically gives us a chance to plan for the next major version (in this case 1.1.0). For major versions I typically allow for refactoring and adding a big piece of functionality / change in the project. (Then of course there are the "significant" versions in this case this will be 2.0.0 which really are a major version but with a lot of major changes/refactoring in.) If you look at the tickets, you will notice that there are really 3 versions (milestones) in the planner : 1.0.1 (minor version), 1.1.0 (major version) and Backlog. I used backlog as a way to deposit ideas for future versions typically these then get used for planning the next minor or major version, though occasionally some of these can be pulled into the current version we are working on. If you are going to raise a ticket by yourself by the way, I suggest by default you assign it to backlog and start a discussion on this list as to where this should go in terms of milestones. If you look at the tickets for milestone 1.0.1 you will notice there are 7 open ones though the list might increase if we find some bugs or can think of any minor improvements we can add to this release one I have taken over myself and Luckson has offered to look into another one. I would like the rest of you to have a look at the bugs remaining and figure out which one you would think would be most suitable for you and assign it to yourself. I think the best way to start getting into this project is by starting dealing with the code of course myself and the other developers are going to be here for help and exchange of ideas so feel free to ask, there is no such thing as a silly question! As I said before, while we are working on version 1.0.1, I wanna kick off a few discussions and bounce a few ideas regarding some of the major issues I want us to tackle in the next major release (1.1.0). At the same time, we will probably kick off some discussions regarding looking into the future at some of the issues which are currently in the Backlog. I will send a separate email for each issue I want us to discuss please reply as always to the list from what I can see the mailman package on sourceforge can structure the replies into threads and hopefully will result in a nice thread of discussions regarding these. How does this sound to everyone? Liv Liviu Tudor E: liv...@gm... <mailto:liv...@gm...> C: +1 650-2833815 (USA) M: +44 (0)7591540313 (UK, Europe) W: http://about.me/liviutudor <http://about.me/liviutudor> Skype: liviutudor I'm nobody, nobody's perfect -- therefore I'm perfect! |