What about having an IRC-meeting to go through the issues and decide what should go into 3.1 and what could be moved to 3.2.
We have developers in quite different timezones (UTC+1, UTC+2 and UTC+10 are the ones I know about) - so it might be not so easy to find a common time-slot but we should try: So please pick your preferred time slots for an IRC meeting (all times in UTC!): http://doodle.com/tbxe8aikq7sg7yf6 Best, Jakob On 3 July 2013 12:46, Sergio Fernández <[email protected]> wrote: > Hi, > > yesterday Jakob and me we were talking about the possibility to plan the > next release by the end of July 2013. I think we have made an important > progress in many parts of the project, but we should try to reflect those > things as releases. > > Taking a quick look into our issue tracker: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MARMOTTA%20AND%20fixVersion%20%3D%20%223.1-incubating%22%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20ORDER%20BY%20priority%20DESC > > Currently there are 55 issues planner for that version. For me it's quite > clear that we would need to prioritize some of them, and shift some to 3.2. > So I think all current assignees should decide what to do with their issues > by 3.1.0, trying to balance priority and the time they would have to take > care of those issue. > > What do you think? Would be feasible? > > Cheers, > > -- > Sergio Fernández
